Re: Making GNOME CVS more usable

[Seth Nickell <seth eazel com>]

I'm in the process of doing something similar to this...I've already
created brief descriptions for most of the projects in CVS, and have
just started working on dependencies. Thus far I am working in a single
heirarchical XML file (which also categorizes the modules according to
function and some other things), but it would be trivial to write a
little program that splits the XML file into files for checking into
individual modules.

If you're interested in working with me on this (anyone!) I would
greatly appreciate it...its a big body of rather repetitive work ;-)

-Seth

Matthias Warkus wrote:
> 
> OK...
> 
> This was proposed a long time ago already, but I thought that we could
> maybe discuss this again.
> 
> Every module on GNOME CVS should contain a file, called maybe
> "SYNOPSIS" or such, describing in a short paragraph just what that
> module is and does. I propose also adding a file "REQUIRES",
> describing all other CVS modules and/or external libraries the module
> requires.
> 
> Scripts could use these files to create a module catalog and even a
> dependency tree.
> 
> I would actually volunteer to create SYNOPSIS and REQUIRES files
> everywhere they do not exist. I'm sure we can find someone to write
> the scripts, too.
> 
> What do you think?
> 
> mawa
> --
> Knieschutzskater!
> Kommunalwähler!
> Komplettlösungsspieler!
> Klarsichtumhüller!
> 
> _______________________________________________
> gnome-hackers mailing list
> gnome-hackers gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-hackers

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers