On Fri, Feb 20, 2015 at 10:19:14PM +0100, Johan Engelen wrote:
> I don't want to push to hard on this, but perhaps I should have
> explained better: isn't one week of Candidacy signup a little short?
> People may want to mull it over just a little.
>
> I vote b., with the Candidacy signup increased by one week:
Fair enough. I was concerned about it dragging out too far, but good
point on people wanting to mull it over.
> Election Schedule
> =================
> * Kickoff Announcement: ${date}
> + Post to inkscape-announce@
> + Publish news item to website
> * Candidacy period Start: ${date}
> * Candidacy period End: ${date + 2 week}
> * Publication of Candidates
> & start of Candidate Q&A: ${date + 2 week}
> * Election Start: ${date + 2 week}
> * Election End: ${date + 2 week + 2 weeks}
> * Results Posted: ${date + 2 week + 2 weeks + 2 days}
>
>
> cheers,
> Johan
Anyone else want to chime in with suggestions (or votes) before I do a
second revision on this?
Bryce
> On 20-2-2015 11:57, Bryce Harrington wrote:
> > A majority vote of the current board members is required for the
> > following matter.
> >
> > Proposal:
> > ---------
> > Adopt the Election Procedure shown in Addendum as the Inkscape Board's
> > official procedure for holding Board Elections. Diverging from this
> > procedure is not allowed without board approval.
> >
> > [ ] a. Accept Election Procedure v.2 as official election procedure
> > [ ] b. Accept Election Procedure, if the following changes are done:
> > __________________________________________
> > __________________________________________
> > [ ] c. Do not accept Election Procedure
> >
> > Votes:
> > ------
> > Bryce Harrington
> > Tavmjong Bah
> > Josh Andler
> > Jon Cruz
> > Ted Gould
> > Johan Engelen
> > MentalGuy
> >
> > Resolution:
> > -----------
> >
> >
> > Background:
> > -----------
> > The procedure detailed in the addendum derives from directions given in
> > past elections, and incorporates ideas from X.org's recent board
> > elections. Notably, in the past we've elected single individuals, but
> > this procedure covers electing several members at the same time.
> >
> >
> >
> > Addendum: election_procedure.txt
> > ---------
> > Inkscape is holding elections for ${NUM_SEATS} new Board Members.
> >
> > ${Introduction_Text}
> >
> > Typically the board votes on things such as project fund expenditures
> > (travel, conferences, marketing materials for events, etc), trademark
> > related issue, other legal issues that arise, etc. The board does not
> > have responsibility currently for technical decisions for the project,
> > and does not handle social/community issues where there are no financial
> > or legal aspects to the problem.
> >
> > Board membership requires a commitment of time: At a minimum you will be
> > expected to participate in votes on the mailing list, which typically
> > occur with a frequency of about 0 to 3 per month. You are required to
> > be on the board mailing list, which has a volume of about 30-50 emails
> > per month; you're not required to participate in the discussions, but it
> > is very strongly encouraged. We also solicit volunteers from the board
> > to serve as as event managers, team leaders, fundraising coordinators,
> > etc. - Again, not a requirement, but we value board members who can
> > shoulder such duties for the project.
> >
> > As specified in Section 6 or our charter we maintain a committee of
> > seven project members. Section 6 reads as follows:
> >
> > "6. Representation of the Project in the Conservancy. The Developers,
> > each a signatory hereto, shall represent the Project in its official
> > communication with the Conservancy. There shall be seven Developers
> > (together, the "Committee"), elected by the community members of the
> > Project listed in the Project's AUTHORS file (the "Community
> > Members"). Each Developer shall continue to serve until he or she
> > resigns from the position. The Developers may be removed from the
> > position at any time by a majority vote of the Community Members. Upon
> > the resignation or removal of a Developer, the Community Members shall
> > elect a replacement Developer to serve on the Committee. The Committee
> > will elect a single individual to communicate with the Conservancy
> > (the "Representative") and shall notify the Conservancy promptly
> > following the election of a new Representative. The Representative
> > will have the authority to instruct the Conservancy on the Project's
> > behalf on all matters. This section may be modified by a vote of at
> > least 3/4 of the Community Members, with the consent of the
> > Conservancy, such consent not to be unreasonably withheld."
> >
> > Election Schedule
> > =================
> > * Kickoff Announcement: ${date}
> > + Post to inkscape-announce@
> > + Publish news item to website
> > * Candidacy period Start: ${date}
> > * Candidacy period End: ${date + 1 week} (Midnight Pacific time)
> > * Publication of Candidates
> > & start of Candidate Q&A: ${date + 1 week}
> > * Election Start: ${date + 1 week}
> > * Election End: ${date + 1 week + 2 weeks} (Midnight
> > Pacific time)
> > * Results Posted: ${date + 1 week + 2 weeks + 2 days}
> >
> >
> > Membership
> > ==========
> > Inkscape developers listed in the AUTHORS file as of ${AUTHORS_DATE} are
> > considered Official Members for purposes of this election, as per our
> > Fiscal Sponsorship Agreement with the Software Freedom Conservancy.
> > Only Official Members may run for the board positions, and only Official
> > Members may vote for them.
> >
> > In this election we will be using an online system to conduct the
> > voting. To vote, you will need to register for an Enfranchised
> > Account.
> >
> >
> > Election Proctor
> > ================
> > The Inkscape Board elects by majority vote an Election Proctor who will
> > run a given election and ensure it's successful completion. The
> > Election Proctor has the responsibility for ensuring the voting is done
> > according to procedure, assuring that the Vote is accurately tallied,
> > and announcing the finalized result of the Vote.
> >
> > Once the vote has been finalized, the selected individual(s) immediately
> > become Board Members.
> >
> > The Community may challenge the Election Proctor's tally within 30 days
> > of the vote finalization, by gathering a number of signatures from
> > Official Members exceeding 2/3rds of the total number of Votes cast
> > declaring the vote to be inaccurate. Should this happen, the Vote is
> > nullified, a new election must be arranged by the Board, with the
> > Election Proctor barred from proctoring future Inkscape votes.
> >
> >
> > Board Election
> > ==============
> > The following Board Members have resigned from their positions and need
> > to be filled by new members:
> >
> > TBD
> >
> > The election process starts with a Candidacy Period during which any
> > Official Member may indicate interest in running for the positions.
> > To register, please email ${ELECTIONS_ADDRESS}, giving your
> >
> > - Name [1]
> > - Current professional affiliation
> > - Statement of contribution to Inkscape or related technologies
> > - A personal statement
> >
> > Alternatively, any Official Member may nominate another Official
> > Member.
> >
> > At the end of the Candidacy Period, the applicants will be reviewed to
> > verify eligibility. The list of candidates will then by published, and
> > the community will have a chance to ask questions on the development
> > discussion list, [email protected].
> >
> > Finally, the election will be held using the Single Transferrable Vote
> > (STV) voting system[2]. This is similar in mechanism to the Instant
> > Runoff Vote (IRV) system we've used in the past[3], but for multi-seat
> > results rather than the single-winner result of IRV. From a voter's
> > perspective it's the same voting procedure: Rank candidates in order of
> > choice with #1 being first choice, and so on.
> >
> >
> >
> > References
> > ==========
> > 1: Pseudonyms are acceptable for registration purposes, but please note
> > that your legal name will need to be provided when officially joining
> > the board as a member, and may be needed on various legal documents
> > which will be publically disclosed for transparency purposes.
> >
> > 2: http://en.wikipedia.org/wiki/Single_transferable_vote
> >
> > 3: Past elections:
> > 2006 Election
> > +
> > http://inkscape.13.x6.nabble.com/Election-process-for-Inkscape-Board-tt2805584.html
> > 2008 Election
> > +
> > http://t48889.graphics-inkscape-development.graphictalk.us/opening-inkscape-committee-nominations-t48889.html
> > 2012 Election
> > +
> > http://inkscape.13.x6.nabble.com/Inkscape-Board-Election-voting-time-tt4965288.html#a4965302
> > +
> > http://inkscape.13.x6.nabble.com/Inkscape-Board-Committee-Nominations-tc4965274.html
> >
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Inkscape-board mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/inkscape-board
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Inkscape-board mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/inkscape-board
