From: Stefan K. <en...@ho...> - 2008-03-15 08:27:20
|
hi, I am main developer of buzztard (http://www.buzztard.org) for those who don't know. I'd like to discuss the cooperation proposal below: It would be great to have a separate buzzmachine source project (e.g. "buzzmachines" on sourceforge.net) to provide buzzmachines to all kind of projects (like buzé, buzztard and aldrin). The project should be buildable under linux (e.g. autoconf/automake) and under windows (msvc projects). The rationale behind: * being able to fix bugs in machines * make up-to-date releases * improve docs * merge in new presets Buzztard has some ported machines in a [http://buzztard.svn.sourceforge.net/viewvc/buzztard/trunk/buzzmachines/ svn module] right now. We have more sources, but they need cleanups and porting still. In case you are interested - lets not overenginer and do things step by step. Main focus is to have buildable sources in a sane structure. Below some thing that need to be discussed (its a bit linux centric, sorry): === Linux Releases === We need to agree on some details: * where to install the plugins? ** ensonic: $prefix/lib/buzzmachines * where to install the docs? ** ensonic: $prefix/share/docs/buzzmachines, $prefix/share/buzzmachines/docs * where to install the presets? ** ensonic: $prefix/share/buzzmachines/presets * do we want to keep 'generator' and 'effects' subdirs? ** ensonic: no * do we want to install unported machines (buzztards wrapper can use them too on x86)? ** ensonic: installing them in the same directory ($prefix/lib/buzzmachines) is ugly === Machine Docs === It would be nice to have docs in the same format and have same look. * html + css docs * docbook docs ** generate html ** not so easy to write ** not that beneficial for short documents * [http://docutils.sourceforge.net/rst.html rest] ** generate html ** easy to write === Merge Presets === We would need some tools to manage preset merging. We can have the default presets that we ship in the repository. When users contribute their presets, they need to be merged. The merging should skip duplicates and maybe warn about similar presets. === Adding new machines === How to handle new sources? Add new sources to the bugtracker. Once its ported to either win/linux it can be added to the svn. We would need some guidelines for cleanups before adding them. E.g. lot of machines where done as a copy of an existing machine. At least the main source should be renamed. Thats it for now. Thanks for reading until here. Ciao Stefan |