This was extracted (@ 2017-09-20 19:10) from a list of minutes
which have been approved by the Board. Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.

## Description:
- Apache STeVe is Apache's Python based voting system that the Foundation uses
to handle things like voting in our new Board of Directors.
## Issues:
- There are no issues that require board attention.
## Activity:
- No noticeable activity in the past quarter, as expected by the fact that the
project mostly revolves around the annual meeting.
- Several apache communities have been using STeVe in the past quarter
to conduct official votes on issues, though not much feedback has
made it back to the STeVe community.
## Health report:
- The automated score of -2 somewhat accurately reflects the project. While
we do have PMC oversight, there has been no considerable efforts
to further develop the system. We may have to start discussing
how to better reach out to new developers/contributors and get
folks interested in working on STeVe.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Sun Apr 19 2015
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- No releases have been made as of yet.
## Mailing list activity:
- No real changes to the list activities and around 10 emails
sent to the various lists over the past quarter.
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months

## Description:
- Apache STeVe is Apache's Python based voting system that the
Foundation uses to handle things like voting in our new Board of
Directors.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- No real activity to speak of. The project appears to be in
maintenance mode mostly.
## Health report:
- Low activity. After the annual members meeting, a few additional
tickets were created, but we have yet to see new contributors step
forward. There are still sufficient PMC members for oversight. I'll
kick off a discussion in the project about our next steps. There have
been inquiries about the use of STeVe in other organisations.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- No public releases yet, though trunk is being used at the ASF.
## Mailing list activity:
- Hardly any mail...
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months

## Description:
Apache STeVe is Apache's Python based voting system that the
Foundation uses to handle things like voting in our new Board of
Directors.
## Issues:
There are no issues requiring board attention yet.
## Activity:
No activity in this period, which was anticipated (STeVe is a project
that generally only has activity around March, April, May)
## Health report:
Two additional people have chosen to resign from STeVe, leaving the
PMC at 5 members currently. This is not a great situation to be in,
and we will be pushing for some more contributors once we get closer
to the annual members meeting. There are still >3 active PMC members
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
- Sean Kelly chose to resign from the PMC on November 1st, 2016.
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- No official releases yet, although the codebase is considered stable.
We might consider pushing a release soon (TBD).
## Mailing list activity:
- Pretty low activity, expected to go up in the coming months as we get
closer to the annual meeting.
- dev@steve.apache.org: no email sent
- issues@steve.apache.org: no email sent
- user@steve.apache.org:
- 13 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)

## Description:
- Apache STeVe is Apache's Python based voting system that the
Foundation uses to handle things like voting in our new Board of
Directors.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- No activity of note this period, which is to be expected.
STeVe is generally only active around the annual meeting.
We expect acvitity to pick up again around February/March.
## Health report:
- As STeVe is a "seasonal project", it is expected that activity is
nonexistent in this reporting period.
- Greg Stein has chosen to leave the STeVe PMC. We thank Greg for his
work - I'd personally like to thank him for his many code reviews
over the years.
- Still have 3+ PMC members that are alive and well, though we could
consider appointing more PMC members at this point.
## PMC changes:
- Currently 6 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
- Greg Stein left the PMC on October 5th 2016.
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- No official releases yet, though the software is being used in
production.

## Description:
Apache STeVe is Apache's Python based voting system that the Foundation
uses to handle things like voting in our new Board of Directors.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
STeVe is currently in a sort of hiatus. We have >= 3 PMC members awake,
but development has been stalled due to lack of spare cycles to devote
on the project. As we get closer to next ASF Members Meeting, we expect
development to pick up the pace again. If not, we'll be sure to notify
the board, but we are not expecting this to become a problem. We are
not aware of any outstanding vulnerabilities or anything critical in
the software.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- No releases yet.
## Mailing list activity:
Mailing list activity seems tied to the members meeting, going
up when we get close to a new meeting, and then dying out afterwards.

