Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Get Your Team Questions Answered Here #1878

Open
1 of 5 tasks
Rabia2219 opened this issue Jan 6, 2025 · 11 comments
Open
1 of 5 tasks

Get Your Team Questions Answered Here #1878

Rabia2219 opened this issue Jan 6, 2025 · 11 comments
Labels
Complexity: Small feature: FAQ Question Further information is requested ready for product ready for a PM to review or assess Role: Product Management size: 1pt Can be done in 6 hours
Milestone
03 - Project Mana...

Comments

@Rabia2219
Copy link
Member

Rabia2219 commented Jan 6, 2025 •
edited by ryanfchase
Loading

Dependency

Waiting for new questions to be added.

Overview

As newbie team members, we need a place to post any questions/suggestions for Bonnie or any other team member.

Action Items

  • Create issue to post questions/suggestions for Bonnie (this issue)
  • Add a question in a new comment
  • Move issue to Questions column
  • Add to agenda
  • Assign to whoever can answer the question, if you know who that is

Resources/Instructions

You can post any questions/suggestions in the comments and tag the appropriate person. If urgent or unanswered for a while, you can bring them up in your next meeting by linking this issue in the agenda and moving this issue in the Questions/Review column.
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: 311: Project Board Jan 6, 2025
@Rabia2219 Rabia2219 added this to the 03 - Project Management milestone Jan 6, 2025
@Rabia2219 Rabia2219 mentioned this issue Jan 6, 2025
Open
2 tasks
@ryanfchase ryanfchase moved this from New Issue Approval to Start Here in P: 311: Project Board Jan 20, 2025
@ryanfchase ryanfchase moved this from Start Here to Icebox (on hold) in P: 311: Project Board Jan 20, 2025
@ryanfchase ryanfchase mentioned this issue Feb 2, 2025
Open
@ryanfchase ryanfchase changed the title Get your Team Questions Answered here Get Your Team Questions Answered Here Feb 2, 2025
@ryanfchase ryanfchase mentioned this issue Feb 2, 2025
Open
1 task
@ryanfchase

This comment has been minimized.

Sign in to view
@ryanfchase

This comment has been minimized.

Sign in to view
@ryanfchase

This comment has been minimized.

Sign in to view
@ryanfchase ryanfchase added the Question Further information is requested label Feb 4, 2025
@ryanfchase
Copy link
Member

ryanfchase commented Feb 4, 2025 •
edited
Loading

What is an Emergent Request?

At Hack for LA, emergent requests are tasks that become apparent while working on a ticket, yet that work falls outside the scope of the issue's Action Items. We want to ensure there is a way to document these emergent requests without blocking the work of the originally defined scope. This also allows volunteers to discuss the emergent request, and eventually assess how it should be prioritized.

How to open a new Emergent Request:

  1. From Github's Issues tab, click "New Issue"
  2. Find and choose the issue template, Emergent Request
  3. Fill out all required fields, fill out optional fields as they apply
  4. Apply label for the correct role (e.g. role: Frontend, role: UI/UX Design, role: product, etc)
  5. Apply label for the correct lead (e.g. ready for dev lead, ready for design lead, ready for product, etc)
  6. Apply label for feature, if one applies
  7. Move to the Questions column

About the Question

@ryanfchase
Copy link
Member

What is a Decision Record

Decision Records are wiki pages that document the process of incorporating or rejecting proposals. The proposals can be relating to the application itself (e.g UI/UX considerations, features and behaviors), or they can document team workflows and internal infrastructure. Use these pages to answer the question of why and how our project has arrived at its current state.

Wiki: Decision Records Home

About the Question

@ryanfchase
Copy link
Member

ryanfchase commented Feb 4, 2025 •
edited
Loading

Can multiple be assigned to one issue? Who is responsible for updating the issue?

We don't recommend assigning multiple people to one ticket. This muddies the waters for determining who completed which work on the ticket. To avoid this, leads should be creating tickets that enumerate the minimum amount of work that one person can do to accomplish the task. In some instances, members may need to return an In-Progress issue to Prioritized Backlog and unassign. Members should document when they put down a ticket, so they can highlight which action items they completed.

If a ticket truly does require the collaboration of two or more members at the same time, documentation of each members' participation must appear in the comments.

Exceptions:

  • agendas: remains open for the entire year, we assign all relevant volunteers to this issue
  • epics: all leads or PMs who own tickets on this ticket can be assigned
  • recruitment: multiple leads can be assigned to the recruitment ticket if multiple roles are being recruited

Bonus: note from Bonnie on an offending ticket:

and p.s. this is why everyone cannot be assigned to the same issue. Everyone is assigned so no one pays any attention.

About the Question

@ryanfchase
Copy link
Member

ryanfchase commented Feb 4, 2025 •
edited
Loading

How Should We Use the Questions and In Review Column?

As of 2025-02-04, the use of these columns are as follows:

Questions Column

Questions Column Rule:

  • Always use the Ready For series label when moving a ticket into the Questions column, e.g. ready for product. Tickets without this label may be delayed, or simply moved back to its previous status in order to clean the board
  • Do not use multiple Ready For labels, try to keep the "required party" obvious

