Newer edit →
How to Run a Telescope Triage Meeting
2,295 bytes added
Created page with " == Introduction == We need to help keep the Telescope project in a healthy state. This needs to happen on a number of fronts, including: * keeping the list of open issues..."
== Introduction ==
We need to help keep the Telescope project in a healthy state. This needs to happen on a number of fronts, including:
* keeping the list of open issues in a productive state
* making sure pull requests are being reviewed in a timely manner
* making sure that any issues/pull requests that are stuck, or need follow-up, get identified and resourced
* helping to unblock people from accomplishing their work
== Ideas for Running the Weekly Meeting ==
# One person should be in charge of taking notes, which need to be made public at the end of the meeting (e.g., in the wiki)
# Another person should lead a discussion with the team, keeping everything on track and progressing. The goal of the meeting isn't to solve everything during the meeting, but to make sure the right people are assigned responsibility to follow-up after the meeting.
# Everyone else is encouraged to work along on their laptop (e.g., in GitHub), and join the discussion.
# Start with Pull Requests.
## Are there any open pull requests that need review?
## Who should do the reviews? Make sure they get assigned.
## Are there pull requests from community members? Let's prioritize these.
## Do any of the open pull requests need additional follow-up or to be closed?
# Next, are there any new "show-stopper" Issues we need to discuss and/or file as a group? For example, recent crash, test failure, broken dev environments, etc.
## Who will take care of filing these?
## Who will own them and make sure they get fixed and reviewed?
# Next, look through the current list of Issues for this week's Milestone/Project.
## Is anything in here at risk?
## Are we stuck on something?
## Can we do anything to remove the risk that this will slip?
## Who needs to get involved and what do they need to do?
# Next, go back to the existing Issues and start working through them in reverse order (oldest to newest).
## Are there any issues we can close
### no longer exists
### no longer a priority
### can't reproduce it
### duplicate of another issue
## If we are going to keep it open, do we have a plan for when we'll do it? Is something else blocking it from happening?
## Are there any Labels we can add, or other information, to make an Issue easier to find and fix?
Retrieved from "
SICT AR Meeting Area
get involved with CDOT
as a Student
as an Open Source Community Member
as a Company
Real World Mozilla
Course Project List
Potential Course Projects
About CDOT Wiki