[Skencil-devel] skencil website migration

[Torsten Irländer]

Hi all, 
After migrating the mailinglist, we will migrate the website sources to wald 
next. 
In this step we like to take the chance to make some improvements to the 
source layout of the website as the situation now seems not to be the best.
This improvement is described in detail in the attached document.

Migration process will start now and will be hopfully finished next week.

best regards 
Torsten   
 
-- 
Torsten Irländer                                    Intevation GmbH

torsten.irlaender at intevation.de
http://www.intevation.de/
-------------- next part --------------
Proposal for Skencil Website SVN repository layout and move
===========================================================
Torsten Irländer <torsten at intevation.de> 
Bernhard Reiter <bernhard at intevation.de>
(20060331)

NOTE: This affects only the website of Skencil!
Skencil' source has already be put into SVN 
https://wald.intevation.org/projects/skencil/ .

For the website we want to take the chance to make some improvements.
Wald.intevation.org offers a SVN repository,
supports the upload of pages with rsync and dynamic pages with mod_python.

1. Current state

There are three CVS modules for Skencil's Website in Savannah:
	SW: cvs.savannah.nongnu.org:/web/skencil
		This is displayed directly on http://skencil.nongnu.org/
		by an automatic process of Savannah.
		Some files are only saved in there, e.g. the screenshots.
		The others are produced by sources in SSO.

	SSW: http://cvs.savannah.nongnu.org/viewcvs/skencil.org/?root=skencil
		Source for the current website.

	SSO:  http://cvs.savannah.nongnu.org/viewcvs/skencil-web/?root=skencil
		Old website source for pages server until 2004 or so.

* In SSO are page source that can be postprocessed by a python script
  and the result then uploaded (=checkedin) to SW.

* Because of original files in SSO, 
  there is no strict seperation in source and target.

* Some parts of the site are large and are needed seldom,
  but must be checked out even if i do not want to change them.


2. Target state

* It would be nice to have a strict seperation in source and target.
  Thus only one repository for the source would be needed, 
  because Wald support rsync upload. For savannah the target files
  had to be checked into SW anyway, requiring a second repository.

*  They layout should make it easy to only checkout the page part
   that changes more often as opposed to the gallery part which
   changes less oftern.
   
* The generated website is located outside the svn-working directory,
  as we do not want to have the generated website in the svn repository.

* Archive SSO as tarball of the cvs repository. 

3. Possible SVN layout for the website sources

website
    |-- tags
    |-- branches
    |-- trunk
        |-- pages (index.html,news.html...)
        |    |--faq 
        |    |--images
        |
        |-- screenshots
        |-- gallery

Rational:

* The documentation source is already part of the application source.
  Thus they do not need be be in the web source repository.

* Patches should be kept in the wald trackers.

* Release notes should be kept close to the released files
  and 

* SSO is only interesting for historical examinations, thus does not
  need to be in the new repository.

* If a completely new version of the website is made, the old versions
  are kept in the branches folder