A New Governance Structure: SEP 2 Revision - Final Comment Period #80
Conversation
Co-authored-by: Nabil Freij <nabil.freij@gmail.com>
Co-authored-by: David Stansby <dstansby@gmail.com>
Co-authored-by: David Stansby <dstansby@gmail.com>
Co-authored-by: Will Barnes <will.t.barnes@gmail.com>
Co-authored-by: Albert Y. Shih <ayshih@gmail.com> Co-authored-by: David Stansby <dstansby@gmail.com>
Co-authored-by: Albert Y. Shih <ayshih@gmail.com>
Co-authored-by: Steven Christe <ehsteve@users.noreply.github.com>
There was a problem hiding this comment.
See my comment, but I don't like "active" in "active Project Custodian" to denote a non-emeritus status. I wonder if instead we get rid of the use of "active" entirely, and have a sentence in the emeritus section saying that for all other sections in the document, "Project Custodian" refers only to non-emeritus custodians.
|
Thanks for the feedback @ayshih I have removed all use of "active Project Custodian" and used non-emeritus where I really felt it needed to be clear. |
| The organization consists of an executive director, an advisory board, and the | ||
| developer community. The goal of the proposed structure is to provide and | ||
| promote community input into the project. | ||
| | discussion | <https://github.com/sunpy/sunpy-SEP/pull/62> | |
Co-authored-by: Albert Y. Shih <ayshih@gmail.com>
What counts as approval? Any form of reaction here, like a 👍 reaction? |
If you approve the PR via a review, I think that would be the simplest. |
| @@ -3,203 +3,288 @@ | |||
| | SEP | 2 | | |||
| |---------------|---------------------------------------------------------| | |||
| | title | SunPy Organization Definition | | |||
There was a problem hiding this comment.
| | title | SunPy Organization Definition | | |
| | title | An Updated SunPy Project Organization Definition |
| ## Rationale | ||
|
|
||
| This SEP describes the second major iteration of the governance for the SunPy Project. | ||
| The objectives of the rewrite were to adapt the governance for the changes the project has seen since the first iteration of this document was written in 2014. |
There was a problem hiding this comment.
| The objectives of the rewrite were to adapt the governance for the changes the project has seen since the first iteration of this document was written in 2014. | |
| The objectives of this update are to optimize the governance based on our experiences running the project since 2014 when the original governing SEP was written. That original governance structure was modeled after a non-profit company structure, assumed a very committed board, and intertwined project finances with board responsibilities. The project has since matured and responsibilities for project management should be fully given over to the community while a smaller and leaner board is maintained to provide oversight. |
|
|
||
| This SEP describes the second major iteration of the governance for the SunPy Project. | ||
| The objectives of the rewrite were to adapt the governance for the changes the project has seen since the first iteration of this document was written in 2014. | ||
| The rewrite aimed to detail a governance structure, which strives to be lightweight, while being designed to enable the project to grow, and facilitating more input from the wider SunPy community. |
There was a problem hiding this comment.
| The rewrite aimed to detail a governance structure, which strives to be lightweight, while being designed to enable the project to grow, and facilitating more input from the wider SunPy community. | |
| The rewrite aims to detail a governance structure which is lightweight, community-driven, and allows the project to grow. |
|
|
||
| ## The SunPy Project | ||
|
|
||
| The primary mission of the SunPy Project is **To develop and facilitate a high-quality, easy-to-use, community-led, free and open-source solar data analysis ecosystem based on the scientific Python environment**. |
There was a problem hiding this comment.
| The primary mission of the SunPy Project is **To develop and facilitate a high-quality, easy-to-use, community-led, free and open-source solar data analysis ecosystem based on the scientific Python environment**. | |
| The mission of the SunPy Project is **To develop and facilitate a high-quality, easy-to-use, community-led, free and open-source solar data analysis ecosystem based on the scientific Python environment**. |
| ## The SunPy Project | ||
|
|
||
| The primary mission of the SunPy Project is **To develop and facilitate a high-quality, easy-to-use, community-led, free and open-source solar data analysis ecosystem based on the scientific Python environment**. | ||
| This includes but is not limited to the following tasks: |
There was a problem hiding this comment.
| This includes but is not limited to the following tasks: | |
| This mission is supported by the following actions: |
| ### The Advisory Board | ||
| * to advise the Steering Committee, | ||
| * aid in finding funding for the project to ensure the core aims of the project can be met, | ||
| * nominate a Ombudsperson, |
There was a problem hiding this comment.
| * nominate a Ombudsperson, | |
| * nominate an Ombudsperson, |
| a 1-year term is defined to expire on December 31, 2015. Initial | ||
| member of the board shall be (with term length in parentheses): | ||
| * The Advisory Board shall consist of at least 3 members and no more than 5 members. The Advisory Board selects how many members within this range are needed. | ||
| * All members shall serve a maximum of a two-year term, and may be re-appointed at the end of their term. |
There was a problem hiding this comment.
| * All members shall serve a maximum of a two-year term, and may be re-appointed at the end of their term. | |
| * A term on the board shall be 2 years. Members may be re-appointed after their term has expired. |
| member of the board shall be (with term length in parentheses): | ||
| * The Advisory Board shall consist of at least 3 members and no more than 5 members. The Advisory Board selects how many members within this range are needed. | ||
| * All members shall serve a maximum of a two-year term, and may be re-appointed at the end of their term. | ||
| * Membership terms should be staggered so that approximately half the number of members will end their terms in any given year. |
There was a problem hiding this comment.
I would just remove this. Given the minimum requirement of 3 members, it is already required to work this out.
| * The Advisory Board shall consist of at least 3 members and no more than 5 members. The Advisory Board selects how many members within this range are needed. | ||
| * All members shall serve a maximum of a two-year term, and may be re-appointed at the end of their term. | ||
| * Membership terms should be staggered so that approximately half the number of members will end their terms in any given year. | ||
| * The Advisory Board may appoint members to its number up to the maximum number of members. |
There was a problem hiding this comment.
| * The Advisory Board may appoint members to its number up to the maximum number of members. | |
| * The Advisory Board may appoint its own members. |
| * All members shall serve a maximum of a two-year term, and may be re-appointed at the end of their term. | ||
| * Membership terms should be staggered so that approximately half the number of members will end their terms in any given year. | ||
| * The Advisory Board may appoint members to its number up to the maximum number of members. | ||
| * The Advisory Board should work to ensure that the composition of the Advisory Board represents a diverse cross-section of the scientific community with an interest in SunPy. This diversity should consider things such as research topic, career stage, as well as all other forms of diversity. |
There was a problem hiding this comment.
Should this rule apply to all of the components Project Custodians and Steering Committee members?
|
I'd suggest that we add a requirement that the project perform a regular (annual?) user survey whose results would be made public to guide future development. |
While I'm not opposed to the idea of requiring a regular survey, I am opposed to going further and making it annual. I think 2 to 3 years between surveys would be better. |
If you are a member of the SunPy community and you read this SEP and agree (or at least don't strongly disagree) with it, please approve this PR as a way of demonstrating community approval.
Rendered Version of the SEP
This PR is the final version of #62 where most of the discussion has taken place.
The goal of this PR (which actually modifies SEP 2 in the repo) is to be a final comment period, we are not expecting to make any substantive changes during this review. The original PR has been open for more than long enough!
The timeline for the adoption of this proposal is as follows: