I think the underlying issue is this. If you are entering an open source project with the idea that it is either desirable or possible to prevent forking, you are in the wrong place. Its not that open source is the bees' knees necessarily, but it is what it is, and its the essence of it that forking shall be possible and open to everyone.
It may be hard to get one's head around this, if one is working in the traditional commercial licensed and paid software model. And it may not be all that great. But that is how it is. If you think its important to limit forking, don't even think of doing a project as open source. Its 180 degrees in the wrong direction. Peter Björnke von Gierke wrote: > > On 20 Oct 2009, at 23:34, Richard Gaskin wrote: > >> Are there any ways to ensure that a common pool doesn't get >> fragmented like that? > > no. > > its _intended_ to be fragmented. .... > -- View this message in context: http://www.nabble.com/Calling-all-open-source-developers-tp25961091p25997496.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
