Improvements to the project's transparency
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
This is sort of an umbrella issue to discuss:
- Issue organization
- GitHub projects, milestones, goals
- Minor / major version planning
- Release schedule
- Testing methodology
I'd love the input from the community to know what you'd like to see in terms of this goal.
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
Start with the issue's five listed areas and the community discussion; no files, tests, or entry points are identified. Done would require an agreed, concrete transparency plan covering those areas, but the issue does not define an implementation target.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, release, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100