Hallo!
However we already have a huge amount of members, who all have access to the whole tree except Miller's branch, and I'd guess, that most of the developers only need to have access to their own directory so that their stuff can be checked out easily, can be included in pd-extended etc.
Maybe it would be better to organize the (future SVN) repository a bit differently: A "default member" would just get write access to one (SVN) directory. Then e.g. Luke could put his abstractions and the
[...]
Of course we would loose the possibility that everyone can quickly fix a bug everywhere, but then, I don't see this as such a big problem. There still would be "trusted core developers" with access to almost everything - or maybe we could let each user decide with an ACL file in her/his user directory, who should have access to it.
I think this is only a good idea if there were already problems, that other developers broke things ... which I cannot really remember. If not, it will only prevent some people from developing, trying to improve other code, improving the build system etc.
I see your point, but I think this is more appropriate for a project, where you really have some core developers (or maintainers) which work quite a lot on the code - but I don't think that it is like that in pd! (exception: millers main, maybe the pd-extended-release branch from hans and pd-devel-core)
LG Georg