I like the idea of a maintenance group. stef
On May 20, 2010, at 11:46 PM, Sean P. DeNigris wrote: > > > Yanni Chiu wrote: >> >> It's really up to each project to make it easy/hard to accept >> contributions. I don't see what outsiders could do to change that, other >> than to ask to become an insider. >> > > Ah, now I see what you're saying. I actually agree. My idea is to > encourage and default to w/r, not impose it. I assume that many projects > are read-only, not because of a desire of the maintainer, but just because > that's the default in SqS. Why not default to r/w, making life easier for > the community, and admins can select read-only if they want. > > > Yanni Chiu wrote: >> >> An idea comes to mind though. Maybe a "maintenance" group could be >> created. Members of the maintenance group would have write permissions >> to all projects. They would only submit code to make things work on >> different platforms, but would not wildly re-factor, change the design, >> add features, etc. That way, the admin/dev's would still maintain >> "control" of their project, but get help from the maintenance crew. >> > > Sounds interesting. > > Sean > -- > View this message in context: > http://forum.world.st/Community-Development-a-suggestion-tp2224670p2225365.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
