Grouping Checklists
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 12
Description
There are currently some checklists on different sections of devguide, such as grammar addition checklist and opcode addition checklist and I wanted to discuss adding a checklist for future directives (like from __future__ import <directive>).
Should we group that checklists in a page with divisions, and should we add a checklist for future directives (because it is also a complex process). (I can prepare a patch if agreed)
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
Review the existing grammar addition checklist and opcode addition checklist sections in the devguide, then determine whether they should be grouped on one page. Define the scope of a future-directive checklist and confirm that the documentation structure and checklist content are agreed before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100