[Tech debt] Contribution: revise guides
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
- Developer contributions
- Translator contributions
Details
Here are probably all of the associated tickets. We need to revise them, see what's done and what's not. We may need to design the process from scratch---not many things are clear.
-
Who maintains the developer style guides?
-
What languages do we really need style guides for?
My idea is that we don't repeat what can be found elsewhere on the web.
Provide any details you consider necessary.
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 reviewing the linked contribution and style-guide issues, especially the unchecked items, and compare them with the two marked complete. Clarify which guides remain needed, who maintains them, and whether the contribution process needs redesign; the work is done when the relevant guides and process are revised with those responsibilities and scope settled.
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
- 20/100