Questions Column Usage

  • If ticket was coming from In-Progress...
    • Individual contributors needing input from lead. Leads should quickly attempt to unblock the work. Add this question to an upcoming agenda if you are unable to do so remotely.
    • Leads need input from another role's lead. This signals that closer scrutiny should have been paid to the ticket while it was in New Issue Approval.
  • If the ticket was coming from New Issue Approval...
    • Product creates a ticket, needing sign-off from lead. If the ticket is acceptable, add the ready for prioritization label to signal that product can move this to Prioritized Backlog
    • Leads need input from another role's lead. If you anticipate back-and-forth, consider adding this to an upcoming agenda to resolve "in-person".
  • Design to Engineering Hand Off: see this section below

Question is Resolved

  • Leads should try to manage moving the ticket to its correct location once the question is answered
  • If it is unclear if further discussion is required, add the Ready For label for the role that initiated the discussion

Note: when a ticket is in the Questions column, please make sure the comment containing the actual question is concise and clearly visible. Please try and answer questions on your own before getting the lead's attention.

In Review Column

This column is mainly going to be used for review of code or documents. For example:

  • dev tickets with Pull Requests that need review
  • product tickets with documents that need sign-off from another PM or from Bonnie

Design to Engineering Hand Off may be an exception, see below.

Note About Designers

We don't anticipate individual designers to use either Questions or In Review for their regularly scheduled feedback cycles. As of this time, the entire design team provides each other feedback during their meetings. Their tickets will remain In Progress until their work receives sign-off from the team. See below for how to hand off the ticket to dev.

Design to Engineering Hand Off

Design tickets need to follow a specific hand off process in order to prepare the related dev ticket. Please follow the instructions in the Blank Design Issue template, requiring designer to properly document each iteration of the work and the finalized design.

When the finalized design is provided...

  • design lead to move the ticket to In Review
    • this needs consensus (2025-02-04)
  • dev lead should review the hand off material, moving to Questions if needed
  • dev lead to create the dev ticket(s)
  • dev lead can now close the design ticket. Phew!

About the Question

@ryanfchase
Copy link
Member

When Is The Current Year's Data Unavailable?

At the beginning of each year it takes about a month for the current year's data to become available on LA's Open Data portal. For example, the cumulative 2025 data might not be published by the city until February of 2025.

Screenshot of searching for 2025 data

Image

About the Question

@ryanfchase
Copy link
Member

ryanfchase commented Feb 4, 2025 •
edited
Loading

What Are Milestones, Epics, and Issues, Labels, and their usage?

Definitions are as follows:

  • Issues: a basic task with a definitive end-goal or deliverable
  • Epics: a grouping of Issues, not necessarily defined by Milestone (e.g Epic may be grouped by Milestone, if useful)
  • Milestones: categories that can be assigned to Issues, used in determining ordering and prioritization of work on the 311-Data team.
    • Pre-Launch: colloquially refers to all milestones that come BEFORE the Launch milestone (e.g. 01 - 09)
    • Post-Launch: colloquially refers to all milestones that come AFTER the Launch milestone (e.g. 10.01 - 12, W - Z)

Wiki Pages

About the Question

  • Asked: 2025-01
  • Source: PM check in meeting

@ryanfchase ryanfchase mentioned this issue Feb 4, 2025
Open
6 tasks
@ryanfchase
Copy link
Member

ryanfchase commented Feb 5, 2025 •
edited
Loading

How to Create a Dropdown To Hide Large Images

Type / to get the Command menu...

Click to see "/" Menu

image

Select Details to generate the <details> markdown

Click to see Markdown before clicking Details

🔍 observe the Image URL that we'd like to encapsulate in our Details dropdwon (e.g. ![image](the-url-for-the-image))

image

Click to see Markdown after clicking Details

⚠ This screenshot assumes you copy/pasted the image INSIDE the <details> markdown ⚠

  • It does not automatically do this for you

image

Review Finalized Details Dropdown (Collapsed and Expanded)

Click to see Output (Collapsed)

image

Click to see Output (Expanded)

image

About the Question

This was referenced Feb 8, 2025
Open
Open
@ryanfchase
Copy link
Member

ryanfchase commented Feb 8, 2025 •
edited
Loading

Add to questions:

  • How to add hyperlinks to markdown
  • What is the difference between Complexity: Small vs Medium vs Large ?

ETA: 2/9/2025

@ryanfchase ryanfchase added Role: Frontend React front end work and removed Role: Missing Dependency An issue that includes dependencies labels Feb 8, 2025
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue that includes dependencies label Feb 9, 2025
@ryanfchase ryanfchase added Role: Product Management and removed Role: Frontend React front end work Dependency An issue that includes dependencies labels Feb 9, 2025
@ryanfchase ryanfchase moved this from Icebox (on hold) to Questions in P: 311: Project Board Feb 9, 2025
@ryanfchase ryanfchase added the ready for product ready for a PM to review or assess label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Small feature: FAQ Question Further information is requested ready for product ready for a PM to review or assess Role: Product Management size: 1pt Can be done in 6 hours
Projects
P: 311: Project Board
Status: Questions
Milestone
03 - Project Management
Development

No branches or pull requests
3 participants
@ryanfchase @ExperimentsInHonesty @Rabia2219