CVS Access Lists WAS Re: [PD-dev] sourceforge tarball problem

[Hans-Christoph Steiner]

> whats this fear of losing control? why is everyone publishing under gpl
> or something similar then?
> 
> the cvs is not the only place to store things, people also have private
> harddisks etc. if i m not happy with the way something works, clone it,
> rename it, hide it or re-publish it, whatever .. the whole point of open
> source licensing, again?

Sure, anyone can edit the sources to the linux kernel.  But there is only
one person who actually says yes or no to what goes into the official
kernel. (OK, probably more than one these days).  This is the control that
I am speaking of.  Most open source projects have such overseers.  We want
to encourage people to keep the 'official' version of their code on the
pure-data.sf.net CVS, that is why I think this option is important.

Plus if we just have a free-for-all development, there is a danger of
chaos and the need to constantly rollback changes that people made to
software they didn't really know enough about.  Permissions/access
controls are excellent tools for preventing mistakes.

.hc


	zen
	   \
	    \
	     \