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

[Nicola Ken Barozzi <ni...@apache.org>]

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.

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?

+1


-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Greg Stein <gs...@lyra.org>]

In article <00...@Lagrange>, "Leo Sutic"
<le...@inspireinfrastructure.com> wrote:
>...
> -0 Seems like even more bureaucracy that will cost more than it
>    will help.
> 
> /LS

Mandating the use of a STATUS file can certainly be a bit ham-handed. But
*using* a status file is far from bureaucratic. 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.

Multiple that time savings across the entire community, and the status
file can be a huge winner.

Cheers,
-g

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Leo Simons <le...@apache.org>]

Nicola Ken Barozzi wrote:
> But coding conventions are voted on. This is the same thing.

OK then :D

+1 on making it a convention that votes, votes results, releases and 
items of similar importance are listed and kept up to date in the STATUS 
file.

cheers,

- Leo



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Leo Sutic <le...@inspireinfrastructure.com>]

> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] 
> 
> Leo Simons wrote:
> > Nicola Ken Barozzi wrote:
> > 
> >>
> >> 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.
> >>
> >> 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?

-0 Seems like even more bureaucracy that will cost more than it
   will help.

/LS


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Nicola Ken Barozzi <ni...@apache.org>]

Leo Simons wrote:
> Nicola Ken Barozzi wrote:
> 
>>
>> 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.
>>
>> 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?
>>
>> +1
> 
> 
> +1 on the idea and on creating general agreement where everyone updates 
> the STATUS file, -1 on some kind of _requirement_ or even having a vote 
> about this.
> 
> If something doesn't go into the status file, does it then not exist?

No, it still exists.

> Is 
> it required you put something in the status file when your work on it? 

No. It's about proposals, votes, releases.

> Can I challenge a vote because it is not in the status file and I wasn't 
> monitoring the list at the time of voting? 

No. A vote on the mailing list is valid, the status file is just 
accounting, not the thing per se.

> It is all just hairy if you 
> formalize. It's sort of like a coding convention to me: apply it, but 
> don't trip over it when it doesn't happen.

But coding conventions are voted on. This is the same thing.

Votes are valid if done on the mailing list. Our convention would 
require in case this gets majority +1 ro add it to the status file.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Stephen McConnell <mc...@apache.org>]

I agree with the principal that status needs to be documented and that 
this is something we need to help out with.  I aslo agree with Leo that 
this is too close to being considered a reference.  The reference for 
things is vote counts and vote resoults posted on the list.

+1 (morally)
-1 (procedurally)

:-)


Leo Simons wrote:

> Nicola Ken Barozzi wrote:
>
>>
>> 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.
>>
>> 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?
>>
>> +1
>
>
> +1 on the idea and on creating general agreement where everyone 
> updates the STATUS file, -1 on some kind of _requirement_ or even 
> having a vote about this.
>
> If something doesn't go into the status file, does it then not exist? 
> Is it required you put something in the status file when your work on 
> it? Can I challenge a vote because it is not in the status file and I 
> wasn't monitoring the list at the time of voting? It is all just hairy 
> if you formalize. It's sort of like a coding convention to me: apply 
> it, but don't trip over it when it doesn't happen.
>
> cheers,
>
> - Leo
>
>
>
> -- 
> To unsubscribe, e-mail:   
> <ma...@jakarta.apache.org>
> For additional commands, e-mail: 
> <ma...@jakarta.apache.org>
>
>
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

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

[Leo Simons <le...@apache.org>]

Nicola Ken Barozzi wrote:
> 
> 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.
> 
> 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?
> 
> +1

+1 on the idea and on creating general agreement where everyone updates 
the STATUS file, -1 on some kind of _requirement_ or even having a vote 
about this.

If something doesn't go into the status file, does it then not exist? Is 
it required you put something in the status file when your work on it? 
Can I challenge a vote because it is not in the status file and I wasn't 
monitoring the list at the time of voting? It is all just hairy if you 
formalize. It's sort of like a coding convention to me: apply it, but 
don't trip over it when it doesn't happen.

cheers,

- Leo



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>