Browse Source

Merge "Add Official User Group Process as static page"

changes/95/170095/1
Jenkins 4 years ago
parent
commit
72be07f5b5
1 changed files with 89 additions and 0 deletions
  1. 89
    0
      official-group-process.md

+ 89
- 0
official-group-process.md View File

@@ -0,0 +1,89 @@
1
+---
2
+title: Official User Group Process
3
+path: official-group-process
4
+menu: Official User Group Process
5
+---
6
+
7
+
8
+Official User Group Process
9
+=============================================
10
+
11
+At OpenStack, we have some of the most passionate user groups in the world.
12
+We want all of our groups to be sustainable, high quality and friendly for
13
+ everyone. This process provides a framework we can use to mentor new groups
14
+through their growth period, and work with established ones to get them through
15
+any remaining niceties to reach the top.
16
+
17
+Steps to Success
18
+----------------
19
+
20
+We help User Groups get through the following steps before noting them as
21
+Official User Groups, and issuing them with an OpenStack User Group logo:
22
+
23
+1.    Agreed to Social Media and Event Policy (TEST: tickbox in portal)
24
+
25
+2.    Complete group contact information entered in portal (TEST: portal completeness % - need name, organiser email>1, URL>1)
26
+
27
+3.    Group organised and coordinated, multiple people from diverse employment involved in organisation, impartial (TEST: coordinators listed in portal, Community Managers + ambassadors to validate organisation, coordination and diversity)
28
+
29
+4.    Communications channels active and following policy (TEST: channels listed in portal, Community Managers + ambassadors to validate activity and policy)
30
+
31
+5.    Meeting regularly, with appropriate content (TEST: Community Managers + Ambassadors to validate)
32
+
33
+6.    An ambassador signed up to mentor the organising group (mainly for new/growing groups)
34
+
35
+Interpreting the criteria
36
+-------------------------
37
+
38
+The aim of this process is to encourage all user groups to strive to be the
39
+ best they can be. In doing this, it is important to note that each group is
40
+ different, and this is one of the main reasons for the relative "looseness"
41
+ of certain criteria - particularly #3,4,5. Consider the 'regularity'
42
+ requirement from criteria 5. One could consider setting a target of
43
+ "once per month". However, in some cultures, the principle of organising
44
+ small meetups amoungst strangers is unusual, and in preference a very
45
+ structured event needs to be put in place in order to make people feel
46
+ comfortable attending. Similarly, with criteria 3, regarding the organisation
47
+ of the group, there is no fixed number of people involved that would be
48
+appropriate to assest all groups against.
49
+
50
+Overall, the aim of the process is to be nurturing. It's a lot less about
51
+ testing, and more about helping groups achieving their goals. Each step is
52
+ laced with education, based on the Ambassadors' extensive experience in working
53
+ with the community both OpenStack and the general population. We're here to
54
+ help! We expect to innovate on the criteria over time, based on practical
55
+ experience and feedback from the community.
56
+
57
+
58
+
59
+
60
+Going Above and Beyond
61
+----------------------
62
+Several groups go beyond the scope of themselves to talk OpenStack to the
63
+ world. They organise meetups and presentations and tech conferences, plan
64
+ conferences themselves, kick-off bug days, installfests, hackfests and many
65
+ other awesome activities.
66
+
67
+Each year, we want to look at these groups and find some way to recognise them
68
+ for being stand-out examples of community activity.
69
+
70
+Handling Change
71
+---------------
72
+In initial ‘approval’, we attempt to assist in ensuring that user groups are
73
+ sustainable and ongoing activities. However, in the event that a group starts
74
+ to decline and despite our assistance we’re unable to keep it going, its official
75
+ status may be revoked and re-granted at a later time.
76
+
77
+Handling New User Groups
78
+------------------------
79
+We need to  balance new groups getting recognition needed to get members,
80
+ against the need to recognise the quality of those that have become
81
+ "sustainable". To do this, we will provide a modified version of the group
82
+ logo to new groups - saving the "official" logo for those who have
83
+ completed the process. We want to enable new groups to have the best
84
+ potential to attract attendees, while recognising that they are still
85
+ in the process of improving.
86
+
87
+Once it is operational, we expect the process to begin by filling out a form
88
+ with details on the user group portal.
89
+

Loading…
Cancel
Save