Survey proposals for missing information
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- HTML
- Stars
- 336
- Forks
- 63
- Avg merge
- 12h
- Merged PRs (30d)
- 8
Description
Depends on https://github.com/tc39/beta/issues/59 -- We want to survey all proposals (starting with stage 3 for now) for what kind of information is missing. For each proposal we can use the checklist outlined in #59 and check off what is available in the proposal and what is missing.
Once that is done, add it to this issue, and open an issue on that proposal with which fields are missing
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 checklist in issue #59, then review all stage 3 proposals and record which fields are available or missing. Add the survey results to this issue and open an issue on each proposal describing its missing fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100