On Nov 29, 2007 9:14 PM, Ches Martin <[EMAIL PROTECTED]> wrote: > On Nov 28, 4:28 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > > > One meta-issue is that the Pylons Cookbook space has become the > > dumping ground for everything because it's the only space everybody > > has guaranteed write access. There are topics such as this, improving > > the Pylons core, etc, that aren't really Cookbook material. > > > > Likewise, the Pylons Community space has tutorials which arguably > > *are* Cookbook material. It has never been made clear what the Pylons > > Community space is for. Is it for marketing/branding/website topics? > > Is it a miscellaneous space for community members to put anything in? > > I agree on all points. I think the need to get some of those things > moved to the right places has been acknowledged, but the wider need > for clarification is a good point.
First we have to determine what the right spaces are. :) The Cookbook was meant to be the place for HOWTOs, tutorials, and code examples, and I'd like to limit it to that. This means several other topics need a home: - Miscellaneous - Project design space (the Superwiki to replace Confluence, CMS, CRUD & admin components) - Feedback to the core developers: how users like the current version, what they'd like to see in the next version - Pylons development version: how to make your app compatable, what works/doesn't work, what's coming. (This may be Cookbook material; but users might play a greater role if they had a structured place to provide feedback.) - Marketing Pylons / logo / Web site design - Job postings / jobs wanted - News (prob'ly belongs on the website but there is an empty page for it in the Community space; this may be a job for Planet Pylons) Once we get clarification on what the Community space is for, we can either move stuff there or to new space(s). Every idea starts out small, so we at least need a miscellaneous space, whatever it's called. There's a part about Community that needs to be distinguished from the miscellania: announcing what the community is and what channels are available, how to get involved, what the community structure should be, and a place to build new modes of community (e.g., sprints). Maybe news about what different parts of the community are doing. So I lean toward limiting the Community space to things like that. Non-technical stuff (e.g., marketing) is currently in the Community space; that seems like a good place for it. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
