RE: [VOTE] All community action items be listed in the Avalon STATUS file

[Leo Sutic]

Greg Stein wrote:
> Would you rather spend an hour trolling through the archive trying to
> figure out how people felt about an issue? Or simply hit the status file?
> What if a lot of time has passed?
>
> In Apache Commons, there is a status file that I can go and look to see
> what direction people were thinking back from day one. No need to find
> and crawl the archives. It's all neatly summarized.

Greg,

I completely agree with the *purpose* of using the STATUS file - both as an indicator of the current situation and as a log of what has been voted on.

However, I think it is a very clumsy way of doing it - I have to SSH to apache, fire up CVS, update STATUS, make my changes, commit them. That, in addition to the usual [VOTE/PROPOSAL/VOTE-RESULT] message that should be sent to the mailing list.

I have been thinking about getting the same functionality, but using Bugzilla (one bug per vote, add comments as the vote progresses, mark the bug as [VOTE] and you can query for it) or our brand new Wiki (put the STATUS file up as AvalonStatus, just surf in, edit and hit submit). We'd get the same functionality, but in a much leaner package.

That made it any clearer what I meant?

/LS


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>