## Description:
Apache STeVe is Apache's Python based voting system that the Foundation uses
to handle things like voting in our new Board of Directors.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Test elections were held in preparation for the annual ASF Members Meeting.
Feedback from these tests (including some UI and form data parsing bugs)
were incorporated into the STeVe software.
- The Annual ASF Members Meeting was held and used STeVe as the voting
platform. On the whole, things went very smooth, with only very few nits.
Issues such as screen reader friendliness has been taken into consideration
for future development.
- Several issues were raised about some design decisions in STeVe, and while
not serious or bad (merely opinions on how it should operate), we do need to
discuss these characteristics and see if we can provide either a changed
backend design or alternately optional features for STeVe.
## Health report:
- STeVe is healthy in the sense that we have >= 3 PMC members active at all
times. We have also seen an uptick in both tickets being filed as well as
people volunteering to help out with further development of STeVe. It is my
sincere hope that these volunteers will stick with us and won't be drive-by
patch submitters.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
- Chris Mattman has chosen to resign from the STeVe PMC.
We thank Chris for his contributions and would of course welcome him back,
should he wish to rejoin.
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
## Releases:
- While no releases have been made yet, STeVe has been used for
several elections. We are hoping to get a release out once the
dust from the last members meeting settles and the kinks have
been ironed out.
## Mailing list activity:
Activity has been relatively low. There was an uptick in mails to the issues@
list due to JIRA tickets being created as a result of users' experience with
the ASF members meeting. User@ has seen virtually no activity, but that is to
be expected when we don't have an official release yet.
- dev@steve.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 19 emails sent to list (47 in previous quarter)
- issues@steve.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 34 emails sent to list (14 in previous quarter)
- user@steve.apache.org:
- 13 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (1 in previous quarter)
## JIRA activity:
JIRA has seen an uptick in issues after the ASF members meeting.
This is generally a very good sign that people are getting involved.
- 14 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months

## Description:
Apache STeVe is Apache's Python based voting system that the Foundation uses
to handle things like voting in our new Board of Directors.
## Issues:
- There are no issues requiring much board attention at this time. As stated
below, we are in a state of trying to find our footing, but at present,
it is not something that the board need to concern themselves with,
unless they wish to help out in a personal capacity.
## Activity:
This quarter has been one of some soul searching within the PMC, kicked off by
a thread by the former VP asking whether it would make sense to disband the
PMC and merge the project with the Whimsy PMC. While this did not gain enough
traction to make it to any formal vote or the likes, it did shine some light
on the difficulties of 'seasonal projects' like STeVe, where the community can
seem quite dead for large periods of time. There were some follow-ups asking
for more participation, and we did manage to vote in a new committer to help
with the project.
## Health report:
While the project can be considered as being in hiatus between annual member
meetings, the above mentioned call for a new committer did manage to garner
votes from 5 PMC members, proving that we still have the 3x+1 needed to have
an active PMC. We continue to monitor the state of the community as we
approach the usual busy period around March/April.
On a more personal note, I will likely be reaching out to the ASF membership
and seek people to help us test and improve the pySTeVe branch of our project.
It is my belief that getting a release out at some point will help our
visibility and grow our community, but we are in need of people to test and
report back with their findings.
Compared to previous quarter, the email flow picked up relatively well, albeit
still not much.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
## Committer base changes:
- Currently 9 committers.
- Pierre Smits was added as a committer on Tue Dec 15 2015
## Releases:
- No releases yet.
## Mailing list activity:
- dev@steve.apache.org:
- 20 subscribers (up 2 in the last 3 months):
- 47 emails sent to list (4 in previous quarter)
- user@steve.apache.org:
- 13 subscribers (up 3 in the last 3 months):
- 1 emails sent to list (0 in previous quarter)
- issues@steve.apache.org:
- 12 subscribers (up 1 in the last 3 months):
- 14 emails sent to list (0 in previous quarter)
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months

Change the Apache STeVe Project Chair

WHEREAS, the Board of Directors heretofore appointed Jim Jagielski
to the office of Vice President, Apache STeVe, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Jim Jagielski from the office of Vice President, Apache STeVe, and
WHEREAS, the Project Management Committee of the Apache STeVe project
has chosen to recommend Daniel Gruno as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Jim Jagielski is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache STeVe, and
BE IT FURTHER RESOLVED, that Daniel Gruno be and hereby is
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.
Special Order 7B, Change the Apache STeVe Project Chair, was
approved by Unanimous Vote of the directors present.

