Tag repositories?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 7
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
Following zopefoundation organization idea to put a maintained label to repositories where ongoing maintenance support is expected, should we do something similar?
i.e. names totally up to discussion and an example:
plone core:Products.CMFPloneplone add-on:plone.app.mosaicvolto:plone.volto(voltois an obvious choice as well 😆 )plone classic ui:plonetheme.barcelonetainfrastructure:documentation,meta...
This way, given GitHub search UI, we could easily filter for repositories when searching for things, specially given that we have +350 repositories (already excluding archived ones).
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 with the proposal in issue #73 and review the suggested repository categories and example names. The names and scope are explicitly open to discussion; done would require an agreed taxonomy and a defined way to apply it so GitHub search can filter the organization’s repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100