On Thu, 2012-04-12 at 12:46 +0200, kiorky wrote: > Hi, i was thinking with Chris Mcdonough about creating something like > the plone collective: > What's that ? That's may one be the most successful things in the > plone community for me. > > - http://plone.org/documentation/glossary/collective > - https://github.com/collective/ (new) > - http://svn.plone.org/svn/collective/ (old) > > Fortunately, This is reproducible for us. > > For those who are not aware of and don't want to open links, it > consists in giving a "meta repository" where all community members are > given read & write to all inner repo minor the "delete repo" thing. > This "meta repository" is not synonym of quality neither the contrary. > Focus is really on central community contribution. > For core quality concerns, use what's in pyramid organization. > The main goal is to centralize contributions. > > - This allow a central place to push your addons or pyramid > related software encouraging re-usability and inter contributions. > - One of the biggest problems, I found nowadays with pyramid is > the lack of consistence between packages. > The "pyramid collective" may lead to improve this lack as > developers/users will be more aware of the ecosystem and try to > integrate things among others. > - No contributor agreement required, welcome to everything without > some written implication. > > > How ? > > - We can create a git-hub organization inspired by the plone's > collective one.. > - To handle the read/write security problem, inspire ourselves > from this script: http://pypi.python.org/pypi/github-collective. > > How about existing packages ? > > - We may need to make some evangelism to encourage people to > migrate their add-ons from their private repos to the collective. > > In organization terms speaking, we will need some staffers to handle > the collective in pretty shape. > > - Managing organization members. > - Accepting pull requests from the "permissions.cfg" to create > repos on the github organization. > - Giving some sort of support. > > Also there is some docs on the collective administration there : > http://collective.github.com/
I'm very +1 on this, it's a good idea; I can't currently take on the task of being in charge of it though. We'd need a few somebodys to set such a thing up and manage it, promotes it, decide what goes in and what stays out, grants and revokes access, maintain something on pylonsproject.org that at least links to it, etc. Anybody want to do that? - C -- 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.