## Description:
STeVe is a system for managing a plethora of vote mechanisms, most notably
the STV (Single Transferable Vote) method used in the ASF board elections.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Minor work on pySTeVe has been done, but the bulk of the program is, for the
time being, considered stable, and so development has slowed down.
- Suggestions to run some mock elections with ASF committers trying out the new
system has been proposed, but not yet carried out.
- We are discussing when/if/how to release the pySTeVe component.
- Jim Jagielski has decided to step down as VP, and proposed Daniel Gruno to
replace him in this role (see special order 7B). The PMC extends its thanks
to Jim for the work he's done as VP.
## Health report:
- The community remains healthy, albeit in a sort of hiatus state. This is
likely due to ASF elections being about half a year away.
- PMC remains alive and responsive when needed.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen at Mon Apr 20 2015
## LDAP changes:
- Currently 8 committers and 8 committee group members.
- No new committee group members added in the last 3 months
- Last committee group addition was Richard Bowen at Mon Apr 20 2015
- No new committers added in the last 3 months
- Last committer addition was Richard Bowen at Mon Apr 20 2015
## Releases:
- No official releases have been made yet, but we are discussing releasing the
pySTeVe component sometime soon.
## Mailing list activity:
- dev@steve.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (1 in previous quarter)
- user@steve.apache.org:
- 10 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@steve.apache.org:
- 11 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)

Note:
This month's report was drafted by Daniel Gruno and approved by
Jim Jagielski.
Description:
STeVe is a system for managing a plethora of vote mechanisms, most notably
the STV (Single Transferable Vote) method used in the ASF board elections.
Activity:
After a successful annual members meeting, many new ideas came up and were
discussed in the project. A new branch, called pySTeVe, was created with the
purpose of providing a unified web UI for setting up, voting and tallying
votes/issues with a modular architecture that allows numerous new ways of
voting. Of particular note is that pySTeVe is Python based, rather than
Perl. No official release has been made yet, but we are confident that
this will happen before the next annual meeting.
An online demo VM has been set up at https://vote-wip.apache.org/, which can
be used by Apache projects to both test pySTeVe and hold online votes on
issues. With infra's support, this VM is scheduled to host the next annual
members votes as well.
Health report:
The project is currently in a summer holiday hiatus, but has seen a great
influx in code, committers and discussion since the annual meeting. We are
confident that there is sufficient oversight in the PMC.
Issues:
There are no issues requiring board attention at this time
LDAP committee group/Committership changes:
- Currently 8 committers and 8 LDAP committee group members.
- No new LDAP committee group members added in the last 3 months
- Last LDAP committee group addition was Richard Bowen at Mon Apr 20 2015
- No new committers added in the last 3 months
- Last committer addition was Richard Bowen at Mon Apr 20 2015
Releases:
- No releases made yet.
Mailing list activity:
- dev@steve.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (218 in previous quarter)
- user@steve.apache.org:
- 10 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (1 in previous quarter)
- issues@steve.apache.org:
- 11 subscribers (down -1 in the last 3 months):
- 0 emails sent to list (39 in previous quarter)

Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* As expected, the annual ASF Members Meeting and elections have resulted
in a *huge* flurry of activity, especially from one of our new PMC
members: Daniel Gruno. Work on a Python version of STeVe, codenamed
pysteve, is ongoing, with some detailed implementation designs being
discussed.
COMMUNITY
* The previous 2 new committers were added in July 2013; since then we
have 4 new committers and PMC members:
o Alan Cabrera (03/2015)
o Sean Kelly (03/2015)
o Daniel Gruno (03/2015)
o Rich Bowen (04/2015)
ISSUES
* There are no issues requiring board attention at this time.

Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* Things have been extremely slow and quiet. I expect once we need to
actually *use* Steve again, things will pick up.
COMMUNITY
* The last 2 new committers were added in July 2013; since then there
has been no new committers or PMC members.
ISSUES
* There are no issues requiring board attention at this time.

Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* Things have been quite slow. Discussion on how and when to roll
a release will be started on the dev list.
COMMUNITY
* The last 2 new committers were added in July 2013; since then there
has been no change.
ISSUES
* There are no issues requiring board attention at this time.

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* The project DOAP file was created, as requested and required.
* Alan Cabrera has been be working on documentation
* The current codebase of Steve was used during the annual ASF
Members Meeting, the 1st time since the project was created
and the codebase "moved" to Steve. A few code changes were required
and the codebase worked perfectly.
* Discussion on how and when to roll a release will be started on
the dev list.
COMMUNITY
* The last 2 new committers were added in July 2013; since then there
has been no change.
ISSUES
* There are no issues requiring board attention at this time.

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* We are on-task to create a project DOAP file, as requested and
required.
* Alan Cabrera will be working on documentation
* We assume that additional suggestions and improvements will result
from the Annual ASF Members Meeting coming up, since that is the
main use-case for Steve.
COMMUNITY
* The last 2 new committers were added in July 2013; since then there
has been no change.
ISSUES
* There are no issues requiring board attention at this time.

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* Both the STeVe website [1] and JIRA [2] have been setup.
Thx goes to Alan Cabrera and Sam Ruby, respectively. List
traffic is quite slow.
COMMUNITY
* There has been no change in committers or members since
June 2013.
ISSUES
* There are no issues requiring board attention at this time.
[1] http://steve.apache.org
[2] https://issues.apache.org/jira/browse/STEVE

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* Activity has slowed down quite a bit since last report. However,
the project has been referred to by other external entities
looking for STV voting tools.
COMMUNITY
* Since the last report, when we added 2 new committers, there has
been no change.
ISSUES
* There are no issues requiring board attention at this time.

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* The Apache Steve website frame is up. A logo has been selected
and work regarding populating the website will commence.
* The code was used in the Incubator PMC Chair election. This
was the 1st use of the tranferred code under the official Steve
repo.
* Work and discussion regarding porting the current Perl-based code
to Python has started. We have baselined Python 2.7.
* A REST-api and use of Sphinx is being discussed and whiteboarded.
COMMUNITY
* Since the last report we have added Alan Cabrera and Sean
Kelly as new committers.
ISSUES
* There are no issues requiring board attention at this time.

