On Tue, 2013-07-09 at 12:49 +0200, Christoph Wickert wrote:
I totally agree, there are a lot of good reasons. Let me summarize
add a few new ones:
* We should share the workload.
* We should not have a single point of failure.
* The mentors do all the work of the sponsoring process, in
they should be rewarded with more recognition and
* Sponsoring somebody and closing his ticket is just a few
No big deal for a mentor, but it can become a lot of work for
* As the mentors are filing the tickets, they should also close
* The process would be consistent with all the other groups
sponsors == mentors.
+1 on this. Sponsors = mentors makes sense. It's how the package
maintainers function, and it works pretty well IMO.
Since we're talking about the mentors programme: Is it possible to get
prospective ambassadors to interact more with the community? At the
moment, they're sort of reliant on the mentors as their sole point of
contacts in the community. They aren't on the ambassadors list yet, so
they don't interact with the current ambassadors. If they do interact
with other teams on other mailing lists, it isn't clear if they're
candidates for the ambassadors programme, since they don't generally
mention this for whatever reason.
I'd like to think that I'm quite active with APAC ambassadors, but I'm
not aware of prospective ambassadors. I can't reach out to them since I
don't know them. If I knew who they were, I'd like to get in touch with
them and invite them to our weekly meetings at least, so they get to
know other ambassadors from the region. (If they come to the meetings
for starters, they'll learn how events are handled, how trac tickets are
handled, what the current status of our region is, how IRC meetings are
held.) Quite a few things they can learn by keeping in contact with the
community. As a comparison, as package maintainers, we do go ahead and
review stuff unofficially for folks waiting sponsorship. Sure, the
package sponsors make the final decision, but the entire package
maintainer body is free to help these candidates via unofficial reviews
and other channels. We give them pointers, wiki links, tips and tricks.
Such a channel would be pretty beneficial I think.
I do have a suggestion that I'll put forward here: use the fedora-join
channels for prospective ambassadors. The SIG is set up for anyone who
wants to join Fedora, to help them with getting started. I think the
candidates for the ambassador teams should maybe required to introduce
themselves in the fedora-join ML (with maybe a "[ambassador candidate]"
subject line?). Since we'd like ambassadors to also join other teams as
a way to learn about Fedora, they can ask their questions and get help
from existing community members at fedora-join. Since there isn't an IRC
channel where prospective ambassadors can communicate with each other
yet, I suggest the fedora-join IRC channel be used for this purpose too.
The gist is that I'd like prospective candidates to communicate more
with the entire community, not just their mentors. Let the mentors be
official sponsors, let the entire community work with candidates, get to
know them, learn with/from them and most importantly, teach them.
I'd think this would help mentors judge them better too, since they'll
be able to review how well these candidates can get along with the
community, the other teams and just everyone in general.
Join Fedora! Come talk to us!