Design Process : Development Framework

Here we collect how the tree/repository will be set up and which tools are needed/required for working on lumiera.

I am always in favor of getting the basic project organization and all scripting up and running very early in a project. I would like if the project would take a rather conservative approach on the required Libs and Tools, so that finally, when we get into a beta state, we can run/compile on the major distros without too much pain. I wouldn’t completely abandon the idea to target *bsd and osX as well later on.

I would propose to move Doxygen to “required”. The Idea to use SCons sounds quite appealing to me at the moment. Besides that, I think this RfC could be moved to “Draft”.

Moved to Draft. For Developer documentation I would prefer doxygen. For user documentation we can make a similar/same think like nicolasm did for cinelerra2, means wiki for edits, git to maintain it, based on gnu texinfo. Texinfo is quite limiting in its capabilities but it suffices, seeing the current cin2 docs, i say its rather well done.

We need to factor out some of the proposals from this page to subpages (scons, documentation, testing,…)

It would really suck if we have to go through the experiences described in the article »Stop the autoconf insanity!«. I have experienced parts of that in the past. I have only some beginner experience with writing autotoolized projects (mostly based on trial-and-error) and no experience in any other build system (such as scons). As such, I still believe that autotools can be manageable (for me personally) once the initial hurdle of learning is overcome.

I all for Doxygen documentation. Related to documentation are Splint: Annotation-Assisted Lightweight Static Checking. See also descriptions of annotations (in comments). I suggest that we consider using such a tool for QA. Like ct said, this should be discussed in a subpage.

I agree with using currently bleeding-edge tools.

We have now a “compatibility wiki”, finalized this proposal