Open Stack

On 20/11/13 15:48, Marcelo Dieder wrote:
> Cool Tom,
>
> I have some questions and suggestions:
>
> Do you know when we can use the alias ambassador @ OpenStack ...?

Once ambassadors agree that's what they want :D

> At the AmbassadorProgram Wiki page, we could put the contacts (email) in
> each ambassador and his location for those people who are looking for
> some reference in your region?

I've at least added everyone's Twitter/Weibo - holding off on email as 
this is not preferred for some people, and there's talk of the alias.

> Recently we did a local survey in our group and we had some interesting
> information about Openstack. Where would be the best place to disclose
> this information, and information such as the number of users, number of
> events held, and other? We could create a new page in the wiki for that?

Yes, that sounds like a good idea - can you make a slot for it?

> Regards,
> Marcelo Dieder
>
>
> Em 18-11-2013 22:16, Tom Fifield escreveu:
>> Hi Ambassadors (and interested friends),
>>
>> It's time to continue our discussions of yore on the mailing list, as
>> promised.
>>
>> Attached is Colin's brainstorming diagram, and below is the text
>> mentioned that "Tom has".
>>
>> One of the first things we need to work out is how we're going to
>> manage comms. Suggestions so far have been:
>> * an ambassador at ...openstack... alias that goes to every ambassador
>> ** This could be implemented using a new mailing list, or perhaps by
>> making a queue on the existing support ticket system
>>
>> * regional aliases (ambassador-{apac, eu, us}@...openstack...), that
>> ambassadors in those regions can use in preference to their personal
>> email address when listing on websites, and share the load between
>> multiple ambassadors
>>
>> * ...
>>
>>
>>
>> Regards,
>>
>>
>> Tom
>>
>>
>> Problems:
>> * The lack of a defined communications structure results in a lack of
>> information coming from the communities – be it feedback from users,
>> requests for assistance or content, promotion of local deployments and
>> activities, adoption rates etc
>>
>> * User Group leaders are not supported to promote the aims of the
>> foundation and OpenStack
>>
>> * Many User Groups are at low levels of maturity, which can result in
>> a poor experience for attendees
>>
>> * There is only a small facility for community leaders to participate
>> with their global counterparts
>>
>>
>> Objectives:
>> 1. Creation of structured communication between the Foundation, global
>> OpenStack community and the members and associates of user groups
>> worldwide, providing insight into regional activity while spreading
>> key messages
>>
>> 2. Increased amount of contributors to activities related to
>> localisation, such as translation
>>
>> 3. Increased quality of user groups
>>
>> 4. Increased accessibility of participation in governance activities
>>
>> 5. A gained understanding of user group funding needs, with increased
>> ability to provision funds where most impact is seen
>>
>> 6. Increased adoption of OpenStack, and strengthening of the OpenStack
>> brand
>>
>>
>> _______________________________________________
>> Community mailing list
>> Community at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>
>
>
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>