I agree with Neville here, and for the same reasons. I, too, am not (much of) a programmer -- but I'm working on it -- and my skills around media, as in "news media," make being an Ambassador (and working in Marketing, which I don't do enough of, I confess) the best fit for me. And I think it's a good practice for Ambassadors and Mentors -- especially Mentors -- to guide those who may have a special talent or interest to match the Ambassador with the department in Fedora that best suits him or her.<div>
<br></div><div>One thing that hasn't been discussed -- or I missed it -- is that many people who want to participate in Fedora and don' t know where to start usually start in Ambassadors and make their way to QA or other departments on the programming/engineering side because they do have the skill set. While we end up "losing" them in Ambassadors, they usually find a home in some other part of Fedora, and that's a win for us.</div>
<div><br></div><div>Larry Cafiero<br><br><div class="gmail_quote">On Fri, Feb 11, 2011 at 6:30 PM, Neville A. Cross <span dir="ltr"><<a href="mailto:neville@taygon.com">neville@taygon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Fri, 2011-02-11 at 11:21 -0800, Jesús Franco wrote:<br>
<snip><br>
<div class="im">> IMHO, every Ambassador should be first at all, contributor in another<br>
> Fedora project.<br>
><br>
</div><snip><br>
<br>
I fully understand why may be useful for an ambassador to start<br>
somewhere else as fedora contributor and later become ambassador. There<br>
are several reason for that I agree with the statement. What I like to<br>
sugest is not make it a rule. My only reason for saying so, it because<br>
otherwise I wouldn't be here. I am not a programer, I am not a designer,<br>
and I wanted to spread Fedora so I joined Ambassadors. I am not ashamed<br>
of my starts on the project just as a "talk-giver" and event organizer.<br>
<br>
It is a difficult balance to keep easy to get onboard of the project and<br>
still keep up quality. I adhere to this as a guideline, but as a rules<br>
is a bit too hard.<br>
<br>
I feel that my role as ambassador is to direct people to contribute with<br>
fedora where their talents may be more useful. What sometime is not as<br>
easy, as people some times want to do things that are not their best.<br>
(Let's hope is because of the learning experience and not because of<br>
sturburness). Ambassador role is about undersatnding the project as a<br>
whole, and about soft skills dealing with people. You may gain some<br>
insight on the project joining one team, but that will be not enough. It<br>
is a ongoing task for every day.<br>
<br>
So, let's help people to help us. Let's direct people to different parts<br>
of the project. But please don't discard people that may be useful on<br>
ambassador team just because they haven't been able to engage in other<br>
tasks.<br>
<font color="#888888"><br>
<br>
<br>
<br>
--<br>
Neville<br>
<a href="https://fedoraproject.org/wiki/User:Yn1v" target="_blank">https://fedoraproject.org/wiki/User:Yn1v</a><br>
Linux User # 473217<br>
</font><div><div></div><div class="h5"><br>
--<br>
ambassadors mailing list<br>
<a href="mailto:ambassadors@lists.fedoraproject.org">ambassadors@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/ambassadors" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/ambassadors</a></div></div></blockquote></div><br></div>