On 9/5/07, Juuso Alasuutari <[EMAIL PROTECTED]> wrote: > That gives me a thought. > > Please excuse me if the following sounds like it's too central > management-based, and it may well be that. But if we as a community would > take more responsibility for managing plugin sets written for specific > purposes, perhaps we could reduce duplication of work and help people > concentrate on shared codebases. > > I'm not suggesting that individually written, "external" plugins and plugin > sets should be considered fringe material, let alone shunned. But seeing how > the Linux kernel community works, I think that creating something like "The > Linuxaudio.org Plugin Collection" could benefit a common purpose. > > There could be separate sets for filters, delays, reverbs, oscillators, etc, > all being individual parts of a larger common code repository. And individual > ("external") developers could actively campaign for the inclusion of their > plugins and/or code refinements to the said plugin sets. Additionally, the > linuxaudio.org plugin set developers could keep an eye on new and promising > plugins, and approach their developers in hopes of gaining new contributions. > > Of course the whole purpose of such a centrally managed plugin repository > would be to give birth to Very Good Code. That implies that any contributions > would need to adhere to accepted common standards and practices, just like > contributions to the Linux kernel need to adhere to the standards and > practices of the kernel community. > > Juuso
You took the words right out of my mouth, I can only agree ;-) __________________ Marc-Olivier Barre. _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-dev