Time/Place
Time: 11:00am Eastern Time (US)
Please see the calendar invite for the Zoom link.
Attendees
- Chris Awre
- Thomas Bernhart
- Danny Bernstein
- Robert Cartolano
- Dan Coughlin
- Jon Dunn
- Dan Field
- Raman Ganguly
- Jennifer Gilbert
- Mark Jordan
- Danny Lamb
- Rosalyn Metz
- Este Pope
- Scott Prater
- Robin Ruggaber
- Tim Shearer
- Andrew Woods
- Dustin Slater
- Jennifer Vinopal
- David Wilcox
- Arran Griffith
- Maurice York
- Laurie Arp
- Robert Miller
- Ben Wallberg
- Emily Gore
- Oliver Schöner
Agenda
Topic Introductions and Welcome Technology - Fedora 6.0 Release Criteria We will review the proposed criteria for the Fedora 6.0 Production release as discussed at the last Quarterly Leadership Meeting. Goal: Achieve consensus on the requirements for production release. Strategy Sub-Group Reports (10 mins each) (link to document that lays out the groups) Product Technology Communication, Outreach, Marketing & Community Governance & Business Model Goal: Ensure alignment around group priorities, encourage Leaders to participate in a group. Strategic Planning for Upcoming Fiscal Year Review of program staff rolls following the release of Fedora 6.0 to ensure they serve the goals the program is aiming to achieve. Two proposals to consider: We will be broken into smaller groups to facilitate discussion surrounding these goals and options. Goal: Agree on program needs for technical role going forward. Recap of BreakoutTime Lead 10 mins David 15 mins Danny 30 mins Break (10 mins) 10 mins 30 mins 15 mins Wrap-up, Action Items 10 mins David
Previous Action Items
Notes
Este's discussion group/ strategic planning conversation:
- Gap is tech lead, to help shape what happens post 6. It's nice to have software developers come in, if we're not clear what we're asking them to develop, not the best use of resources. Having someone come in to help shape the future is most needed.
- Also someone able to work with implementers, understand gaps that haven't been previously identified. And help implementers with issues - lean toward tech lead role as priority.
- If we have major technical needs down the road with more implementations, we may need intensive technical development for issues that arise. 75% tech leadership, 25% technical work
- Concern about only three committers - we need the community to be bulked up more, to avoid burnout/job changes
- How to characterize building community aspect - recruiter? People capacity, that portion of the role is important. Needs to be included in the job description.
- Want to rely on committers more for building code - role of leadership in building this.
- Balance between what you ask the community to do and what you have staffing for? Struggle to identify members in the community to contribute
- Fedora 4 was really community led - given the testing and engagement in Fedora 6 has been a positive sign of community engagement - ride on crest of Fedora 6 wave to get more people involved.
- Challenge of attracting volunteer committers? Can't justify involvement in Fedora as much because it isn't as visible to users - application layer isn't visible, it is a utility. It's hard to drum up developers even at the application layer. Saturation in the field - are we setting up the role for struggle/challenge? Will we even be able to get more committers?
- We also need to be able to train new committers - that ties into someone's role. Can't rely on committers to train new committers.
- Someone with ability to do both leadership and hands on work and judgment about when to shift between the two.
- What about a model of using contract work on a regular basis - do we need to allocate all of the position funds to a position/use it now?
Action Items
