[kde-guidelines] CVS - Attempt to summarise

[Ellen Reitmayr]

Jan and me were in Prague last week, and unexpectadly could not send
emails. So now some comments and an attempt to summarise the CVS
discussion:

On Fri, 2004-10-29 at 23:44, Lauri Watts wrote: 
> In fact, I didn't understand the reasoning then either, I just haven't 
> remembered to raise the question.  Thomas explanation seems to explain it 
> sufficiently, and I agree that editing previous versions once a new version 
> is finalised is unlikely to happen, so we could simply turn off 
> auto-generation of those older versions (if there is any auto-generation 
> going on), move the last generated version to a subdirectory named for the 
> version and provide links to them.

Sounds reasonable to me. Should we then create a subdirectory /arch or
/versions? What way is that usually handled? 

> [...]  The maintainers are the ones who will be working in the sources, 
> so until and unless they find it unmanageable, the point is moot.   At that 
> point, unless there is a really compelling reason to change from standard KDE 
> procedures, then we won't.  It's non negotiable because it's completely and 
> utterly not relevant to the issue to be discussed.

Both, Jan and me, do not have too much CVS experience. It won't be a
problem for us to manage the source files once everything is set up
properly. But by now, due to that lacking experience I am not yet able
to say what is the best way to manage those sources (this will hopefully
change within the next few months 8-) ). That's why with respect to this
discussion, Jan and I should rely on your experience and the KDE
standard procedures.

Let me now summarise what I understood everybody agreed on right now:

[1] The directory structure will be 

/ 
        /common/
        /src/ 
                /index.docbook
                /accessibility/  
                /usability/
        /simple
        /plain
        /html 
        /pdf


[2] plus a /archive/ or /versions/ directory (?)


[3] Images (that are included into the contents, no header images) are
version-specific and should therefore be included into the source tree.
Should it be /src/images/ or rather /src/accessibility/images/ and
/src/usability/images/ ??


[4] Auto-generating will be turned off. Once a new version is released,
generating will be done by the maintainers manually. Wording/spelling
may be changed on the fly.


[5] Versioning will be done by simply copying the old version to a
subdirectory with the respective version number, and be linked to.


[6] Accessibility of the 'normal' html pages should be reviewed by Olaf,
please.



**** Did I get everything correctly? ****


Greetings
/ellen






-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.kde.org/pipermail/kde-guidelines/attachments/20041101/0c15780b/attachment.pgp