Dear all,
Thank you for your interest in the UX internship so far.
We have now developed a more formal strategy how to handle all applications. Please refer to this guide below and try to follow it before making your final contributions.
1) Make sure you’re registered as an interested applicant on the Outreachy dashboard, so far we only have 2 official expressions of interest there.
2) Make sure to get acquainted with OpenRefine before beginning the contribution process.
- Check out the documentation here - OpenRefine user manual | OpenRefine
- Watch some videos - good short intro (OpenRefine Beginners Tutorial - YouTube); good presentation on cleaning data (Data Cleaning with OpenRefine - YouTube); more in-depth on data reconciliation with Wikidata (OpenRefine tutorial (WikidataCon 2021 recording) - YouTube)
- Check out some design documentation already developed for a previous design-inclusive project at OpenRefine - OpenRefine4SDC Design Links - Google Docs
3) Review existing issues on Github that have the tags UX / UI / design discussions:
- Issues · OpenRefine/OpenRefine · GitHub
- Issues · OpenRefine/OpenRefine · GitHub
- Issues · OpenRefine/OpenRefine · GitHub
If you would like to work on a particular issue please write a comment on that issue before you begin your contribution and tag me and Antonin in it (@lozanaross / @wetneb). We will then assign issues to concrete people. We would prefer that only one person works on a particular issue to avoid unnecessary sense of competition and peer pressure.
If you can’t find an unclaimed issue to work on, you can ask us (write a comment below in this thread) for an assignment.
The amount of issues you contribute to is less important than the depth of the contribution, take your time and don’t feel rushed to immediately contribute.
4) Writing new GitHub issues with concrete design suggestions for new, previously unlisted issues.
If you don’t see an issue above that you feel comfortable contributing to, you can also just make general suggestions for UX / UI improvements. Please do that in new Git issues following a similar structure to this issue: Better display of which reconciliation service a specific column is reconciled against · Issue #4824 · OpenRefine/OpenRefine · GitHub (i.e. start with an explanation of what you think is the problem; then make some proposals and include images; indicate additional considerations or context).
Make sure to tag your issues with “UX”, “UI” and also the “outreachy design” label we’ve set up in GitHub for this purpose.
General notes:
- Please be aware that OpenRefine is an open source project without full time staff. This means that even if you make excellent design contributions during the application process, we may not have capacity to develop your designs. What designs get implemented in the final product is usually driven by developer capacity, perceived need in the community (i.e. features that are needed by many users in the community get prioritised), and level of complexity or simplicity of the solution.
- Please keep in mind that the current OpenRefine design framework is also rather limited in terms of implementing cutting edge UX patterns. OpenRefine still uses the old Google design framework (pre-Material design), so various interactions that may seem simple to implement in Angular or React are not possible to implement here, or may require significant development effort and cost/benefit analysis may preclude realisation of the design proposal.
If you have additional questions, please note them in this thread.
Regards,
Lozana