The OpenStack Ambassador program aims to create a framework of community leaders to sustainably expand the reach of OpenStack around the world. It was introduced in August 2013, with this blog post
- 1 Ambassadors
- 2 Role of Ambassadors
- 3 Ambassador Communication
- 4 Selection process
- 5 Frequently Asked Questions
- 6 Administration
Role of Ambassadors
Ambassadors will be recognised on the OpenStack website for their efforts, and provided with support from foundation staff to conduct their duties. They will also get access to a funding program – allowing them to request funds for activities of impact in their region. We’d also expect ambassadors to attend the summits, and the Foundation would likely assist if it wasn’t possible for them to be there using their own methods.
- Act as a liason between multiple user groups, the Foundation, and the general community, for example:
- helping to solicit feedback on OpenStack and aggregate it to the global level
- promoting key messages into the user communities (eg “ask questions on ask.openstack.org!”)
- finding people to help localise content
- helping onboard new users and contributors
- Assist in user group best practice – from nurturing new groups to cementing the quality of existing ones
- Help people find the ‘right people’ to talk to
- Represent the community via speaking and visibility opportunities with the official title
- Report on the activities in their region
- Be a good leader, wranging activity from others and mobilising the global OpenStack community!
The title is designed to recognise those who are already good leaders with a proven track record in the community. With the title, new users, contributors and community members should easily be able to recognize their Ambassador as a go-to resource. While the role provides inherent credibility, it also comes with accountability, meaning decisions and actions made by the Ambassador should benefit the whole community, not just one person or company.
We believe that the Ambassadors will already be active participants in our community. Think about those people who are already working across multiple user groups, submitting OpenStack mini-events to related conferences, helping onboard new users and contributors, arranging hackfests or just generally going above and beyond in the name of making Openstack great.
To that end, we intend to ask that potential ambassadors provide some information about themselves, namely:
- Why are you applying to become an OpenStack Ambassador?
- How have you participated in the OpenStack Community to date?
- What ideas do you have for your community, that you wish you had time or resources to implement?
A small number of ambassadors will then be selected based on a set of criteria:
- Community participation track record
- Geographical location
- Potential impact of selection on community
Should I Apply?
Great leaders know when to be modest, but if you feel like you’re already doing the kind of things listed in the role description, we’d like to recognise your efforts – so do consider applying. Initially we’re being a little more cautious and smaller scale, iterating our way toward a larger more active program – but putting your application in at the beginning will ensure you’re considered later too in the event you’re not selected initially.
How can I Apply?
This is an exciting new program, and we want to get right from the outset. To that end, we want to get some more feedback before starting it. So, to begin with, start thinking about whether you or someone you know is ambassador material – and then let us know whether you think there’s something that should be changed! So, please continue to discuss on the mailing list/comment section, or, if you would feel more comfortable raising your issues in private – email firstname.lastname@example.org Following this period of consultation, we’ll open for selections, aiming to have the first OpenStack Ambassadors bestowed their title in September. While the discussion continues, if you feel ready, you can put in an application at the form here: https://docs.google.com/forms/d/1LF9_1JVcrak5edqYMl1hqqnmDGhjlq7O5ZNn3Csk4ac/viewform
Frequently Asked Questions
When is all this going to happen?
We hope to have our first tranche of ambassadors entitled by September, so we can get the program running before the summit. We want to get this done as soon as manageable, since we expect it to go a long way to solving some problems that exist right now.
How much do ambassadors get paid?
They are paid in love – this is a volunteer position.
How big will the regions be?
Initially: big. We’re starting with a small number of ambassadors so we can learn before scaling up. We also want to avoid situations where there are many ambassadors in one region – hence the selection criteria related to geography.
How does “Ambassador” relate to “User Group Leader”?
OpenStack Ambassador and OpenStack User Group leader are two distinct roles, which can of course be fulfilled by one person, but they have distinct responsibilities. The Ambassador may be involved in running their local meetup group, but they’ll be chatting to the User Group Leaders in their region about how to best help – not taking over!
What will the term length be for ambassadors?
It’s a ‘job for life’. We believe that the kinds of people who would be eligible to be ambassadors will know when to step down gracefully.
How will we manage misuse of the ambassador title?
This question comes up frequently, but we have faith in our community. We’ll be applying selection criteria to weed out any undesirables at the beginning, but then keeping in constant contact with the ambassadors to look for early signs things aren’t going the right way. Community members are also welcome to help us looking out for misuse of the title.
This section contains some boring information about administrative processes to do with the AmbassadorProgram.
Add an Ambassador
To add an ambassador:
- Update https://wiki.openstack.org/wiki/Community/AmbassadorProgram with their information
- Update http://www.openstack.org/community with their information
- Change profile on https://groups.openstack.org/ to have ambassador status
- Update their "home" group to mark them as ambassadors for that group
- Add email to the mailing list
- Send a welcome email to the mailing list
Groups Portal: New Group Request
- New request comes in to the "Groups waiting for approval" queue
- If it's obviously not an OpenStack user group - for example spam, a general group covering IT, etc, reject with a link to what an OpenStack User Group is
- If it is something that looks almost like a user group
- Fix up the title so it conforms with the geographic name requirements - put "pet names" in braces at the end
- If there is missing information, such as an URL, that is easy to find, add it and update the group
- Research the group a little
- If the group is in conflict with an existing group (eg geographic overlap), or has obvious issues (such as advertising), ask Ambassadors to find a solution before approving.
- If the groups is not in obvious conflict with an existing group and has no obvious issues, find an Ambassador to mentor the group and pending no Ambassador objections, approve the request quickly.