New package acceptance policy and maintenance
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
I've noticed an increasing number of new applications being submitted, many of them apparently AI/vibe-coded these days.
Problem is like this:
(borrowed from Reddit)
I'm not against AI-assisted development at all, but I'm concerned about the growing maintenance burden. Every new application means another package that needs to be reviewed, updated and maintained, while we're already struggling to maintain some of the existing ones.
I'd like to hear what @openwrt/packages-write thinks.
Should we be more selective about accepting new applications, perhaps based on upstream activity, actual use case and long-term maintainability?
Contributor guide
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
Start by reading CONTRIBUTING.md and the existing package submission guidance. Review the discussion and current package-maintenance expectations, then identify whether the project agrees on concrete acceptance criteria; done would require an agreed policy and corresponding guidance updates.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100