[Discuss] Apache Steve
Background: over a period of time, the ASF has developed a number of tools that help with voting processes. These are used to vote in new boards and members. From time to time, they have also been used by various PMCs. These tools are currently located in a foundation private location: https://svn.apache.org/repos/private/foundation/voter We've received (and/or planted :-)) outside interest in these tools, and as such thought about how to make a release of these tools for outside consumption. The votes cast to date are private, but the tools used to process these votes need not be. Much of the initial code was written by Roy Fielding, and I can verify that we have an ICLA on file for him. Jim expressed an interest in chairing, and I can vouch that he gets the Apache Way :-). Greg Stein wrote/ported stv_tool.py (after which this proposal is named), and knows how to make an ASF release. I can go on, but a number of things are clear: the code is in active use, this code is already in ASF repositories and has been for some time, everybody who has contributed to date has an ICLA on file, and everybody who has contributed to date qualifies to be a Mentor for this effort. This so far has lead us to the conclusion that there really isn't any incubating that needs to be done. I'd like to open the topic up for discussion. To kick things off, I'd copy the draft ASF Board resolution into the incubator wiki, but apparently SamRuby is not in the ContributorsGroup. If somebody could rectify that and/or copy the resolution into the wiki, I would appreciate that. There's not much to see there, it simply is a routine resolution, full of words like WHEREAS, THEREFORE, and RESOLVED. https://svn.apache.org/repos/private/foundation/board/apache-steve.txt - Sam Ruby P.S. I apologize for publishing private links to a public list, but the clear intent here is to open everything up. We just need to figure out the best way to get from where we are to where we want to be. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Steve
Hi, On Sat, Jun 30, 2012 at 12:03 PM, Sam Ruby ru...@intertwingly.net wrote: This so far has lead us to the conclusion that there really isn't any incubating that needs to be done. I'd like to open the topic up for discussion. Here's what I wrote about this on board@: There's plenty of precedent of existing TLPs spawning off subprojects without having them first go through the Incubator, and I don't see why stuff from infra would need to be treated differently. However, there's also precedent of TLPs bringing subprojects to the Incubator to grow the community and to evaluate when critical mass for a TLP has been reached. I'd say it's up to infra and the people who're already working on the STV tools to decide which path to follow. The Incubator would of course be happy to help (in the ways it can), but I see no hard reason why the Incubator would absolutely need be involved if a good enough community already exists for a TLP. To kick things off, I'd copy the draft ASF Board resolution into the incubator wiki, but apparently SamRuby is not in the ContributorsGroup. Fixed. If somebody could rectify that and/or copy the resolution into the wiki, I would appreciate that. There's not much to see there, it simply is a routine resolution, full of words like WHEREAS, THEREFORE, and RESOLVED. https://svn.apache.org/repos/private/foundation/board/apache-steve.txt Not sure if it needs to be on the wiki, so for now I'm just including a copy of the proposed resolution below: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to voting systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Steve Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Steve Project be and hereby is responsible for the creation and maintenance of software related to voting systems; and be it further RESOLVED, that the office of Vice President, Apache Steve be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Steve Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Steve Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Steve Project: * Jim Jagielski j...@apache.org * Chris A. Mattmann mattm...@apache.org * Sam Ruby ru...@apache.org * Greg Stein gst...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be appointed to the office of Vice President, Apache Steve, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Steve Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Steve Project. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board will be proposing a new TLP
Le 6/30/12 2:23 PM, Jim Jagielski a écrit : Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... Sure we should go through incubation, to make sure the peeps being STV code *knows* about the Apache Way... Or is this simple non-sense ? My +1 to the TLP without going through incubation... -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board will be proposing a new TLP
On Sat, Jun 30, 2012 at 3:53 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Le 6/30/12 2:23 PM, Jim Jagielski a écrit : Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... Sure we should go through incubation, to make sure the peeps being STV code *knows* about the Apache Way... Or is this simple non-sense ? No I don't think this is non-sense. However note that as Jim pointed out, the difference here, that would favor the direct TLP route, is the fact that everyone working on the voting tool are already Apache Committers and Members. Conceivably they already know the Apache Way. Then again a quick incubation process might help get an extra sanity check from the Incubator. Your point makes sense considering outside participants to build a larger community around the tool. Incubation might be a good environment for a mass influx of new to Apache, interested parties to participate. But it does not sound like they're going to be directly involved, knocking on our doors immediately. Also there's no IP to vet. I presume this is more a matter of making the software an official Apache Product with PMC endorsed releases that other organizations like OpenStack can use immediately. +1 Setup TLP without incubation, yet I can understand arguments for a quick incubation. -- Best Regards, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board will be proposing a new TLP
+1 straight to TLP -- dims On Jun 30, 2012, at 7:23 AM, Jim Jagielski j...@jagunet.com wrote: For those not following board@, the board is proposing the creation of a new TLP (tentatively called Apache Steve) which will serve as the project behind our STV and voting tools. The impetus behind this was when I suggested to the OpenStack people to use STV for their voting system, which kind of re-kicked the idea in my head that our voting tools were too good to not provide as releasable code to the world at large. Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... The board would like to recommend to the Incubator that the board simply proceed with the creation of this project at the next board meeting. Thx. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board will be proposing a new TLP
+1 on the proposal itself and how it will go directly through the board I also agree /w what has been said and replied to by both Emmanuel Alex On Jun 30, 2012 3:32 PM, Alex Karasulu akaras...@apache.org wrote: On Sat, Jun 30, 2012 at 3:53 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Le 6/30/12 2:23 PM, Jim Jagielski a écrit : Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... Sure we should go through incubation, to make sure the peeps being STV code *knows* about the Apache Way... Or is this simple non-sense ? No I don't think this is non-sense. However note that as Jim pointed out, the difference here, that would favor the direct TLP route, is the fact that everyone working on the voting tool are already Apache Committers and Members. Conceivably they already know the Apache Way. Then again a quick incubation process might help get an extra sanity check from the Incubator. Your point makes sense considering outside participants to build a larger community around the tool. Incubation might be a good environment for a mass influx of new to Apache, interested parties to participate. But it does not sound like they're going to be directly involved, knocking on our doors immediately. Also there's no IP to vet. I presume this is more a matter of making the software an official Apache Product with PMC endorsed releases that other organizations like OpenStack can use immediately. +1 Setup TLP without incubation, yet I can understand arguments for a quick incubation. -- Best Regards, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Steve
Looks good to me +1 :) On Jun 30, 2012 12:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Sat, Jun 30, 2012 at 12:03 PM, Sam Ruby ru...@intertwingly.net wrote: This so far has lead us to the conclusion that there really isn't any incubating that needs to be done. I'd like to open the topic up for discussion. Here's what I wrote about this on board@: There's plenty of precedent of existing TLPs spawning off subprojects without having them first go through the Incubator, and I don't see why stuff from infra would need to be treated differently. However, there's also precedent of TLPs bringing subprojects to the Incubator to grow the community and to evaluate when critical mass for a TLP has been reached. I'd say it's up to infra and the people who're already working on the STV tools to decide which path to follow. The Incubator would of course be happy to help (in the ways it can), but I see no hard reason why the Incubator would absolutely need be involved if a good enough community already exists for a TLP. To kick things off, I'd copy the draft ASF Board resolution into the incubator wiki, but apparently SamRuby is not in the ContributorsGroup. Fixed. If somebody could rectify that and/or copy the resolution into the wiki, I would appreciate that. There's not much to see there, it simply is a routine resolution, full of words like WHEREAS, THEREFORE, and RESOLVED. https://svn.apache.org/repos/private/foundation/board/apache-steve.txt Not sure if it needs to be on the wiki, so for now I'm just including a copy of the proposed resolution below: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to voting systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Steve Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Steve Project be and hereby is responsible for the creation and maintenance of software related to voting systems; and be it further RESOLVED, that the office of Vice President, Apache Steve be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Steve Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Steve Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Steve Project: * Jim Jagielski j...@apache.org * Chris A. Mattmann mattm...@apache.org * Sam Ruby ru...@apache.org * Greg Stein gst...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be appointed to the office of Vice President, Apache Steve, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Steve Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Steve Project. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board will be proposing a new TLP
On Sat, Jun 30, 2012 at 5:23 AM, Jim Jagielski j...@jagunet.com wrote: For those not following board@, the board is proposing the creation of a new TLP (tentatively called Apache Steve) which will serve as the project behind our STV and voting tools. +1 to proceed directly to steve.apache.org. Incubation is only one possible approach among many to fostering a healthy project which is likely to succeed as a TLP. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Board will be proposing a new TLP
+1 for straight to TLP given the individuals and code provenance. -Original Message- From: Jim Jagielski [mailto:j...@jagunet.com] Sent: Saturday, June 30, 2012 8:24 AM To: general@incubator.apache.org Subject: Board will be proposing a new TLP For those not following board@, the board is proposing the creation of a new TLP (tentatively called Apache Steve) which will serve as the project behind our STV and voting tools. The impetus behind this was when I suggested to the OpenStack people to use STV for their voting system, which kind of re-kicked the idea in my head that our voting tools were too good to not provide as releasable code to the world at large. Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... The board would like to recommend to the Incubator that the board simply proceed with the creation of this project at the next board meeting. Thx. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
