HI Marvin,
Let me try to reply on feasibility inline

On 2015-03-21 01:09, Marvin Humphrey wrote:
On Fri, Mar 20, 2015 at 3:57 PM, Alan D. Cabrera <[email protected]> wrote:

I was thinking that we could also come up w/ a standard mechanism to
announce a proposed release and for people to vote on them.
This could be incredibly helpful.  I've thought about it many times but have
kept it to myself because I don't have the tuits to deliver it.

Interface wishes:

*   Hook to LDAP for binding votes.
Very tricky, as STeVe was designed to hide what people have voted, even if you have disk access. I will see if there's a possible workaround for this, but I doubt it will be possible to determine <2 binding votes without giving away who voted for what. 3+ can be determined, I'm sure of that. As for the LDAP part, the pytest already tries to determine if a user is authed via httpd or not, so this could be extended to do some more magic.
*   Email sent out to dev list when vote launched.
Currently, every person receives a personal email with a vote link. That's part of STeVe's anonymity. I suppose what we could do is add a more open election type, that does not have the same level of secrecy
and bypasses the various security checks normally in place.
*   Automatic close at scheduled time if enough votes have been cast.
I think a smarter way would be to set it to remain open until N (binding) votes have been cast.
That should be easy enough to implement.
*   Autogenerated tally email sent out at close.
This would be one of the cron jobs I spoke of earlier in this thread.
*   No email sent with each vote.
See above. It's a possibility, but requires us to invent a new word that means "YNA but not secret". I think what we could do is have a page that autogenerates a vote ID and sends to an email address. That way, each email gets one vote, and if it's hooked to LDAP, your apache.org email would give you a binding vote or some such.
*   Scheduled "nag" emails: current tally sent to dev list every 24 hours
     starting 24 hours before close and continuing until the vote passes.
Cronjob stuff ;)

With regards,
Daniel.

PS: I am of a forgetful nature and with a fleeting memory, so please do nag once in a while if I or the others don't pick up on your ideas. I think they are mostly doable, and make sense :)

Marvin Humphrey


Reply via email to