Community Group Meeting 5 March 2004
Agenda
This is a special meeting to talk about the
Community Goals for 0.4.
Other docs of possible interest:
Discussion
Big-picture things:
- What does success look like?
- What level of investment in community do we make?
- What are the risks to a particular plan?
- Process and results goals are different.
Community Working Group Goals
Proposed process goals:
- Get community docs in better shape and thoroughly discussed by OSAF staff. (Ducky, Mitchell)
- Outreach to Python community re repository in DC, Bay Area, and Seattle:
- Host one SF area Chandler developers event (e.g. Sprint, developer day, etc). (Pieter)
- Outreach to the Seattle area Python Users Group (Ted).
- One person from OSAF to each of the Bay Area UGs at least once and evaluate them (usually Ducky).
- One person from OSAF attending Baypiggies regularly (Ducky, maybe Katie, maybe others).
- Document legal process for contributing code. (Mitchell)
- Document technical process for committing code. (Ducky, Heikki?)
- Lead all-hands discussion about what "success" in the community means. (Mitchell, all)
- Lead working group discussions about what "success" means. (Mitchell, all)
- Process for granting CVS write access (might not be 0.4 timeframe).
- Assist other working groups in developing and implementing community goals
Proposed results goals:
- One or two people doing QA stuff.
- One or two people working on the repository.
- Tangible contribution from volunteers resulting from process goals.
- Develop nascent longer-term community plan (e.g. when do we need user testing?).
Note that some of the community group goals could easily be reassigned to be "Repository Group" goals.
Action items
- review past big-picture docs:
--
DuckySherwood - 04 Mar 2004