OpenRefine / OpenRefine/openrefine.org
Blog post about OpenRefine's governance transitions
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
Publish a blog post that announces OpenRefine's governance transitions (creating an 'ambassador council', other changes), the expected transitions in the next months, + asking for feedback.
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
The issue names no file, test, or entry point, so first locate the blog content structure in the openrefine.org repository and review existing post conventions. Gather the governance transitions and expected next-month changes, then publish a post announcing them and requesting feedback.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100