r3 - 08 Jul 2005 - 08:52:57 - LisaDusseaultYou are here: OSAF >  Projects Web  >  CommunityHome > CommunityPlan > HubNeeds

We know that non-staff hub developers are critical to the long term success of Chanler. We need to take the right steps to help foster community development of those elements, while remaining open to possibilities we haven’t imagined. We don't know what all of these steps are now, but we know some of the basics.

Our general approach is "organic" community development, for both hub and spoke developers. This means that: we will make our activities as open, transparent and permeable as possible; we are committed to being inclusive; we will encourage everyone interested to follow and participate in our development process, we will help people to help themselves, and we'll develop mechanisms necessary for people to get involved more deeply.

We'll interact through our general development channels -- IRC, bugzilla, mailing lists, code review and contribution. We'll get to know community members primarily through these interactions. It means that we will have an inclination to focus on those people who get involved first, and ask questions about their specific plans later. This may or may not be an ideal setting. We may provide inadequate assistance to potentially great contributors who seek personalized OSAF attention to their planning activities before being known in the OSAF community. We would prefer not to lose any potentially great contributors, but need to recognize the limits on our resources.

To encourage "organic" development of hub participants, we need the following are key requirements:

  • development is done publicly
    • discussions are public
    • decisions are documented publicly
    • code and bugs, etc are public
  • Interested parties are always able to follow development

  • Good Documentation
  • Interested parties have identifiable paths for getting involved:
    • submit patches
    • review work of hub developers
    • work of non- hub developers to have their code reviewed and checked in when it's ready
    • be involved in decision-making (potentially including authority for some decisions)
  • Articulated view of the "responsibility -- commitment" tradeoff from OSAF
  • Existing hub developers are open and interested in new people
  • Existing hub developers have a system for to evaluate and grant permissions
    • Bugzilla
    • Code review
    • CVS access
  • Existing hub developers have a space in which they can speak publicly with confidence. (The development process issue brief is to deal with the issue of determining "who owns what" and what "ownership" means.)

-- MitchellBaker - 05 Jun 2003

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.