You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@steve.apache.org by Daniel Gruno <hu...@apache.org> on 2015/11/12 15:57:00 UTC
Re: Mock tests at some point?
Gentle ping - it would be nice to get some feedback here :)
With regards,
Daniel.
On 10/11/2015, 3:13:38 PM, Daniel Gruno <hu...@apache.org> wrote:
> Hi folks,
>
> I know we're quite a way from actual election time, but I think it might
> be worth having us try some mock elections at some point soon, so make
> sure the new pysteve system is up to the task and possibly identify any
> nits in the system that we can fix.
>
> As I wrote earlier this year, we have a new machine for conducting votes
> on, located at https://vote-wip.apache.org/ - the admin interface for
> this (for setting up elections etc) is at
> https://vote-wip.apache.org/admin/ and uses the regular ASF LDAP creds
> for login.
>
> Currently, Jim and I have administrative rights there and some CouchDB
> people have access to set up elections. If you're on the STeVe PMC and
> you'd like to give tinkering with the system a try, please speak up so
> Jim or I can add you as an admin in the system.
>
> What I'd really like for us to do is make some mock elections of various
> types (STV, yes/no/abstain) and invite some people to try out the test
> election, so we can make sure that:
>
> 1) Things in general work
> 2) Setup is something multiple people can figure out
> 3) The UI is intuitive
> 4) Vote tallying works as intended
> 5) Vote monitoring works as intended
>
> 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.
>
> WDYT?
>
> With regards,
> Daniel.
>
------
Sent via Pony Mail for dev@steve.apache.org.
View this email online at:
https://pony-poc.apache.org/list.html?dev@steve.apache.org
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
It goes to show that community building is not the same as coding.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Tue, Nov 17, 2015 at 12:06 AM, Sean Kelly <ke...@apache.org> wrote:
> The total of two---count 'em, 2---threads on the user@steve.apache.org
> mailing list since December 2014 might be an indication of a lack of
> outside interest.
>
> --k
>
>> Jim Jagielski <ma...@jaguNET.com>
>> 2015-November-16 at 3:33 PM
>> 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.
>>
>>
>>
>> Sam Ruby <ma...@intertwingly.net>
>> 2015-November-16 at 3:18 PM
>>
>> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org> 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<hu...@apache.org>
>>>>>> 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<hu...@apache.org>
>>>>>>> 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
>>>>>>
>>>>>> Jim Jagielski <ma...@jaguNET.com>
>> 2015-November-16 at 3:12 PM
>> I wonder if it's time to move STeVe to be under Whimsy...
>> Or is the goal still to have STeVe be generic enough for
>> other external users?
>>
>>
>> Daniel Gruno <ma...@apache.org>
>> 2015-November-12 at 9:25 AM
>> To wit, the admin interface on vote-wip is found at:
>> https://vote-wip.apache.org/admin/
>>
>> With regards,
>> Daniel.
>>
>> Daniel Gruno <ma...@apache.org>
>> 2015-November-12 at 9:22 AM
>>
>> On 11/12/2015 04:12 PM, Sam Ruby wrote:
>>
>>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org>
>>> 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<hu...@apache.org> 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
>>>
>>>
>>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/08/2015 04:45 PM, Pierre Smits wrote:
> Hi Daniel,
>
> Am I not already contributing? But with respect to the upcoming tests;
> according to the definitions in various documents I don't qualify.
I'll have to respectfully disagree with the last bit there :)
Anyone can participate in UX tests here, you don't have to be
committer/PMC to do that. It will be mostly a user experience and
usability test to determine any flaws or non-niceties in the system.
With regards,
Daniel.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Tue, Dec 8, 2015 at 3:00 PM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 12/07/2015 03:50 PM, Pierre Smits wrote:
>>> The only thing I see at that url (https://vote-wip.apache.org/) is a big
>>> fat logo, which is nice...
>>>
>>> But it doesn't enable me to do anything obvious. Maybe I am missing
>>> something.
>>
>> This is a BTW: Does this mean you'll be interested in helping out with
>> the upcoming tests? :)
>>
>> With regards,
>> Daniel
>>
>>
>
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
Hi Daniel,
Am I not already contributing? But with respect to the upcoming tests;
according to the definitions in various documents I don't qualify.
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Tue, Dec 8, 2015 at 3:00 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 12/07/2015 03:50 PM, Pierre Smits wrote:
> > The only thing I see at that url (https://vote-wip.apache.org/) is a big
> > fat logo, which is nice...
> >
> > But it doesn't enable me to do anything obvious. Maybe I am missing
> > something.
>
> This is a BTW: Does this mean you'll be interested in helping out with
> the upcoming tests? :)
>
> With regards,
> Daniel
>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/08/2015 04:54 PM, Sam Ruby wrote:
> [snip]
>
> P.S. There seems to be a disconnect between what Pierre and I are
> referring to as tests, and what you (Daniel) are referring to as
> tests. I would feel more comfortable if there were some automated
> unit tests.
>
Anyone can contribute to unit tests - the software to deploy and run
pysteve is freely available. I'm going to get started on some, but it is
quite a large task, as there are quite a lot of units inside the
libraries. This is one of the areas where more help would be especially
welcomed, both to speed up things, but also to show that we have some
sort of community around this that wants to help :)
With regards,
Daniel.
Re: Mock tests at some point?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Tue, Dec 8, 2015 at 9:45 AM, Daniel Gruno <hu...@apache.org> wrote:
> On 12/08/2015 03:00 PM, Daniel Gruno wrote:
>> On 12/07/2015 03:50 PM, Pierre Smits wrote:
>>> The only thing I see at that url (https://vote-wip.apache.org/) is a big
>>> fat logo, which is nice...
>>>
>>> But it doesn't enable me to do anything obvious. Maybe I am missing
>>> something.
>>
>> This is a BTW: Does this mean you'll be interested in helping out with
>> the upcoming tests? :)
>>
>> With regards,
>> Daniel
>
> Oh, also, there is a Dockerfile for building pySTeVe with docker now :)
Sweet!
Prior to looking at the Dockerfile, I was concerned that this would be
a Yak Shaving exercise. This makes me feel better.
> With regards,
> Daniel.
- Sam Ruby
P.S. There seems to be a disconnect between what Pierre and I are
referring to as tests, and what you (Daniel) are referring to as
tests. I would feel more comfortable if there were some automated
unit tests.
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/08/2015 03:00 PM, Daniel Gruno wrote:
> On 12/07/2015 03:50 PM, Pierre Smits wrote:
>> The only thing I see at that url (https://vote-wip.apache.org/) is a big
>> fat logo, which is nice...
>>
>> But it doesn't enable me to do anything obvious. Maybe I am missing
>> something.
>
> This is a BTW: Does this mean you'll be interested in helping out with
> the upcoming tests? :)
>
> With regards,
> Daniel
>
Oh, also, there is a Dockerfile for building pySTeVe with docker now :)
With regards,
Daniel.
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/07/2015 03:50 PM, Pierre Smits wrote:
> The only thing I see at that url (https://vote-wip.apache.org/) is a big
> fat logo, which is nice...
>
> But it doesn't enable me to do anything obvious. Maybe I am missing
> something.
This is a BTW: Does this mean you'll be interested in helping out with
the upcoming tests? :)
With regards,
Daniel
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
Hi Daniel,
Thanks!
I guess it'll happen when it will happen.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Mon, Dec 7, 2015 at 4:48 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 12/07/2015 03:50 PM, Pierre Smits wrote:
> > The only thing I see at that url (https://vote-wip.apache.org/) is a big
> > fat logo, which is nice...
> >
> > But it doesn't enable me to do anything obvious. Maybe I am missing
> > something.
> >
> It's working as intended :) The instructions on how to use pysteve are
> on the 'try it out' page, but I'll email with more details on the test
> we'll be doing when we get closer (and gather more folks to help out).
>
> Currently, the admin config wouldn't let you anywhere near the voting
> data anyway ;) That has to be set up appropriately when the time comes.
>
> With regards,
> Daniel.
>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/07/2015 03:50 PM, Pierre Smits wrote:
> The only thing I see at that url (https://vote-wip.apache.org/) is a big
> fat logo, which is nice...
>
> But it doesn't enable me to do anything obvious. Maybe I am missing
> something.
>
It's working as intended :) The instructions on how to use pysteve are
on the 'try it out' page, but I'll email with more details on the test
we'll be doing when we get closer (and gather more folks to help out).
Currently, the admin config wouldn't let you anywhere near the voting
data anyway ;) That has to be set up appropriately when the time comes.
With regards,
Daniel.
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
The only thing I see at that url (https://vote-wip.apache.org/) is a big
fat logo, which is nice...
But it doesn't enable me to do anything obvious. Maybe I am missing
something.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Mon, Dec 7, 2015 at 3:44 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 12/07/2015 03:43 PM, Pierre Smits wrote:
> > Is the product not being dockerized right now going to be a show stopper
> > for the testing you asked volunteers for earlier today? Do you want the
> > volunteers to wait for that?
>
> The Docker issue is a minor one, and certainly not one halting the test
> :) We have a VM at the ASF for this (vote-wip.apache.org), and the tests
> will be conducted there.
>
> With regards,
> Daniel.
>
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *OFBiz Extensions Marketplace*
> > http://oem.ofbizci.net/oci-2/
> >
> > On Mon, Dec 7, 2015 at 3:12 PM, Daniel Gruno <hu...@apache.org>
> wrote:
> >
> >> On 12/07/2015 03:09 PM, Sam Ruby wrote:
> >>> On Mon, Dec 7, 2015 at 7:24 AM, Daniel Gruno <hu...@apache.org>
> >> wrote:
> >> [snip]
> >>>>
> >>>> I for one will start looking for new people to help out with this, as
> I
> >>>> still think STeVe has a role to play, not just as an internal tool,
> but
> >>>> something that could be used elsewhere.
> >>>
> >>> When projects approach me looking to enter the incubator and build a
> >>> community, I stress the need for the project to have clear
> >>> instructions on how to download, build, and test their changes. I
> >>> asked earlier on this thread for this, and got basically a hand wave.
> >>>
> >>> If work starts on those aspects, I'll be a glad to increase my
> >>> participation and spread the word. This could be instructions for
> >>> setting up a Vagrant VM, or a Docker container, or running on your own
> >>> machine.
> >>
> >> I believe pysteve already has instructions for deploying it, on
> >> http://steve.apache.org/demo.html .
> >>
> >> As for docker, that could indeed be done (putting aside the fact that
> >> elasticsearch often doesn't work OOTB with docker). I'll look into
> >> dockerizing that today :)
> >>
> >> With regards,
> >> Daniel.
> >>
> >>>
> >>>> With regards,
> >>>> Daniel.
> >>>
> >>> - Sam Ruby
> >>
> >>
> >
>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/07/2015 03:43 PM, Pierre Smits wrote:
> Is the product not being dockerized right now going to be a show stopper
> for the testing you asked volunteers for earlier today? Do you want the
> volunteers to wait for that?
The Docker issue is a minor one, and certainly not one halting the test
:) We have a VM at the ASF for this (vote-wip.apache.org), and the tests
will be conducted there.
With regards,
Daniel.
>
> Best regards,
>
> Pierre Smits
>
> *OFBiz Extensions Marketplace*
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Dec 7, 2015 at 3:12 PM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 12/07/2015 03:09 PM, Sam Ruby wrote:
>>> On Mon, Dec 7, 2015 at 7:24 AM, Daniel Gruno <hu...@apache.org>
>> wrote:
>> [snip]
>>>>
>>>> I for one will start looking for new people to help out with this, as I
>>>> still think STeVe has a role to play, not just as an internal tool, but
>>>> something that could be used elsewhere.
>>>
>>> When projects approach me looking to enter the incubator and build a
>>> community, I stress the need for the project to have clear
>>> instructions on how to download, build, and test their changes. I
>>> asked earlier on this thread for this, and got basically a hand wave.
>>>
>>> If work starts on those aspects, I'll be a glad to increase my
>>> participation and spread the word. This could be instructions for
>>> setting up a Vagrant VM, or a Docker container, or running on your own
>>> machine.
>>
>> I believe pysteve already has instructions for deploying it, on
>> http://steve.apache.org/demo.html .
>>
>> As for docker, that could indeed be done (putting aside the fact that
>> elasticsearch often doesn't work OOTB with docker). I'll look into
>> dockerizing that today :)
>>
>> With regards,
>> Daniel.
>>
>>>
>>>> With regards,
>>>> Daniel.
>>>
>>> - Sam Ruby
>>
>>
>
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
Is the product not being dockerized right now going to be a show stopper
for the testing you asked volunteers for earlier today? Do you want the
volunteers to wait for that?
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Mon, Dec 7, 2015 at 3:12 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 12/07/2015 03:09 PM, Sam Ruby wrote:
> > On Mon, Dec 7, 2015 at 7:24 AM, Daniel Gruno <hu...@apache.org>
> wrote:
> [snip]
> >>
> >> I for one will start looking for new people to help out with this, as I
> >> still think STeVe has a role to play, not just as an internal tool, but
> >> something that could be used elsewhere.
> >
> > When projects approach me looking to enter the incubator and build a
> > community, I stress the need for the project to have clear
> > instructions on how to download, build, and test their changes. I
> > asked earlier on this thread for this, and got basically a hand wave.
> >
> > If work starts on those aspects, I'll be a glad to increase my
> > participation and spread the word. This could be instructions for
> > setting up a Vagrant VM, or a Docker container, or running on your own
> > machine.
>
> I believe pysteve already has instructions for deploying it, on
> http://steve.apache.org/demo.html .
>
> As for docker, that could indeed be done (putting aside the fact that
> elasticsearch often doesn't work OOTB with docker). I'll look into
> dockerizing that today :)
>
> With regards,
> Daniel.
>
> >
> >> With regards,
> >> Daniel.
> >
> > - Sam Ruby
>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/07/2015 03:09 PM, Sam Ruby wrote:
> On Mon, Dec 7, 2015 at 7:24 AM, Daniel Gruno <hu...@apache.org> wrote:
[snip]
>>
>> I for one will start looking for new people to help out with this, as I
>> still think STeVe has a role to play, not just as an internal tool, but
>> something that could be used elsewhere.
>
> When projects approach me looking to enter the incubator and build a
> community, I stress the need for the project to have clear
> instructions on how to download, build, and test their changes. I
> asked earlier on this thread for this, and got basically a hand wave.
>
> If work starts on those aspects, I'll be a glad to increase my
> participation and spread the word. This could be instructions for
> setting up a Vagrant VM, or a Docker container, or running on your own
> machine.
I believe pysteve already has instructions for deploying it, on
http://steve.apache.org/demo.html .
As for docker, that could indeed be done (putting aside the fact that
elasticsearch often doesn't work OOTB with docker). I'll look into
dockerizing that today :)
With regards,
Daniel.
>
>> With regards,
>> Daniel.
>
> - Sam Ruby
Re: Mock tests at some point?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Dec 7, 2015 at 7:24 AM, Daniel Gruno <hu...@apache.org> wrote:
> On 11/17/2015 12:06 AM, Sean Kelly wrote:
>> The total of two---count 'em, 2---threads on the user@steve.apache.org
>> mailing list since December 2014 might be an indication of a lack of
>> outside interest.
>
> Well that veered off topic fast :)
>
> two threads on user@ is probably because we have _no release_ to offer
> to people. There is one active developer and perhaps 3-4 active
> contributors, and yes, that's an issue. We need to test what we have and
> consider releasing at some point, even if it's just pySTeVe we release.
> But that requires people that are interested in testing and releasing.
>
> I don't see how combining STeVe and Whimsy would solve much - if
> anything, it would simply create two diaspora-projects within a TLP.
>
> Before we start considering drastic measures like combining TLPs or
> moving to the attic, I would strongly urge the committers and PMC
> members to at least try to help out with promoting STeVe and getting
> some new blood to the project. If that fails completely, then fine - but
> by golly, we should at least TRY.
>
> I for one will start looking for new people to help out with this, as I
> still think STeVe has a role to play, not just as an internal tool, but
> something that could be used elsewhere.
When projects approach me looking to enter the incubator and build a
community, I stress the need for the project to have clear
instructions on how to download, build, and test their changes. I
asked earlier on this thread for this, and got basically a hand wave.
If work starts on those aspects, I'll be a glad to increase my
participation and spread the word. This could be instructions for
setting up a Vagrant VM, or a Docker container, or running on your own
machine.
> With regards,
> Daniel.
- Sam Ruby
>> --k
>>> Jim Jagielski <ma...@jaguNET.com>
>>> 2015-November-16 at 3:33 PM
>>> 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.
>>>
>>>
>>>
>>> Sam Ruby <ma...@intertwingly.net>
>>> 2015-November-16 at 3:18 PM
>>> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org>
>>>>> 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<hu...@apache.org> 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<hu...@apache.org>
>>>>>>>> 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
>>>>>>>
>>> Jim Jagielski <ma...@jaguNET.com>
>>> 2015-November-16 at 3:12 PM
>>> I wonder if it's time to move STeVe to be under Whimsy...
>>> Or is the goal still to have STeVe be generic enough for
>>> other external users?
>>>
>>>
>>> Daniel Gruno <ma...@apache.org>
>>> 2015-November-12 at 9:25 AM
>>> To wit, the admin interface on vote-wip is found at:
>>> https://vote-wip.apache.org/admin/
>>>
>>> With regards,
>>> Daniel.
>>>
>>> Daniel Gruno <ma...@apache.org>
>>> 2015-November-12 at 9:22 AM
>>> On 11/12/2015 04:12 PM, Sam Ruby wrote:
>>>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org>
>>>> 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<hu...@apache.org> 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
>>>>
>>>
>>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 12/07/2015 02:03 PM, Pierre Smits wrote:
> Up to yesterday I made 89 contributions to this project. But to no avail
> regarding being noticed/recognized. This must be a 'very special project'.
I can only speak for myself, of course, but your contributions have been
noted.
With regards,
Daniel.
>
> You won't get more people on board when at organisational level it is only
> intended for the incrowd. See at
> https://projects.apache.org/committee.html?steve, with only the very
> privileged people in the PMC (of which 5 hae even more specific
> roles/functions at board and exec level).
>
> It just doesn't come across as 'open' with the contributors of the other
> kind.
>
> But maybe it is supposed that way.
>
> Best regards,
>
> Pierre Smits
>
> *OFBiz Extensions Marketplace*
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Dec 7, 2015 at 1:24 PM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 11/17/2015 12:06 AM, Sean Kelly wrote:
>>> The total of two---count 'em, 2---threads on the user@steve.apache.org
>>> mailing list since December 2014 might be an indication of a lack of
>>> outside interest.
>>
>> Well that veered off topic fast :)
>>
>> two threads on user@ is probably because we have _no release_ to offer
>> to people. There is one active developer and perhaps 3-4 active
>> contributors, and yes, that's an issue. We need to test what we have and
>> consider releasing at some point, even if it's just pySTeVe we release.
>> But that requires people that are interested in testing and releasing.
>>
>> I don't see how combining STeVe and Whimsy would solve much - if
>> anything, it would simply create two diaspora-projects within a TLP.
>>
>> Before we start considering drastic measures like combining TLPs or
>> moving to the attic, I would strongly urge the committers and PMC
>> members to at least try to help out with promoting STeVe and getting
>> some new blood to the project. If that fails completely, then fine - but
>> by golly, we should at least TRY.
>>
>> I for one will start looking for new people to help out with this, as I
>> still think STeVe has a role to play, not just as an internal tool, but
>> something that could be used elsewhere.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> --k
>>>> Jim Jagielski <ma...@jaguNET.com>
>>>> 2015-November-16 at 3:33 PM
>>>> 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.
>>>>
>>>>
>>>>
>>>> Sam Ruby <ma...@intertwingly.net>
>>>> 2015-November-16 at 3:18 PM
>>>> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org>
>>>>>> 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<hu...@apache.org> 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<hu...@apache.org>
>>>>>>>>> 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
>>>>>>>>
>>>> Jim Jagielski <ma...@jaguNET.com>
>>>> 2015-November-16 at 3:12 PM
>>>> I wonder if it's time to move STeVe to be under Whimsy...
>>>> Or is the goal still to have STeVe be generic enough for
>>>> other external users?
>>>>
>>>>
>>>> Daniel Gruno <ma...@apache.org>
>>>> 2015-November-12 at 9:25 AM
>>>> To wit, the admin interface on vote-wip is found at:
>>>> https://vote-wip.apache.org/admin/
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> Daniel Gruno <ma...@apache.org>
>>>> 2015-November-12 at 9:22 AM
>>>> On 11/12/2015 04:12 PM, Sam Ruby wrote:
>>>>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org>
>>>>> 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<hu...@apache.org> 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
>>>>>
>>>>
>>>
>>
>>
>
Re: Mock tests at some point?
Posted by Pierre Smits <pi...@gmail.com>.
Up to yesterday I made 89 contributions to this project. But to no avail
regarding being noticed/recognized. This must be a 'very special project'.
You won't get more people on board when at organisational level it is only
intended for the incrowd. See at
https://projects.apache.org/committee.html?steve, with only the very
privileged people in the PMC (of which 5 hae even more specific
roles/functions at board and exec level).
It just doesn't come across as 'open' with the contributors of the other
kind.
But maybe it is supposed that way.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Mon, Dec 7, 2015 at 1:24 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 11/17/2015 12:06 AM, Sean Kelly wrote:
> > The total of two---count 'em, 2---threads on the user@steve.apache.org
> > mailing list since December 2014 might be an indication of a lack of
> > outside interest.
>
> Well that veered off topic fast :)
>
> two threads on user@ is probably because we have _no release_ to offer
> to people. There is one active developer and perhaps 3-4 active
> contributors, and yes, that's an issue. We need to test what we have and
> consider releasing at some point, even if it's just pySTeVe we release.
> But that requires people that are interested in testing and releasing.
>
> I don't see how combining STeVe and Whimsy would solve much - if
> anything, it would simply create two diaspora-projects within a TLP.
>
> Before we start considering drastic measures like combining TLPs or
> moving to the attic, I would strongly urge the committers and PMC
> members to at least try to help out with promoting STeVe and getting
> some new blood to the project. If that fails completely, then fine - but
> by golly, we should at least TRY.
>
> I for one will start looking for new people to help out with this, as I
> still think STeVe has a role to play, not just as an internal tool, but
> something that could be used elsewhere.
>
> With regards,
> Daniel.
>
> >
> > --k
> >> Jim Jagielski <ma...@jaguNET.com>
> >> 2015-November-16 at 3:33 PM
> >> 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.
> >>
> >>
> >>
> >> Sam Ruby <ma...@intertwingly.net>
> >> 2015-November-16 at 3:18 PM
> >> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org>
> >>>> 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<hu...@apache.org> 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<hu...@apache.org>
> >>>>>>> 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
> >>>>>>
> >> Jim Jagielski <ma...@jaguNET.com>
> >> 2015-November-16 at 3:12 PM
> >> I wonder if it's time to move STeVe to be under Whimsy...
> >> Or is the goal still to have STeVe be generic enough for
> >> other external users?
> >>
> >>
> >> Daniel Gruno <ma...@apache.org>
> >> 2015-November-12 at 9:25 AM
> >> To wit, the admin interface on vote-wip is found at:
> >> https://vote-wip.apache.org/admin/
> >>
> >> With regards,
> >> Daniel.
> >>
> >> Daniel Gruno <ma...@apache.org>
> >> 2015-November-12 at 9:22 AM
> >> On 11/12/2015 04:12 PM, Sam Ruby wrote:
> >>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org>
> >>> 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<hu...@apache.org> 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
> >>>
> >>
> >
>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 11/17/2015 12:06 AM, Sean Kelly wrote:
> The total of two---count 'em, 2---threads on the user@steve.apache.org
> mailing list since December 2014 might be an indication of a lack of
> outside interest.
Well that veered off topic fast :)
two threads on user@ is probably because we have _no release_ to offer
to people. There is one active developer and perhaps 3-4 active
contributors, and yes, that's an issue. We need to test what we have and
consider releasing at some point, even if it's just pySTeVe we release.
But that requires people that are interested in testing and releasing.
I don't see how combining STeVe and Whimsy would solve much - if
anything, it would simply create two diaspora-projects within a TLP.
Before we start considering drastic measures like combining TLPs or
moving to the attic, I would strongly urge the committers and PMC
members to at least try to help out with promoting STeVe and getting
some new blood to the project. If that fails completely, then fine - but
by golly, we should at least TRY.
I for one will start looking for new people to help out with this, as I
still think STeVe has a role to play, not just as an internal tool, but
something that could be used elsewhere.
With regards,
Daniel.
>
> --k
>> Jim Jagielski <ma...@jaguNET.com>
>> 2015-November-16 at 3:33 PM
>> 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.
>>
>>
>>
>> Sam Ruby <ma...@intertwingly.net>
>> 2015-November-16 at 3:18 PM
>> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org>
>>>> 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<hu...@apache.org> 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<hu...@apache.org>
>>>>>>> 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
>>>>>>
>> Jim Jagielski <ma...@jaguNET.com>
>> 2015-November-16 at 3:12 PM
>> I wonder if it's time to move STeVe to be under Whimsy...
>> Or is the goal still to have STeVe be generic enough for
>> other external users?
>>
>>
>> Daniel Gruno <ma...@apache.org>
>> 2015-November-12 at 9:25 AM
>> To wit, the admin interface on vote-wip is found at:
>> https://vote-wip.apache.org/admin/
>>
>> With regards,
>> Daniel.
>>
>> Daniel Gruno <ma...@apache.org>
>> 2015-November-12 at 9:22 AM
>> On 11/12/2015 04:12 PM, Sam Ruby wrote:
>>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org>
>>> 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<hu...@apache.org> 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
>>>
>>
>
Re: Mock tests at some point?
Posted by Sean Kelly <ke...@apache.org>.
The total of two---count 'em, 2---threads on the user@steve.apache.org
mailing list since December 2014 might be an indication of a lack of
outside interest.
--k
> Jim Jagielski <ma...@jaguNET.com>
> 2015-November-16 at 3:33 PM
> 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.
>
>
>
> Sam Ruby <ma...@intertwingly.net>
> 2015-November-16 at 3:18 PM
> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski<ji...@jagunet.com> 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<hu...@apache.org> 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<hu...@apache.org> 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<hu...@apache.org> 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
>>>>>
> Jim Jagielski <ma...@jaguNET.com>
> 2015-November-16 at 3:12 PM
> I wonder if it's time to move STeVe to be under Whimsy...
> Or is the goal still to have STeVe be generic enough for
> other external users?
>
>
> Daniel Gruno <ma...@apache.org>
> 2015-November-12 at 9:25 AM
> To wit, the admin interface on vote-wip is found at:
> https://vote-wip.apache.org/admin/
>
> With regards,
> Daniel.
>
> Daniel Gruno <ma...@apache.org>
> 2015-November-12 at 9:22 AM
> On 11/12/2015 04:12 PM, Sam Ruby wrote:
>> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno<hu...@apache.org> 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<hu...@apache.org> 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
>>
>
Re: Mock tests at some point?
Posted by Jim Jagielski <ji...@jaguNET.com>.
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 <ru...@intertwingly.net> wrote:
>
> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski <ji...@jagunet.com> 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 <hu...@apache.org> 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 <hu...@apache.org> 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 <hu...@apache.org> 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
>>>>>
>>>>
>>>
>>
Re: Mock tests at some point?
Posted by Jim Jagielski <ji...@jaguNET.com>.
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 <ru...@intertwingly.net> wrote:
>
> On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski <ji...@jagunet.com> 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 <hu...@apache.org> 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 <hu...@apache.org> 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 <hu...@apache.org> 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
>>>>>
>>>>
>>>
>>
Re: Mock tests at some point?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Nov 16, 2015 at 4:12 PM, Jim Jagielski <ji...@jagunet.com> 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 <hu...@apache.org> 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 <hu...@apache.org> 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 <hu...@apache.org> 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
>>>>
>>>
>>
>
Re: Mock tests at some point?
Posted by Jim Jagielski <ji...@jaguNET.com>.
I wonder if it's time to move STeVe to be under Whimsy...
Or is the goal still to have STeVe be generic enough for
other external users?
> On Nov 12, 2015, at 10:25 AM, Daniel Gruno <hu...@apache.org> 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 <hu...@apache.org> 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 <hu...@apache.org> 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
>>>
>>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
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 <hu...@apache.org> 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 <hu...@apache.org> 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
>>
>
Re: Mock tests at some point?
Posted by Daniel Gruno <hu...@apache.org>.
On 11/12/2015 04:12 PM, Sam Ruby wrote:
> On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno <hu...@apache.org> 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 <hu...@apache.org> 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
>
Re: Mock tests at some point?
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno <hu...@apache.org> 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 <hu...@apache.org> 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?
- Sam Ruby