astropy / astropy/astropy-project

Pathway from contributor to maintainer

Open
#445 3 comments 0 reactions 0 assignees View on GitHub
roadmap :world_map:
Dominant language
TeX
Stars
48
Forks
48
PR merge metrics
No merged PRs in 30d

Description

I think this has been brought up from time to time, but I cannot seem to find an official issue for it. If you find one, we can close this (or that other one) as duplicate.

There is a need to formally document our expectations so a contributor is aware how one can go from being a contributor with no write access to a maintainer with write access. We can start with `astropy` and then downstream can adopt/adapt as needed.

I think this is a pre-cursor for:

* https://github.com/astropy/astropy-project/issues/158

Contributor guide

No contributing guide indexed for this repository

Research direction

Review issue #158 and search this repository for existing contributor, maintainer, or write-access policies before proposing a formal pathway. Done means the Astropy contributor-to-maintainer expectations are documented and agreed clearly enough for downstream projects to adopt or adapt.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.