Things to sort out before merging
"""""""""""""""""""""""""""""""""

 + Verify ideal buildsystem and concepts
   - Ok with idea that SPEC owner owns SPEC file, and you have a builder per platform ?
   - Ok with idea that we build decentralized and have a central repository manager ?

 + Naming of repositories
   - Ok with idea that we will have 3 ?
   - Ok with the idea that the 'stable' is a subset of 'testing' which is a subet of 'unstable'
   - What names are we going to choose ?
        unstable/testing/stable is bad idea

 + How to build merged packages ?
   - If ok with a single builder per platform (dist/arch)
     Easy to merge, we just specify who's responsible for what
   - If not ok, how to synchronize build environments

 + Build system
   - Depending on whether the ideal buildsystem setup is accepted
   - Naming for each component  (centralized, decentralized)
	'Hub' for centralized repository manager
	'Farm' for decentralized build system
   - Who and how implemented ? (Dries/Dag using python ?)

 + Subversion access and management
   - Are we going to have strict access control ?
   - Who's going to maintain it ?
   - Can we have a mailinglist/log with all the commits ?
   - Is everything backupped ?

 + Website
   - 2 parts, enduser and developer part
   - Bug tracking system ?
   - What technology ? Developer part needs integration with 'Hub'
   - Who is going to have access for website development ?
   - How are we going to maintain this ?