split `core/issues-notes` into manageble chunks
Open
Nobody has claimed this yet.
good first issue
refactoring
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Split into issues, github issues, reports and notes.
Should make it easier to support https://github.com/w3c/respec/issues/4097, https://github.com/w3c/respec/issues/3433 etc.
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 core/issues-notes and the linked issues 4097 and 3433 to understand how the current combined notes are used. Split the existing material into issues, GitHub issues, reports, and notes, then verify that the linked use cases are easier to support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100