Initial commit

This commit is contained in:
Marton Kiss 2014-04-23 03:23:19 +02:00
commit d918c79ce8
3 changed files with 70 additions and 0 deletions

29
README.md Normal file
View File

@ -0,0 +1,29 @@
OpenStack Community portal static pages
=======================================
This repository holds the static content of groups.openstack.org website. You
can easily add or modify new content using the standard
[OpenStack CI workflow](https://wiki.openstack.org/wiki/Gerrit_Workflow).
Structure
---------
Every .md file here define a specific page of the site, and consits of
a yaml style header to describe meta informations like title of the
page, content path, menu item, etc. and a markdown body.
Example:
```
---
title: Organizer tips
path: tips
menu: Organizer tips
---
Contents
========
Content goes here...
```

10
hackaton.md Normal file
View File

@ -0,0 +1,10 @@
---
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
- 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.

31
organizer-tips.md Normal file
View File

@ -0,0 +1,31 @@
---
title: Organizer tips
path: tips
menu: Organizer tips
---
Contents
========
- 1.1 Purpose
- 1.2 What is an OpenStack User Group
- 1.3 What OSUG exist?
- 1.4 Starting a new OpenStack User Group
- 1.5 Operating a user group
- 1.6 Running a Hackathon
Purpose
-------
The OpenStack User Group HOWTO is intended to serve as a guide to founding, maintaining, and growing a GNU/Linux user group. OpenStack is Open source software for building private and public clouds. If you want to know more about OpenStack go to http://openstack.org
What is an OpenStack User Group
-------------------------------
The OpenStack User Groups are informal associations of people around the world that meet to discuss about OpenStack, share knowledge and experiences. These are important entities for the OpenStack project as they help by spreading awareness, recruit developers and users and more. The user groups don't have a direct relation with the OpenStack Foundation even though the members of the user groups can be members of the OpenStack Foundation and/or be a member of the OpenStack User Committee. It is important to note that these user groups include developers, operators, end-users, ecosystem partners, and distribution providers. So we are defining a user more broadly than usual.
What OSUG exist?
----------------
The full list of OpenStack User Groups is maintained on OpenStackUserGroups. Before starting a new OSUG consult that list and find one in your area. The point is that starting a user group is a significant undertaking, which should be commenced with all relevant facts and some appreciation of the effect on other groups. If you don't find one on the list, ask on the mailing list community@lists.openstack.org of the User Group team.