sktime governance widening of participation - design issue

[fkiraly]

This issue collects material on the incoming widening of sktime governance to the user base.

• timeline of implementation
• governance structure
• governance mechanisms

This is as a basis for discussion (my thoughts in prep for the meeting) and not final, all are invited to comment.

Related/earlier issues from the main sktime repo:

• [GOV] sktime governance iteration and upcoming elections (Mar/Apr horizon) sktime#4234

timeline

timeline for community meetings

• Fr 5pm UTC, tbd
• Mar 10 - short-term model, elections
  • discussion of model, suggestions
• Mar 17 - short-term governance committee first meeting
  • admin and planning
  • short-term model discussion continued
• Mar 24 - mid-term, charity incorporation
  • intro to mid-term models, discuss options
  • decision on short-term model
  • planning elections
• onwards: bi-weekly

timeline for 1st elections

1st elected sktime committee
(exact dates tbc)

• w/c Apr 3 - election rules published
• w/c Apr 10 - voter registration
• w/c Apr 24 - 1st round elections

update Apr 3: likely +2-4 weeks to the above (emergent admin and easter holidays)

short-term vs mid-term

short-term: interim governance committee

• finalizes governance structure endpoint
• oversees 1st round of elections
• members can stand for elections (given eligibility)

mid-term:

• regular election schedule
• charity incorporation

governance structure

roles

• community representatives
  • user representatives
  • outreach & opportunity
    • special role: community admin; moderator
  • developer
    • special developers: architect; release manager
• community council
  • 3 times 1-2 slots - advanced versions of community rep
  • president, treasurer, secretary
• code of conduct committee

Eligibility:

• eligibility to vote
  • on all-contributorsc
• for roles, role-specific requirements
  • users: need to submit user requirement summary (use case, needs, roadmap preferences)
  • outreach & opportunity: any small contribution & admin/outreach
  • developer: any small contribution & code
• for community council: more contributions, similar to Wikipedia model

votes, electorate

• eligibility to vote = on allcontributorsrc, has name and verified public acct (email, linkedin, etc)
• on committees: at most one vote per org (companies, universities); contracted employment counts
• 3 roles - users, devs, outreach - have equal vote on any committee

elections - reps and CC

similar to charity model:

• term limitation 3 years
• 1/3 re-elected every year
• anyone can stand for election (subject to eligibility)
  • must have proposer and seconder (2 other people)

pre-election phase:

• all candidates must write policy & contributions document
• presented jointly to electorate, similar to Wikipedia procedure
• at least 2 weeks before election

scope:

• for representatives
• for council
• not for CoC committee (US supreme court like mechanism)

CoC committee appointment

• appointed until resignation
• by absolute majority of CC
• max 1 person added per election period (1Y)
• start with committee of 3

intention of rules: to mitigate populist/political maneuvers (e.g., pack with loyalists), ensure stability in judication and arbitration

charity incorporation

mid-term intention is charity incorporation

structure intended to map closely on "standard" charity structure, compare UK model governing documents

• president, treasurer, secretary
• representatives = members
• elections = elections in standard charity models
• budget reporting = as required by charity

governance mechanisms

regular council meetings

• at least once per month
• regular slot, public
• minuted (by secretary or in delegation)
• quorum of council required
• topics can be tabled by electorate (3 days advance notice to secretary)

deciding on governance model changes

• not subject to PR rules
• before vote must be presented at least at 3 readings, in regular meetings
• 2-tier vote: reps, then CC
• 20 signatures by non-reps (electorate) can force public vote - non-binding, but must be conducted

opportunities transparency

• council must publish any opportunities arising from/to sktime to representatives
• opportunities include requests for consultancy, opportunities to present, job ads
• may be preceded by background checks or initial discussions, but cannot be "consumed" without publishing

financial transparency

• treasurer must track and publish monthly budget
• substantial expenditures (>1k) must be presented, approved, minuted approved at 3 separate meetings
• approval by CC majority

arbitration and code of conduct

CoC committee responsibilities:

• CoC enforcement
• arbitration in community disputes
• oversee election process
• check and confirm eligibility requirements

[fkiraly]

update on timelines for elections (or more generally governance design) - we're working on design, but due to easter holidays and other emergent admin, we're a few weeks behind.