altstoreio / altstoreio/AltStore
Question about issue & PR maintenance
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 14.4k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that for a prolonged period of time, there was no activity from project owners in the issue or PR section of this repository.
This not only led to many unanswered questions and not triaged bug reports, but also to duplicates and spam issues not being closed.
On top of that, the community is still putting work, time & effort into submitting PRs that are not getting reviewed.
If issues created here won't be taken care of, this should be made clear to the community. Same goes for PRs.
It would be great if one of the maintainers (I see that @rileytestut was pushing to this repository less than 24 hours ago) could share what their maintenance strategy for this issue tracker and the PR section of this repository is.
Thank you!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
There are no files, tests, or entry points named in the issue. Read the issue and its existing comment thread first, then review the repository's issue and pull-request activity. Done would require a maintainer-defined maintenance strategy for triage, duplicate and spam handling, unanswered questions, and PR reviews.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100