Le 12/04/2012 14:41, Domen Koz(ar a écrit :
My two cents:
Giving a big group of people commit access to addon packages results
in conflicts if intended commit was useful to everyone. Most simple
example is breaking tests for sake of being lazy and adding
functionality. It can be of course mostly avoided, but not prevented.
IMHO, it worth the risk as we may loose some coherence between
contributions by not having a common place to contribute. Many factors
can just be avoided like maintainer hitted by a bus, or dictator, or
diverging opinions. It's more easy to handle by just commiting stuff at
the revert/reset risk.
Having something like djangopackages.com <http://djangopackages.com> +
pypi classifier would achieve the same goal. Pull requests are also
easy to make, I would propose rather to have a good read about
preferred way of contributing to package maintainers.
Also managing permissions (or basically and configuration) for
organisations on github in PITA.
Cheers, Domen
On Thu, Apr 12, 2012 at 2:23 PM, Chris Rossi <[email protected]
<mailto:[email protected]>> wrote:
I don't want to discourage anyone from doing this, but my initial
thought, at least, is that the Plone collective came from a place
and a time where hosting your own code in public wasn't
ridiculously easy the way it is now. Now anyone can host whatever
they want on Github. Or Bitbucket, Sourceforge, Launchpad,
etc.... From reading the thread I do so that beyond just a place
to host there does seem to be a desire to have a sort of clearing
house that is one place people can go to to see what's in the
collective, which makes sense. But in this day and age, given the
options to host and distribute, that could be as simple as a web
page that acts as a registry for people's projects. Managing that
might be a little bit easier and be just as good. Just a thought.
Chris
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:pylons-discuss%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
--
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.
--
Cordialement,
kiorky
--
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.
