Browse Source

Update Organiser Tips, new user-group faq page

The Organiser Tips page on the groups portal was sadly
almost blank. This patch brings all the content from the wiki
(https://wiki.openstack.org/wiki/OpenStackUserGroups/HowTo )
and modernises it.

Also a new section started aimed at people who aren't group
organisers but want to know what a user group is.

Change-Id: I526f29c0e89158298b90cc875864a819b00e6ba6
changes/00/231400/3
Tom Fifield 3 years ago
parent
commit
914ecae449
2 changed files with 198 additions and 15 deletions
  1. 130
    15
      organizer-tips.md
  2. 68
    0
      what-are-user-groups.md

+ 130
- 15
organizer-tips.md View File

@@ -6,26 +6,141 @@ menu: Organizer tips
6 6
 
7 7
 Contents
8 8
 ========
9
+The OpenStack User Group HOWTO is intended to serve as a guide to founding,
10
+maintaining, and growing an OpenStack user group.
9 11
 
10
-- 1.1 Purpose
11
-- 1.2 What is an OpenStack User Group
12
-- 1.3 What OSUG exist?
13
-- 1.4 Starting a new OpenStack User Group
14
-- 1.5 Operating a user group
15
-- 1.6 Running a Hackathon
12
+Starting a new OpenStack User Group
13
+-----------------------------------
16 14
 
17
-Purpose
18
--------
15
+Based on the experiences gathered by other OpenStack user groups, like the
16
+San Francisco User Group, the questions and answers below will help guide
17
+you to creating a sustainable user group. We have an
18
+[Ambassador Program](https://groups.openstack.org/ambassador-program),
19
+which you can ask for help for mentoring through the process.
19 20
 
20
-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
21
+Here are the steps to create a new OpenStack User Group:
21 22
 
22
-What is an OpenStack User Group
23
--------------------------------
23
+1. Contact your local [Ambassador](https://groups.openstack.org/ambassador-program),
24
+   they're here to help you through the process!
25
+2. Add yourself to the mailing list for
26
+   [community organisers](http://lists.openstack.org/cgi-bin/mailman/listinfo/community).
27
+3. Check the [User Group List](https://groups.openstack.org/) to double-check
28
+   there is no existing group nearby. If there is a group in your city,
29
+   contact their organisers and offer to help. Note that some countries have
30
+   an umbrella group that covers the entire country.
31
+4. It takes a lot of work to start and operate a user group, so make sure that
32
+   you get at least one additional person to help you and act as a backup.
33
+5. Find your audience. Who do you want to attract to your user group meetings?
34
+   Where do they live and work? What will their skill level be? What content
35
+   do they want?
36
+6. Ask for more volunteers - many people are willing to assist with tasks like
37
+   registration, contacting lecturers, hosting meetings, sending reminders,
38
+   taking photos.
39
+7. [Register a new group](https://groups.openstack.org/node/add/group) in the
40
+   Groups Portal. Ensure you fill in the description and add all the details
41
+   to allow your audience to find you. Once your Ambassador approves the
42
+   request, add your co-organisers as administrators.
43
+8. Announce the new group on the openstack mailing lists and any social media
44
+   that is popular in your location.
24 45
 
25
-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.
46
+Working with different skill levels
47
+-----------------------------------
48
+Even though you may be an OpenStack expert, not everyone who comes to your
49
+group will be. Here are some tips for the various skill levels we've observed:
26 50
 
27
-What OSUG exist?
28
-----------------
51
+- Beginner: If you want to attract new users to OpenStack then you will want
52
+  to discuss the architecture and the basics of how to use OpenStack.
53
+  There are many suitable presentations available online.
54
+- Intermediate:  Developers and operators that want to understand how to make
55
+  OpenStack production ready for their organization need a place to discuss
56
+  setups, review and share topics like details on APIs, package installation,
57
+  and configuration. You might teach new attendees how to use devstack, or
58
+  hold bug squash hackathons for developers.
59
+- Advanced: Some groups tend to call this a ''devOps meeting''. The topics
60
+  are generally about blueprints, advanced operations, or specific deep dive
61
+  into part of OpenStack like Neutron. You may ask OpenStack developers for
62
+  assistance with the advanced meetings, even if they can only present
63
+  remotely.
29 64
 
30
-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.
65
+Planning your meetings
66
+----------------------
67
+A surprising amount of effort goes into making an informal gathering
68
+successful. Here are some quick tips.
69
+
70
+- Attendance: For free events, it's not uncommon that 30% of people who
71
+  register don't show up, so plan accordingly. Track the no-show rate for
72
+  improved planning.
73
+- Sponsorship: There are many vendors in the OpenStack community who are
74
+  happy to provide space, food and drink, or money in exchange for placing
75
+  their logo on your group page, putting up banners or giving a 5-minute pitch.
76
+  Go through the [list of companies](http://openstack.org/community/companies/)
77
+  and contact who you can in your area. If the company is serious about being
78
+  involved they will help you out! Ask them if they can do a short talk on
79
+  their company's involvement with OpenStack.
80
+- Food and drink: If you can afford it or have a sponsor, it makes the
81
+  meetings much more sociable.
82
+- Promotion: Look for local sysops/sysadmin/network ops email lists or online
83
+  forums and promote your events there to get folks along. Also write to the
84
+  Heads of Schools of the University IT faculties in the area and
85
+  invite them and their school along.
86
+- Content: Your topics will your different types of users who attend. Have a
87
+  look at other user groups on the groups portal to see what they have done
88
+  recently, or ask your ambassador for help. An interesting user story is
89
+  always a good  bet. Once you have an idea of content, you can contact
90
+  potential speakers.
91
+- Location: This is critical part of your user group. It makes your life much
92
+  easier if you can find a location that will be there long term. There may
93
+  be a local function room that is under-utilized early in the week, or
94
+  cloud computing companies in your area may have a conference room. Local
95
+  universities, technical colleges or co-working spaces may also be interested.
96
+  Check other non-OpenStack user groups in your city. And ask your friends,
97
+  relatives and colleagues about other meetings they have gone to. Free spaces
98
+  can be found basically everywhere in the world.
99
+- Materials: there are some basic meeting materials you will want to go ensure
100
+  are present. White boards, projectors, tables and chairs are the basics.
101
+  The location you secured may have a few of these things, but don't assume
102
+  they do.
103
+- Other Venue Preparation: Consider after-hours heating or cooling, lighting,
104
+  and security. A small room can get hot or cold, very quickly with the air
105
+  conditioning turned off. Sometimes our security forgets the event and locks
106
+  our doors.
107
+- Reminder Announcements: A lot of OpenStack User Group use [Meetup](http://meetup.com)
108
+  to announce their meeting, since it automatically sends reminders. You can
109
+  pick the tool you prefer to organize your events.
110
+- Afterward: keep the conversations going online after a meeting. In order to
111
+  support those who couldn't make it this time, collect materials such as
112
+  speech scripts, photos, video, and reports and  make them accessible online
113
+  as much as possible, Collecting the material immediately at the event works
114
+  better than chasing speakers afterward. Write a blog post and share the
115
+  materials.
116
+
117
+Example Planning Schedule
118
+-------------------------
119
+This is an example planning schedule from the SFBay OpenStack User Group.
120
+
121
+1. Establish dates and times at least 6 months in advance
122
+2. Schedule speakers, assistants at least a month in advance
123
+3. Schedule tweets and emails to go out 7, 2, 1, and 0 days before the meetup reminding possible attendees of the meetup.  Examples below
124
+  * T-7 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
125
+  * T-2 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
126
+  * T-1 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening tomorrow at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
127
+  * T-0 day 11:30: @[[OpenStack]] #OSSFO hackathon meetup happening today at #Yahoo Sunnyvale, RSVP via ow.ly/g2V3u, webex avail
128
+- Schedule an email to go out to the community mailing list with the same content
129
+  * To: community@lists.openstack.org
130
+  * Subject: [[OpenStack]] SFBay hackathon next Thursday
131
+  * Body: @[[OpenStack]] #OSSFO hackathon meetup happening next Thursday at
132
+  * #Yahoo Sunnyvale, RSVP via http://meetup.com/openstack, webex avail. More updates via @sarob
133
+4. Book your meeting space at least 1 month in advance
134
+5. Notify security about the meetup and so they can provide directions so
135
+   visitors do not get lost
136
+6. Order the food at least 3 days in advance. A good gauge is about 70% of the
137
+   RSVPs actually show up. Better topics get a higher percentage turnout.
138
+7. Prep the room about an hour before the meetup. Check the AV equipment,
139
+  power strips, seats, food, drink, and white boards are ready to go. Setup
140
+  the video camera, so you know where the static viewing area is. Line up
141
+  the projector screen to be in the picture. Lay down a tape box where the
142
+  speaker should stand. Dial into the audio conference line. If you are using
143
+  webex or youtube, check for connection to the remote server.
144
+8. Post Meetup: After the meeting, you can prepare a summary blog post with
145
+   images, links to video, marketing updates for the OpenStack blog.
31 146
 

+ 68
- 0
what-are-user-groups.md View File

@@ -0,0 +1,68 @@
1
+---
2
+title: What are User Groups?
3
+path: what-are-user-groups
4
+menu: What are User Groups?
5
+---
6
+
7
+
8
+What are User Groups?
9
+=============================================
10
+
11
+What are user groups?
12
+---------------------
13
+
14
+In many places, people running clouds or building apps on them get together in
15
+person to discuss OpenStack, share knowledge and experiences (sometimes with
16
+the developers who build OpenStack too!). User Groups are little pockets of
17
+our global community, where you can go to learn and meet people in an informal
18
+setting.
19
+
20
+
21
+What happens at a user group meeting?
22
+-------------------------------------
23
+Every user group is different. Many have a strong social element, so there
24
+might be food and drink. Someone might give a presentation. It's best to
25
+carefully check the agenda so you can make the most of your time.
26
+
27
+How are user groups organised?
28
+------------------------------
29
+Normally a passionate person finds a couple of friends and decides they
30
+would like to make a group, who will be the first organisers. They try to
31
+find other people nearby to join and help schedule the meetings and content.
32
+Over time, more volunteers should emerge to help share the burden. The
33
+organisers are donating their time to the cause, so support them if you can!
34
+You can read more on organising a meetup
35
+[here](https://groups.openstack.org/content/organizer-tips).
36
+
37
+Why are groups important?
38
+-------------------------
39
+Aside from the reasons mentioned above, user groups are essential for the
40
+OpenStack project as they spread awareness and knowledge, recruit developers,
41
+encourage and users to provide feedback and more.
42
+
43
+Will vendors try to sell me things at a user group?
44
+----------------------------------------------------
45
+User groups must be non-commercial, though they may accept sponsorship to
46
+cover costs. For example, in order to justify providing money to book a venue,
47
+a sponsor may be given an opportunity to do a short pitch by the organiser,
48
+but it should not be the main focus of the meeting. You may also see sponsor
49
+logos on the meeting website or on signage, however no-one should be
50
+pressuring you to buy anything at a user group. The OpenStack Foundation
51
+also mandates other restrictions such as not allowing the use of your
52
+registration details for marketing - more can be found at the
53
+[Event Policy](https://www.openstack.org/brand/event-policy/) .
54
+
55
+What is the OpenStack Foundation?
56
+---------------------------------
57
+The OpenStack Foundation is the non-profit, neutral organisation that exists
58
+to protect, empower and promote OpenStack and its community. User groups don't
59
+have a direct relation with the OpenStack Foundation, but since they use the
60
+OpenStack name and logo, the Foundation works to ensure they meet certain
61
+requirements.
62
+
63
+What happens if something goes wrong at a user group?
64
+-----------------------------------------------------
65
+Activities at OpenStack user groups must comply with the [OpenStack Community
66
+Code of Conduct](https://groups.openstack.org/content/openstack-community-code-conduct)
67
+and other policies. If you feel uncomfortable or unsafe, do take action.
68
+There are contact details for Foundation staff in the policy if needed.

Loading…
Cancel
Save