And who is the Linus Torvalds of Opensim?
I understand the existence of a core team, I understand too the existence of a "secret" list for organization purposes (for example what Adam says about voting a new comitter). But some kind of decissions (i.e. what should or should not be included in core, what to change or not to change on public interfaces...) must be public. Usually there are lots of other os projects giving value to the main project and their voices should be taken into account. Don't misunderstood me, please, I am not trying to say that "opensim is ruled by some kind of supercool guys with superpowers and the rest of people are just bullshit", personally I am comfortable with the project management, but maybe taking care with some pollitical or image questions will be necessary to increase both high valuable contributions and project popularity. To manage political stuff like this sucks, but that's the difference between community and enterprise, I think. Maybe it's time to define who is who, and how to do this kind of things before the monster grows up. Anyway, as with hundreds of os projects, anyone could make a fork and follow his/her/their own rules. Please excuse me if I looks like some kind of Captain Obvious :-P Greetings 2009/10/20 Teravus Ovares <tera...@gmail.com> > This does not validate your argument. Your argument was that the > advent of the distributed source control system made the 'commit right > vote' obsolite, however, in the project that spawned said distributed > source control system, there's a benevolent dictatorship. > > My argument was that the source control system doesn't dictate the > type of community an open source project has. If it did, then the > Linux kernel wouldn't be a benevolent dictatorship. > > Regards > > Teravus > > On Tue, Oct 20, 2009 at 3:41 AM, Edward Middleton <emiddle...@bebear.net> > wrote: > >>Edward Middleton wrote: > >>> Frisby, Adam wrote: > >>> > >>>> --- > >>>> From the excellent F/OSS guidebook: > http://producingoss.com/en/consensus-democracy.html#electorate > >>> I think the quote is a bit out of context, the book was released in > 2005 > >>> when most people were using centralized version control systems CVCS > >>> like subversion. I can understand making a big deal about commit > access > >>> (or rights if you want to put it that way) when you are working with a > >>> CVCS because it is pretty constraining to work it, but aren't you > >>> moving/have moved to a DVCS[1] (i.e. git) where having commit access > to > >>> the central repository is something more akin to being the release > manager. > > > >> [snip: references to Linus and Benovolent Dictator Governance Model] > >> > >> In conclusion, the quote was not out of context. This type of > >> community is alive and well /currently/ in the Linux kernel. ... > >> > > > > The quote was in relation to the Consensus-based Democracy (the opensim > > political structure?) which in most projects has changed significantly > > with the advent of DVCS. Maybe this might be more helpful[1]. > > > > Edward > > > > 1. http://drnicwilliams.com/2008/02/03/using-git-within-a-team/ > > _______________________________________________ > > Opensim-dev mailing list > > Opensim-dev@lists.berlios.de > > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > _______________________________________________ > Opensim-dev mailing list > Opensim-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/opensim-dev >
_______________________________________________ Opensim-dev mailing list Opensim-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/opensim-dev