Hello,
I've always thought of the pure-data CVS as a place where developers work together on code as a common platform. People who want to be independent can easily make their own repositories, like Gem, PDP, grill, etc. Then for Pd-extended, releases of code that is in other repositories can be imported into pure-data CVS.
I always thought of the pure-data CVS as a market place where everyone can put their open source projects like libraries of externals, so a user can find them there und do not need to make a own web presence and CVS/SVN and also make it easier to make an extend release or for everyone to build their own extended version of pd.
This is why we put the iem-libs in there and not in the IEM-Opensource http://sourceforge.net/projects/iem repositories. The problem that every developper change the source if we cant react in an proper time was because we trust in other developers unlike some other projects like PDP, grill or GEM...
A lot of libraries are no longer released separately from Pd- extended, so it is something of a standard platform. There isn't anything else like it, so it's the defacto standard at least.
But they are still in CVS so they are released as head and if somebody need it, it can be fixed if something is broken, so these libraries are in my opinion not dependent on "pd extended".
BTW, I also like to state, that I prefer as less dependencies from one project on another if not depended on shared resources other than build systems, eg. Makefiles in the parent is really a mess to include this externals in a project.
I think, if we solve this problem the decision of how to organize the code will be clear.
mfg Winfried Ritsch
PS: Who askes the developer on sf on transition. I have no admin rights until now, so I think someone from the admins should do the job.