Suggestion: Add `ROADMAP.md` with the roadmap for versions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
Summary
It's kinda hard from an outside perspective to know what is on versions such as v3. It would be good to publish a md file with the project roadmap so that outside contributors know what to prioritise and to contribute to the correct scoped work. We used roadmaps at webpack-cli when we defined project-critical work.
Alltough the webpack-cli roadmap was very simple, it was a good idea and should/could be adopted.
Webpack core also had this process.
💬 Description
See above
Why do we need it?
See above
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 issue’s proposal for a new ROADMAP.md and review how the project currently communicates version scope, including v3. The issue does not identify source files or tests to run; done would mean an agreed roadmap is documented in ROADMAP.md so outside contributors can identify priorities and scoped work.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100