[Ambassadors] Ambassador Group Role for 2011 - was [FAmSCo] almost done with current year's budget

Neville A. Cross neville at taygon.com
Sat Feb 12 02:30:16 UTC 2011

On Fri, 2011-02-11 at 11:21 -0800, Jesús Franco wrote:
> IMHO, every Ambassador should be first at all, contributor in another  
> Fedora project.

I fully understand why may be useful for an ambassador to start
somewhere else as fedora contributor and later become ambassador. There
are several reason for that I agree with the statement. What I like to
sugest is not make it a rule. My only reason for saying so, it because
otherwise I wouldn't be here. I am not a programer, I am not a designer,
and I wanted to spread Fedora so I joined Ambassadors. I am not ashamed
of my starts on the project just as a "talk-giver" and event organizer.

It is a difficult balance to keep easy to get onboard of the project and
still keep up quality. I adhere to this as a guideline, but as a rules
is a bit too hard.

I feel that my role as ambassador is to direct people to contribute with
fedora where their talents may be more useful. What sometime is not as
easy, as people some times want to do things that are not their best.
(Let's hope is because of the learning experience and not because of
sturburness). Ambassador role is about undersatnding the project as a
whole, and about soft skills dealing with people.  You may gain some
insight on the project joining one team, but that will be not enough. It
is a ongoing task for every day.

So, let's help people to help us. Let's direct people to different parts
of the project. But please don't discard people that may be useful on
ambassador team just because they haven't been able to engage in other

Linux User # 473217

More information about the ambassadors mailing list