# Contribution phase: instructions for developer applicants

**URL:** <https://forum.openrefine.org/t/contribution-phase-instructions-for-developer-applicants/604>\
**Category:** Outreachy-GSoC\
**Created:** [March 12, 2023, 8:30am UTC](https://forum.openrefine.org/t/contribution-phase-instructions-for-developer-applicants/604 "2023-03-12T08:30:56Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![antonin\_d](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/antonin_d/32/32_2.png) [@antonin\_d](https://forum.openrefine.org/u/antonin_d)\
**Post date:** [March 12, 2023, 8:30am UTC](https://forum.openrefine.org/t/contribution-phase-instructions-for-developer-applicants/604/1 "2023-03-12T08:30:56Z")

</div>

Hi all,

Since the [other thread](https://forum.openrefine.org/t/welcome-and-guidelines-to-the-outreachy-ux-design-internship-applicants/567/31) about design Outreachy applicants is also attracting developers looking for guidance, here is a dedicated thread for those who want to apply our development projects in Outreachy.

In the contribution phase, we are asking you to tackle some issues in OpenRefine. Those issues should not be in the scope of the project you intend to apply for (since that work will happen during the internship itself). We just want to see that you are capable of tackling some smaller issues independently and that you have been able to go through the prerequisites for that, such as setting up your development environment.

We have a fairly complete guide about how to tackle your first issues in OpenRefine as a developer:

> **[Contributing | OpenRefine](https://openrefine.org/docs/technical-reference/contributing#your-first-code-pull-request)**
>
> Please read the general guidelines on contributing to OpenRefine first, then review the information on reporting and tracking issues, and on making your first pull request below)

We also have a list of issues which should be appropriate for newcomers:

> **[Issues · OpenRefine/OpenRefine](https://github.com/OpenRefine/OpenRefine/issues?q=is%3Aopen%2Bis%3Aissue%2Blabel%3A%22good%2Bfirst%2Bissue%22)**
>
> OpenRefine is a free, open source power tool for working with messy data and improving it - Issues · OpenRefine/OpenRefine

You are also welcome to tackle issues outside of that list if you feel like you are equipped to work on them. In any case, we cannot pick the issue for you, as we do not know which areas of OpenRefine you are familiar with and what your interests are.

When you start working on an issue, please add a comment on the issue asking to be assigned to it, so that we avoid duplication of effort.

If you are stuck, please reach out on the forum and we will try and help you to progress.  
The contribution phase of Outreachy is a pretty intense period for existing OpenRefine developers as we get a lot of questions and pull requests to review, so we thank you for your patience on this.

Thank you for your contributions and good luck!

---

_[View the full topic](https://forum.openrefine.org/t/contribution-phase-instructions-for-developer-applicants/604)._