Driki - make the Wiki smile

Right now the SVN  contains selective copies of the various Drupal CVS repositories merged into a new directory structure that resembles/is an installable Drupal installation. The good side is, that installing a Driki is as easy as svn co svn://driki.ws/drikiroot/branches/SocialNet-7.04  . Also, copying the sources makes sure, that changes in a Drupal CVS will not affect a Driki  trunk/branch. This is important because a lot of modules are provided as "CVS snapshots".

The downsides are, that it is hard to track what has changed in a Drupal CVS because copying will remove the cvs information. It is also hard to quickly include security fixes (automatically ?) and new components like themes and modules.

 Instead I think we should do the following:

• check out the Drupal  sources from the CVS
• if a tag (version) is available we'll use it, if not we'll use the head (latest & greatest, subject to change without notice)

After this step we have a bunch of directories (or Eclipse projects) for the Drupal core, modules and themes.  Since Drikis come in different flavours, we need to create various Drikis from what we have. This is accomplished by a bunch of scripts (ANT)  that copy components from the checked out Drupal dirs into the Distros. After that the Distro can be versioned.

Advantages:

• Build process can be automated
• It's easy to include new stuff
• As long as we use tagged Dupal code, the distros are reproducable.

Disadvantage:

•  The main problem with this approach is that if two people build a Driki, the outcome might be different, becuase the Dupal CVS may have changed meanwhile