<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> the (future SVN) repository a bit<br>differently: A "default member" would just get write access to one
<br>(SVN) directory. Then e.g. Luke could put his abstractions and the<br>mmonoplayer and whatever comes up there, pd-extended could still<br>collect it. I guess this would be sufficient for a large number of<br>developers. (Many people recently added as members, like Eric Lyon
<br>etc., "just" put their externals and abstractions there and all is<br>fine.)</blockquote><div><br><br>I agree strongly with this. As an externals developer, I have no need or desire to have access to the Pd core code except as a spectator. One benefit of two-tiered access (1 for people working on core code, 2 for people like me) is that there would not need to be major discussion about adding externals developers, since you would not need to worry about them wandering into the Pd code and accidentally turning into Microsoft Word :)
<br><br>Cheers,<br><br>Eric<br><br></div><br></div><br>