nicolaken 2003/01/20 00:25:43
Modified: . STATUS.txt
Log:
Added latest votes and a precision on the STATUS file issue vote.
Revision Changes Path
1.15 +12 -6 jakarta-avalon/STATUS.txt
Index: STATUS.txt
===================================================================
RCS file: /home/cvs/jakarta-avalon/STATUS.txt,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- STATUS.txt 19 Jan 2003 10:39:24 -0000 1.14
+++ STATUS.txt 20 Jan 2003 08:25:43 -0000 1.15
@@ -71,24 +71,30 @@
The information about the authors will still be present in commit
messages and in the site credits.
[20020119]
- +1: nicolaken
+ +1: nicolaken, leosimons, mcconnell, leosutic,
+0:
-0:
- -1:
+ -1: hammant, proyal, jefft
o The STATUS file is a great mean of synching the community agenda.
To be effective, it must be uptodate, and I can't do it all myself.
Proposals should be entered as such, votes should have listed all
current votes and the vote start date, and when the issue item is
completed, the names of the voters are removed and it's resolved,
- positive or negative. Releases too should be listed.
+ positive or negative. Releases too should be
+ Votes and all action items that are placed in the STATUS file
+ are valid if done by their rules. In other words, the STATUS file
+ does not validate them in any way, it's just a community synch tool.
+ If something doesn't go into the status file, it still exists and is
+ perfectly valid.
I'm asking you, do you want that for each [Proposal] and [Vote]
and release there be an entry in the STATUS file, that has to be
updated by the original item proposal?
+
[20020119]
- +1: nicolaken
+ +1: nicolaken, leosimons, mcconnell
+0:
- -0:
+ -0: leosutic
-1:
o Coming up with a set of bylaws for the project
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
