OpenRefine / OpenRefine/openrefine.org

Add curated list of OpenRefine tutorials recommended for new contributors

Open
#265 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
161
Forks
142
Avg merge
6h 10m
Merged PRs (30d)
9

Description

We often have new contributors coming in who don't know anything at all about OpenRefine as a user. They might be coming to the project because they want to gather experience contributing to an open source project (for instance: Outreachy/GSoC applicants), or because we hired them to work in a particular capacity in the project (for instance: hiring a designer, a security consultant, a community manager…)

To onboard those new contributors on the project, it would be helpful to have a pre-defined set of resources we can point them at, to learn how to use OpenRefine. This knowledge of the tool from a user perspective is generally very useful to get involved in the project.

We currently list a few resources in passing in https://openrefine.org/docs/technical-reference/code-contributions but it would be helpful to have a bigger list, more visible (also advertised to other types of contributors, not just developers), where people would be able to find tutorials focusing on certain topics.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing resources in the technical-reference/code-contributions documentation linked in the issue, then inspect how the site organizes contributor and user-facing pages. Curate tutorials by topic and make the list visible to non-developer contributors; done means new contributors can find a clear, useful set of OpenRefine learning resources.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.