Consider introducing Issue Templates
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
It may help to introduce some issue templates.
Let's process https://github.com/solid/specification/blob/main/CONTRIBUTING.md (e.g., Work Item Proposals) and other material elsewhere to see what would be useful to template.
- New Work Item Proposal
- Use Case Proposal - This may need to be in https://github.com/solid/user-stories or Work Item repo specific?
- Work Item Change Proposal - identify intended/anticipated change using W3C correction classes (issue should be for "significant" classes 3-5).
- Dedicated Meeting Proposal (topic, time, location, focus..)
- ...
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, especially the Work Item Proposals guidance, then review the linked user-stories repository and W3C correction classes. Determine which proposal types belong in this repository and define templates for the agreed categories, including their required information; done means the selected templates reflect the project’s contribution process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100