astropy / astropy/astropy-project
Need a plan to keep Astropy Coordinated Packages better maintained
- Dominant language
- TeX
- Stars
- 48
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Astropy Coordinated Packages: https://www.astropy.org/affiliated/#coordinated-package-list
How do we provide resources to keep these packages better maintained and also implement new features? How do we provide development roadmaps? Do we redistribute core maintainers for these? Do we recruit from institutions that use these packages?
Case study (but not the only one): `ccdproc` -- We lost Steve Crawford and Michael Seifert, so only @mwcraig is left to maintain it but he does not have enough time. How do we solve this problem?
xref astropy/astropy.github.com#410
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the Astropy Coordinated Package list and the linked astropy/astropy.github.com#410 discussion, using ccdproc and its listed maintainer changes as the case study. Done would require an agreed maintenance-resourcing approach, development-roadmap process, and decision on recruiting or redistributing maintainers; no file or test is named.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100