openinfra
/
groups-static-pages
Code Issues Proposed changes

Content out of date 

Deprecate content, link to current location.

Change-Id: Ifa2537736e3a0b4d996d9fdfd5aae81ad3b7414d
This commit is contained in:
David F. Flanders 2016-05-13 12:54:12 +10:00 committed by Jeremy Stanley
parent 1106ce3d77
commit 3a9c0497c3
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
hackaton.md
View File

@ -3,8 +3,8 @@ title: Running a hackaton
path: tips/hackaton-howto
---
Running a Hackathon is to benefit both operators and developers who want to learn OpenStack AND experienced OpenStack devOps who want to teach new batch of stackers. To run a Hackathon, you will need the following experience
This page is deprecated. For further information on OpenStack Application Hackathons, please send an email to the User Committee mailing list for further information:
- You will need to know how to use and navigate openstack, python, git, maven, launchpad, gerrit, jenkins, and zuul. The OpenStack Install Guide and the OpenStack Training Guides are great sources to source build OpenStack. The rest of the tools are a bit more completed. The OpenStack community training can get you started http://docs.openstack.org/trunk/training-guide/content/getting-tools-and-accounts.html. Running a Hackathon will require some real experience of how these tools work and interoperate.
- Once you have some of the basic experience you will need to connect with a user group if you are not already running one. See above on details OpenStackUserGroups
- Each Hackathon will need at least one person ready to help the "students" with problems. Hackathons are hands on "teaching" and learning sessions.
user-committee@lists.openstack.org
https://www.openstack.org/foundation/user-committee/