Anonymous user
Get involved: Difference between revisions
mooore detail
imported>Brittag (updating documentation link; removing extra newlines) |
imported>Brittag (mooore detail) |
||
| (One intermediate revision by the same user not shown) | |||
Line 17:
The source code is open and [https://github.com/openhatch/oh-mainline in Github]. We encourage you to submit patches, too -- and we'll mentor you to make sure your changes can be deployed as quickly as possible. You can read more on this page: [http://openhatch.readthedocs.org/en/latest/getting_started/index.html Getting started with the OpenHatch code].
You can join the [http://lists.openhatch.org/mailman/listinfo/devel development mailing list], where people discuss ideas and improvements for the website (code, user interface, everything).
The [[Main Page]] of this wiki has even more ideas for contributing to OpenHatch.
We welcome people with any degree of experience in programming or web tools. We mean it; it's a website, and it's imperfect, so we know there is something every single person can contribute.
=== Organize events ===
Check out the [http://openhatch.org/events/ list of events we organize] and consider if you want to run one of these within your community.
Our main event project is [http://campus.openhatch.org/ Open Source Comes to Campus]. If you're affiliated with a college (such as a student, staff/faculty, or alumnus), you can help organize an event. Unaffiliated people can also volunteer to teach at a nearby event, make your open source project easy to contribute to for students, help us find company sponsors, and [https://github.com/openhatch/open-source-comes-to-campus contribute to the curriculum]. If you're interested in any of this, you're invited to email us (hello@openhatch.org) or email the [http://lists.openhatch.org/mailman/listinfo/osctc-planning OSCTC planning mailing list].
=== Donate ===
| |||