DESCRIPTION
Apache Steve is a toolset implementing STV voting capability and
counting.
RELEASES
* We are working towards a 1.0.0 release, based on the migration
of the old ASF-specific codebases.
CURRENT ACTIVITY
* Website development is in the process of being finalized. We have an
agreed-upon logo that will be used. We need to add 'TM' to the logo
however, which is being done.
* It is expected to use the formal release of Steve for the annual
ASF members meeting in May.
COMMUNITY
* No change.
ISSUES
* There are no issues requiring board attention at this time.

Apache Steve is up to a somewhat slow start, with the SVN import
being the main item to be resolved.
DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* All Steve mailing lists, jira, wiki, etc. are set up per
INFRA-5082 [1].
* Discussion continues on the dev mailing list regarding the SVN
import issue in INFRA-5169 [2].
COMMUNITY
* No new committers or PMC members
ISSUES
* There are no issues requiring board attention at this time.
[1] https://issues.apache.org/jira/browse/INFRA-5082
[2] https://issues.apache.org/jira/browse/INFRA-5169

DESCRIPTION
Apache Steve is a collection of tools and programs used by the
ASF to implement the STV voting system and tallying of results.
RELEASES
* No releases yet.
CURRENT ACTIVITY
* All Steve mailing lists, jira, wiki, etc. are set up per
INFRA-5082 [1].
* Discussion continues on the dev mailing list regarding the SVN
import issue in INFRA-5169 [2].
* Dev list activity peaked at 17 messages in August 2012, and
is down to 7 in September 2012. No commits list activity yet
as we are waiting for SVN import to occur.
COMMUNITY
* No new committers or PMC members
ISSUES
* There are no issues requiring board attention at this time.
[1] https://issues.apache.org/jira/browse/INFRA-5082
[2] https://issues.apache.org/jira/browse/INFRA-5169

* Summary
No board-level issues at this time.
The project was established just a few weeks ago, and is currently
bootstrapping itself into existence. Version control, mailing lists,
and the wiki have been set up. See [1] for more details.
The project is currently reviewing issue tracker options, and its
options for preserving development history of the formerly-private
voter tools code. Greg Stein is producing an initial SVN dump as part
of this effort [2].
[1] https://issues.apache.org/jira/browse/INFRA-5082
[2] http://s.apache.org/yF

Establish the Apache Steve Project

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 <jim@apache.org>
* Chris A. Mattmann <mattmann@apache.org>
* Sam Ruby <rubys@apache.org>
* Greg Stein <gstein@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.
Special Order 7A, Establish the Apache Steve Project, was
approved by Unanimous Vote of the directors present.