r3 - 07 Jul 2005 - 22:26:54 - LisaDusseaultYou are here: OSAF > Journal Web > TopicOutline20030604? > CommunityPlanReleaseZeroPointOne
Community Plan -- 0.1 Release
Community Goals for the 0.1 Release
-
Testing
-
What needs to be tested
- builds? We should probably build a GLIBC 2.2 and a GLIB 2.3 version of Chandler.
- Ports?
- selected APIs ( or is this design only)
- parcel framework via sample parcels
- Do we provide tools and guidance -- smoketests,
- What doesn't need to be tested -- database?
-
- Recruiting Volunteers -- identifying a manageable number of people who appear to have immediate helpful input
-
2-3 people knowledgeable involved in architectural discussions
- 2-3 people testing the parcel framework by writing sample parcels and highlighting problems
-
2-3 people involved in QA and bug-tracking
-
Some criteria for sorting bugs into useful and not. For example, if it's a bug that says "I'd like to see feature X" or "I don't like the icons" we just dump it.
- Goals in Chao's 0.1 Release doc: http://twiki.osafoundation.org/twiki/bin/view/OSAF/FPRPurposeAndGoals
Effects of 0.1 Release
-
CVS Source Repository
-
should become open at the Initial Release (Alternative is to stay closed and due only milestones and releases, which is bad for transparency and not recommended
-
-
Bugzilla
-
Bugzilla should become a community tool, open for non-staff to file bugs?
- Shall we provide assistance in filing good bugs -- a helper form requiring platform, steps to reproduce the problem, etc. </li
- BugzillaHelper as an example
- Does desired feedback fit into the bug system, or elsewhere?
-
-
Some questonns about builds and releases
- When will the next publicly available build be?
- Will we continue to do internal releases?
- Will we do periodic builds that are publicly available even though not polished as releases?
- Will we want testing on all such builds?
Proposal: Post-0.1 Release "Community Week"
Let's dedicate time immediately after the 0.1 release to focus on the community. The 0.1 release will be out, people will be interested, this will be a great time to prove we're "for real" in terms of community engagement as well. If we plan this right, we can avoid piecemeal responses that feel like irritants to us and grudging, harried response to the community. We don't an immediate deadline staring us in the face, let's take advantage of it. Our goals might include:
-
Have fun. Talk about long term goals. Think about what could be. We all joined this project for a reason, let's enjoy the fact that a whole bunch of people really care about what we're doing, want to know more, and might even help us get there.
-
Get to know the current community. Are they potential programmers? Or mostly users who want to see features?
-
Look for people who can help us now. As sounding boards, for sanity checks, for assisting OSAF staff with outstanding tasks.
To do this, we can do things such as:
- Schedule some online chat sessions. For example, let's schedule an Architecture chat, have appropriate OSAF staff to discuss the block diagram and answer questions. Same for Katie and the calendar parcel, and probably John and the parcel framework, etc. Chat sessions result in logs, which can be the basis for additional, rough documentation. Maybe we can find someone to clean up the logs and end up with a set of FAQs.
- Respond to bugs.
- Focus on the discussion forums Use this time and questions to take material on the twiki and get it out. Having a bit of time will allow us to provide this info in some context.
- Distribute Bobble-heads of our favorite staff and community members.
Ongoing Communications Effort
After this initial focus, we should define some ongoing mechanisms by which we remain more involved with the community. Some possibilities include:
- Weekly Online Chats, hosted by Ducky
- Evaluate internal info -- should it be public?
- Scope of staff effort -- what do we hope for?
- Metrics? (time per day as a bad example)
- Outreach to core technology communities
- Python
- wxWindows
- database, once selected
- Jabber, once confirmed