Add more detailed description of the advisory board

Open
#460 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Start with the Role Descriptions page linked in the issue and compare its current content with SEP-002 and the supplied advisory board text. Add the mission, member responsibilities, project interaction, meeting cadence, notice, and minutes details there; done means the advisory board description is publicly captured on that page.

Written by the indexing model from the issue text.

Description

SEP-002 is intentionally vague regarding the description of the advisory board and its exact responsibilities. In the process of recruiting an Advisory Board, we've written up a few more details, largely culled from SEP-002, regarding the goals and roles of the advisory board (see below). This information should live somewhere on the Role Descriptions page as it is not fully captured in SEP-002. Adding a section to the Role Descriptions section probably makes the most sense.

Advisory Board Mission Statement

The mission statement of the SunPy Advisory Board is to promote the sustainability and longevity of the SunPy Project. The Advisory Board will carry out this mission by finding sustainable sources of funding for the Project, monitoring that the Project is being run consistent with the approved governance structure, and ensuring that the Project is meeting the needs of the wider solar physics scientific community.

Board Member Role Description

A member of the SunPy Advisory Board should agree with the mission statement of the Advisory Board. Additionally, members of the Advisory Board should be actively involved in the solar physics community in some way, for example, through research, teaching, software development, and/or policy. Notably, members of the Advisory Board do not need to have an in-depth knowledge of any software package under the purview of the SunPy Project nor have explicitly contributed code to any such package. Members of the advisory board should be available to meet once every quarter to advise the Steering Committee. The Advisory Board may appoint its own members and in doing so should work to ensure that the composition of the Advisory Board represents a wide and varied cross-section of the scientific community. Said appointments should consider aspects such as research specialty, career stage, and working location, among others.

How Does the Advisory Board interact with the SunPy Project?

The Advisory Board interacts with the SunPy Project by advising the Steering Committee. The Advisory Board shall meet with the Steering Committee at least every quarter. The Steering Committee shall present the state of the project and future plans at meetings of the Advisory Board on a yearly basis (i.e. every fourth meeting of the Advisory Board). The Advisory Board shall advise and consent on those plans. At least one week (7 days) notice of a meeting shall be provided to all eligible to attend. Notice of meetings shall provide the information necessary to participate in the meeting. Minutes for the meetings shall be recorded and made public as much as is appropriate.

Dominant language
Jupyter Notebook
Stars
24
Forks
38
Avg merge
18h 37m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sunpy/sunpy.org

All issues in sunpy/sunpy.org

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.