w3c / w3c/github-notify-ml-config
Maybe it's time to manage WGs by include files
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
I wonder whether we want people editing a single ginormous file each time they want to add to a WG's notifications. On the other hand, I can see not wanting to introduce new dependency management and complexity.
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
The issue proposes managing WG notifications with include files instead of one large file, but names no files, tests, or entry points. Review the repository configuration to assess the proposed structure and whether added dependency management is justified. The issue does not define completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100