Henrik Bechmann wrote: > Step 1: declare current release out of beta > Step 2: identify a (for real) webmaster to take responsibility for > pmwiki.org > Step 3: create a development.pmwiki.org subsite, where we can set up a > wiki to begin a formal planning process (and set up a TRAC repository > for the current code base) > Step 4: fire up pmwiki-devel for *lively* discussions about related > issues: planning, feature discussions, organization, decision making, etc. > Step 5: follow-up from steps 1-4 <grin>... I agree that these steps are foundational -- although not so much on [2], but that depends on the definition of webmaster.
Key for me is creating a structure beyond Pm (but not excluding Pm) that encourages and manages development within the core. I believe it's this level of community which is missing. This I think will encourage more activity in the dev and user communities. As others mentioned, developer documentation needs to play a role here, and with the help of some of the more experienced Pm'ers. And contrary to other opinions, I think Trac would be a positive start, communicating both what's done, but what's planned. The key issue is whether anyone beyond the voices heard so far has any interest in *actively* participating -- therein lies the key. ~ ~ Dave _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
