Work with CPC for documentation guidance
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the linked CPC issue 1263 and the discussion referenced in this issue. The payload identifies a proposed working session but does not name files, tests, or a defined outcome, so the completion criteria need to be established with the CPC before implementation can begin.
Written by the indexing model from the issue text.
Description
https://github.com/openjs-foundation/cross-project-council/issues/1263
We discussed on the CPC call and decided that we should have a working session on it. @sheplu are you available next week for the CPC time to work on this?
- Dominant language
- No language data
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bisq-network/support#2181 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
tutorial updates Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
sveltejs/svelte.dev#2241 ·