Project Dead? Does it need more maintainers?
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Is this project dead?
Are there not enough project maintainers? @indutny Do you see a need for them within this project?
There are a number of PRs and Issues that have had no activity or have stalled progress. (Some even from a couple years ago)
Additionally, there are also some deviations RFCs that need to be/have addressed in PRs (Ex: RFC 5753, RFC 6598...)
No one can expect `indutny` to spend hours on an open source project because it is a dependency for theirs.
They have a life.
That being said there needs to be steps taken to ensure the future of this project:
- A selected set of active package maintainers to keep this package up-to-date and improve upon it as standards/best practices change.
- A formalized `CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md`
I am by no means the correct person for that.
There more qualified people with more time than I do currently.
But who ever has the time and wants to help with maintaining this package, please speak up.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the stalled pull requests and issues referenced in the discussion, then check the project's current contributor guidance. The issue names CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md as possible documentation gaps; done would require an agreed maintenance plan and finalized project documents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100