OpenRefine / OpenRefine/openrefine.org
Create Contributor Pathways
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
This ticket follows this forum thread and focuses on the first playbook named: Contributor Pathways.
This ticket is currently a placeholder to request feedback. An early draft of the playbook structure is available in this public Google Document (only section 2Contributor Pathways). I do not plan to open a PR until the content is more advanced in the Google Doc.
I will open separate tickets and PRs for the two other handbooks.
You can provide your feedback on this ticket, in the forum thread, or in the Google Doc as it suits you.
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 Contributor Pathways section in the linked Google Document and review the forum thread for the requested feedback. The issue is explicitly a placeholder and says no PR will be opened until the content is more advanced. Done means the playbook has matured through feedback and is ready for a separate PR.
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