incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: the Voting Status monitor is overloaded
Date Fri, 15 Nov 2013 02:10:55 GMT
Thanks to those who did follow-up. That clears a bit.

Another plea from me to help you to clear the clutter:

I reviewed the mail archives for the outstanding ones
to see why the "Vote Monitor" did not detect their vote result.

I do not have time to correct them nor to tweak voter.py
but hope that others can utilise my work.

Here is a summary:

As expected in my original mail, some tallies added extra words
to the Subject, so tricked the monitor.

Others did not tally.

Others tallied but did not add RESULT tag.

Others did cancel but did not add CANCEL tag.

There were a few "community graduation" votes which were "Fwd:" 
but did not summarise. Perhaps voter.py could detect these "notices".

There were a few with common mis-spelings, such as the CANCLE one.

Thanks to Branko, the regex is nice. People could help to expand.

Some possible tweaks to voter/voter.py are flagged below.

Some situations could be cleared with a new RESULT or CANCEL email.

Please assist.

Notes:

--------
Release Apache Stratos 3.0.0 Incubating RC4

They added (passed) at the end of Subject.

--------
Release Apache Tajo-0.2-incubating RC1

Prepended tag CANCLE instead.
(FIXME: voter/voter.py needs additional code to handle such typo errors.)

(Now a follow-up has done a reply with CANCEL.)

--------
Apache Ambari 1.4.1-incubating RC1

No-one did summarise.

--------
Graduate Apache Marmotta from incubator and become a TLP

This was a community graduation vote.
Used "Fwd:" but not summarised.
(FIXME: perhaps voter/voter.py needs additional code to handle such "notices".)

--------
Apache Kalumet 0.6-incubating release (3rd try)

No-one did summarise.

--------
Usergrid BaaS Stack for Apache Incubator

No-one did CANCEL.
(A subsequent new thread was summarised, but this old one remains.)

--------
: Release Apache Sentry 1.2.0 incubating (rc0)

Was tallied but no RESULT tag.

--------
Apache Chukwa graduation

Was tallied and RESULT, but different thread with different Subject.

--------
first milestone release of Apache Drill (incubating)

Was tallied, but broke the thread and removed the VOTE tag.

--------
Graduate Curator from Apache Incubator

This was a community graduation vote.
Used "Fwd:" but not summarised.
(FIXME: perhaps voter/voter.py needs additional code to handle such "notices".)

--------
Release Apache Provisionr version 0.4.0-incubating, RC0

Was tallied and RESULT, but different thread with different Subject.

--------
Release Curator 2.1.0-incubating

No-one did summarise.

--------
Release Apache Wave 0.4 based on RC3

No-one did summarise.

--------
Accept Stratos proposal as an incubating project

Was tallied, and RESULT tag
but had "Re: " in between the tags
2013-06-20
(FIXME: voter/voter.py needs additional code to handle this.)

--------
Accept Apache BeanShell in the Incubator

No-one did summarise.

--------
Release Apache Mesos 0.11.0-incubating (RC1)

No-one did tag with CANCEL

--------
helix 0.6.1-incubating

Was tallied and RESULT, but different thread with different Subject.

--------
S4 0.6.0 Release Candidate 4

No-one did summarise.

--------
S4 0.6.0 Incubating Release Candidate 3

No-one did tag with CANCEL.

--------
Recommending DeltaSpike for Graduation to an Apache Top Level Project

This was a community graduation vote.
Used "Fwd:" but not summarised.
(FIXME: perhaps voter/voter.py needs additional code to handle such "notices".)

--------

---------------
David Crossley wrote:
> If the projects that are listed there cannot make the effort
> to clean up, then do not be surpised if your subsequent
> vote threads are overlooked. This is also not fair on the
> other projects, especially new ones.
> 
> -David
> 
> David Crossley wrote:
> > It seems that the brilliant "Voting Status" monitor
> > has fallen into disrepair. Partly due to people
> > not properly following up with a clear RESULT tally
> > and partly perhaps inadequacies of the monitor script.
> > 
> > Follow the top-left link from the Incubator home:
> > http://incubator.apache.org/
> > 
> > Items coloured any shade of orange need attention.
> > 
> > We all need to care for these tools to assist us
> > through incubation efficiently.
> > 
> > Would people who have an interest in each open entry
> > please review the email archives to see why your
> > result summary tally email was not detected.
> > 
> > Perhaps you forgot to prepend "[RESULT]".
> > Or maybe changed the email Subject too and so
> > confused the monitor.
> > 
> > If so then please send a followup to your VOTE thread.
> > That will cause the monitor to clear its backlog.
> > 
> > However, i do see some that should be marked as Resolved.
> > 
> > So maybe the script that does this scan needs tweaks
> > to pattern matching. The code is there for all
> > in the top-level of Incubator SVN.
> > http://incubator.apache.org/facilities.html#voting-status
> > 
> > Please add more instructions to the docs:
> > http://incubator.apache.org/facilities.html#voting-status
> > 
> > -David
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message