The Stan Governing Board wants your input! We have put together a proposal for a new type of “official” Stan involvement— tentatively called a Contributor— which will believe will recognize and encourage the impact and involvement of our awesome users. We welcome your comments, including suggestions for the name of this new type of role.
Ways to get (officially) involved with Stan:
These people directly change the code base of the Stan language or one of its interfaces.
- Special privileges: vote on Developer-Only topics; access to Developers section of Discourse; ability to review pull requests
- Responsibilities: abide by Code of Conduct; vote on topics which you feel sufficiently informed about; abstain from voting on topics about which you do not feel informed or impacted
- How to get involved: there has been an informal process in place, but SGB is currently drafting a official proposal for recognizing new Developers
Contributors are enthusiastic users or community members who want to be more involved with Stan.
- Special privileges: voting on any motion not designated Developers-only; participation in working groups around certain topic areas (e.g., “Stan in marketing” or “Stan meetup coordinators”)
- Responsibilities: abide by Code of Conduct
- How to get involved: be nominated (self-nominations are encouraged!), respond with a post on Discourse with a description of what you hope to bring to Stan, and have your nomination seconded by two existing Contributors or Developers
Governing board member
The Stan Governing Board sets the procedures and governance structure for the overall Stan project and manages financial aspects of the organization.
- Special privileges: none as individuals, unless designated by role within SGB (e.g., a NumFOCUS point of contact to approve expenses)
- Responsibilities: meeting attendance, informed decision making, fundraising, stewardship of NumFOCUS-held funds
- How to get involved: nominate yourself during the SGB election cycle each fall; 5 members will be elected to serve. SGB terms are typically one year.
This corresponds to 4 categories of votes that could occur on Stan issues, each with its own group of eligible voters:
Stan electorate-wide: Contributor & Developer
- Scope: Direction/vision of project (anything non-technical); non-binding roadmaps; SGB elections
- Scope: Technical decisions impacting multiple domain areas; binding roadmaps; any subject area-specific topics where Developers in the subject area are unable to achieve consensus
Subject area-wide (e.g., “math library”): Developers in a module area self-identifying as having the necessary domain expertise to make informed decisions
- Scope: Technical decisions that primarily impact a single domain area, with limited effect on other areas
SGB-specific: Current elected SGB member
- Scope: Governance and voting structures; financial decisions for NumFOCUS funds; general execution of direction/vision
Note: References to the Code of Conduct currently mean the NumFOCUS Code of Conduct, since that applies to all NumFOCUS projects in the absence of a project-specific Code of Conduct.
What do you think?