...
- Action item: volunteers pick up "high user impact" items, and go through and document what questions need to have answers, and we'll use this small set of concrete cases to establish what our development reporting template should be.
- Megan - Forums
- Clay - Assignments
- David Haines - Synoptic Messages/Forums tool
- Anthony - when returning back from vacation will work with Pete on cleaning up Jira issues
Release Team Creation*
- Release team organization is being organized right now
...
- , and we're in an awkward state while Anthony is on vacation and we don't yet have branch managers.
- UCT's interest in 2.7 not guaranteed, so we can't assume David H, but he expressed interest. Probably want more than one branch manager for this effort.
...
- What is the process for putting together the release team? Anthony -
...
- go out individually to active community members in this area and try to recruit them.
- Need to set up clear expectations and guidelines ahead of time so that if and when things come to a head in the release process it's not just a debate on a phone call.
- It hasn't been like that recently - the discussions have matured since the early days.
- We do need to clearly identify people and roles, and eliminate the mystery.
- Some of the details of pulling this team together is going to need to wait until Anthony gets back, but we won't wait to have it formalized before we start working on what we know needs to happen.
Next Steps
- Volunteers go through a few concrete projects and identify questions that need answers (see above)
- We'll attempt to synthesize these on a Confluence page, and develop a clear template that all development leads can use. Should have this by next week's meeting.
- Anthony will work with Pete on some JIRA cleanup