If STeVe still has the goal to be a generic voting system for use by not only the ASF but others as well, then it makes sense for us to continue as is.
If, instead, the goals for STeVe have changed, or we have realized that the only realistic users for STeVe are, in fact, the ASF, then why not have Whimsy absorb STeVe as well? Certainly there is duplication, etc... which would make that viable. Far from being a collection of "absolutely unnecessary yet often quite handy applications", Whimsy is in fact becoming a core requirement for the ASF, and so unless STeVe really is going to stand on its own, it does seem to make sense to fold it into Whimsy. This might also encourage Whimsy to grow beyond its still singular (mostly) developer mode. > On Nov 16, 2015, at 4:18 PM, Sam Ruby <[email protected]> wrote: > > On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski <[email protected]> wrote: >> I wonder if it's time to move STeVe to be under Whimsy... > > Could you explain what you mean by that? That's not to say that it is > not an intriguing thought, but at the moment there is little overlap > in development communities. > >> Or is the goal still to have STeVe be generic enough for >> other external users? > > Independent of how we structure PMCs, I would hope that remains the goal. > > - Sam Ruby > >>> On Nov 12, 2015, at 10:25 AM, Daniel Gruno <[email protected]> wrote: >>> >>> To wit, the admin interface on vote-wip is found at: >>> https://vote-wip.apache.org/admin/ >>> >>> With regards, >>> Daniel. >>> >>> On 11/12/2015 04:22 PM, Daniel Gruno wrote: >>>> On 11/12/2015 04:12 PM, Sam Ruby wrote: >>>>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno <[email protected]> >>>>> wrote: >>>>>> Gentle ping - it would be nice to get some feedback here :) >>>>>> >>>>>> With regards, >>>>>> Daniel. >>>>>> >>>>>> On 10/11/2015, 3:13:38 PM, Daniel Gruno <[email protected]> wrote: >>>>>>> >>>>>>> So, let's start by gathering a bunch of people interested in configuring >>>>>>> and monitoring an election (with multiple issues to vote on), and then >>>>>>> let's get some folks to volunteer as voters. >>>>> >>>>> Are there instructions someplace for setting up and monitoring an >>>>> election on your own hardware? >>>> >>>> http://svn.apache.org/repos/asf/steve/trunk/pysteve/GETTING_STARTED.txt >>>> >>>> It's a very minimal install guide. I'll see if I have spare cycles to >>>> elaborate a bit on how to install, but in my experience, it's just a >>>> matter of pulling the pysteve contents into a CGI-enabled httpd instance >>>> and having a standard elasticsearch (if you choose to use that) DB >>>> running on the same machine. >>>> >>>> In the case of ASF's vote-wip instance, it uses LDAP auth which then >>>> goes to steve.cfg and checks which rights you have on the machine. I >>>> have set up you as an admin of the vote-wip instance, so you should be >>>> able to see/do everything there. >>>> >>>> As for monitoring: >>>> >>>> When you create an election, you specify who is designated as monitor of >>>> the election. Right before you invite everyone to an election, you click >>>> 'Cue monitors' in the admin interface, and they will receive a link to >>>> the monitoring site along with some checksum values. This link stuff >>>> needs some improvements (some uniqueness added to it), but the basics >>>> work as intended. >>>> >>>> With regards, >>>> Daniel. >>>> >>>>> >>>>> - Sam Ruby >>>>> >>>> >>> >>
