Documentating our progress

[Aaron J. Seigo]

hi all...

i'd like to volunteer to set up an area on the dev wiki[1] where we can have 
the following set of information for a start:

- a matrix of the svn modules (kdelibs, kdepimlibs, kdebase, kdeedu, etc) 
noting their scope and current release manager. i'll create the matrix with 
mostly blank areas and then each of us can fill in our own bits, leaving us 
with the blanks. when a release is set to roll, we can then use this same 
matrix to record status.

- outstanding application requests. this would let us keep track of issues in 
our modules such as okular/ligature, gwenview, etc... my concern is that 
right now i'm keeping most of these things in my own head and taking action 
when it seems there is consensus. this is an amazingly brittle process and it 
gives me the willies.

- 4.0 release milestone targets? this might be more appropriate on the 
Schedules pages, but it has occurred to me that a scratch area to record 
less-than-final-but-generally-gained-consensus-on-this-list milestones

in your opinion, is this is a good idea, unnecessary, a really stupid idea?

[1] http://developernew.kde.org/Projects/TechnicalWorkingGroup ? i debated 
putting it on the policies page, but i'm not sure that's the best place for 
it; what do you think?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/release-team/attachments/20070125/bc7c197f/attachment.pgp