Participate
First thanks for your interest in the OpenRefine community. OpenRefine is 100% supported by volunteer and we are always looking for new participant to jump in!
Interested to participate in the development of OpenRefine? You can help to
- Develop the next version
- Develop the Documentation and Support other Users
- Promote OpenRefine around you!
The discussion list is the best place to engage with the rest of the community and ask questions!
Develop the Next Version
You have some developers skills and want to help fix current bug and develop the next release of OpenRefine? Log in on GitHub and fork OpenRefine repository. We accept pull request on a regular basis.
You’ll find more information regarding OpenRefine architecture in the Documentation for Developers wiki section.
You can help us to fix open issue or propose new enhancement using the Issue List.
Documentation and Support Users
Not a coder but still want to help? No worries you can help OpenRefine to grow in many ways.
Help us to maintain the wiki
Help us to maintain OpenRefine documentation up to date. See the list of what need to be done, or come up with your own improvement.
The wiki is written in an easy wiki markup languge nammed Creole in order to let anyone participate. See the Creole Cheat Sheet.
Anyone with a GitHub account can edit the documentation.
Answer other questions
Anyone is invited to ask questions regarding OpenRefine usage on the mailing list. You can keep an eye on it and answer when
Share your tutorials
Are you writting tutorial on your own platform (blog, website, wiki …)? Let us know by email (info@openrefine.org), twitter (@OpenRefine) or directly by editing the External Resources wiki page.
We will also add it to the OpenRefine Custom Search Engine
Promote OpenRefine in Public Events
Organizing a workshop or presentation OpenRefine in your city? Add your event details in our wiki event page or give us a shout on twitter so we can spread the word!
The event page also list previous presentations as catch up and source of inspiration for your presentation!
Current & Previous Contributors
Current
- Lead Developer: Tom Morris - @tfmorris - Github
- Sponsor, Tester, Documentation: Thad Guidry - @thadguidry - Github
- Documentation & Community: Martin Magdinier - @magdmartin - GitHub
- See list of all recent code contributors
Previous Contributors
This software was created by Metaweb Technologies, Inc. and originally written and conceived by David Huynh dfhuynh@google.com. Metaweb Technologies, Inc. was acquired by Google, Inc. in July 2010 and the product was renamed Google Refine. In October 2012, it was renamed OpenRefine as it transitioned to a community-supported product.
They helped to develop Gridworks and Google Refine (in chronological order):
- David Huynh dfhuynh@google.com
- Stefano Mazzocchi stefanom@google.com
- Vishal Talwar vtalwar@google.com
- Jeff Fry jfry@google.com
- Will Moffat wdm@google.com
- James Home jameshome@google.com
- Iain Sproat iainsproat@gmail.com
- Tom Morris tfmorris@gmail.com
- Heather Campbell campbellh@google.com
- Thad Guidry thadguidry@gmail.com
- Paul Makepeace paulm@paulm.com
- Tomaž Šolc tomaz.solc@zemanta.com
- Gabriel Sjoberg GabrielSjoberg@gmail.com
- Rod Salazar rodrod.salazar@gmail.com
- pxb pxb1988@gmail.com