summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005586.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005586.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005586.html264
1 files changed, 264 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005586.html b/zarb-ml/mageia-dev/2011-June/005586.html
new file mode 100644
index 000000000..2f2c0c312
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005586.html
@@ -0,0 +1,264 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%22Job%20offer%22%20%3A%20mentoring%20program%20coordinator&In-Reply-To=%3C4DF72106.1050702%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005513.html">
+ <LINK REL="Next" HREF="005819.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%22Job%20offer%22%20%3A%20mentoring%20program%20coordinator&In-Reply-To=%3C4DF72106.1050702%40laposte.net%3E"
+ TITLE="[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator">andr55 at laposte.net
+ </A><BR>
+ <I>Tue Jun 14 10:51:18 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005513.html">[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator
+</A></li>
+ <LI>Next message: <A HREF="005819.html">[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5586">[ date ]</a>
+ <a href="thread.html#5586">[ thread ]</a>
+ <a href="subject.html#5586">[ subject ]</a>
+ <a href="author.html#5586">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Samuel Verschelde a &#233;crit :
+&gt;<i>
+</I>&gt;<i> Le lundi 13 juin 2011 00:52:18, andre999 a &#233;crit :
+</I>&gt;&gt;<i> Samuel Verschelde a &#233;crit :
+</I>&gt;&gt;&gt;<i> Hello to everyone,
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> I'm sure there's someone among you who wants to help Mageia but hasn't
+</I>&gt;&gt;&gt;<i> found yet the good way to do it. Today is your lucky day, because
+</I>&gt;&gt;&gt;<i> there's a job that's available and can be really useful and interesting:
+</I>&gt;&gt;&gt;<i> coordinating the packagers mentoring program.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> You know that one key point of success for Mageia is in the ability to
+</I>&gt;&gt;&gt;<i> welcome new packagers. The better we will be at it, the better the
+</I>&gt;&gt;&gt;<i> distro will be. The packagers mentoring program has been created for
+</I>&gt;&gt;&gt;<i> that reason and several packagers have been or are being mentored. But
+</I>&gt;&gt;&gt;<i> we have some difficulty knowing who is being mentored by who and who
+</I>&gt;&gt;&gt;<i> hasn't found a mentor. And we need also to find more mentors and more
+</I>&gt;&gt;&gt;<i> apprentices.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> During a packagers weekly meeting, misc invited us to read the following
+</I>&gt;&gt;&gt;<i> article about mentoring programs in open-source projects:
+</I>&gt;&gt;&gt;<i> <A HREF="http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/">http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Very interesting, especially many of the comments.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> I invite those who haven't read it yet, to read it. I'll quote one of the
+</I>&gt;&gt;&gt;<i> mentoring best practices that were given: &quot;In bigger projects, keeping
+</I>&gt;&gt;&gt;<i> track of who is a mentor, and who is mentoring who, and inviting new
+</I>&gt;&gt;&gt;<i> mentors, and ensuring that no-one falls through the cracks when a mentor
+</I>&gt;&gt;&gt;<i> gets too busy, is a job of itself.&quot;
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> I'm looking for someone who could fill that &quot;job&quot;.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Description of the job:
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> - keep track of:
+</I>&gt;&gt;&gt;<i> -- who's being mentored by who, how well it's going
+</I>&gt;&gt;&gt;<i> -- who needs a mentor and hasn't found one yet (this is one of the most
+</I>&gt;&gt;&gt;<i> important parts: no volunteer must be forgotten, volunteers are too
+</I>&gt;&gt;&gt;<i> precious !)
+</I>&gt;&gt;&gt;<i> -- who can mentor more apprentices (and sometimes convince packagers to
+</I>&gt;&gt;&gt;<i> become mentors or accept one more apprentice)
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> - be available for questions from apprentices or mentors, by mail, and if
+</I>&gt;&gt;&gt;<i> possible, to be present on the IRC channel #mageia-mentoring on freenode
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> - help mentors with gathering &quot;junior tasks&quot; (bugzilla is a never empty
+</I>&gt;&gt;&gt;<i> reserve that can be used for that. Maybe ask the bug triage team to help
+</I>&gt;&gt;&gt;<i> identify such tasks. Maybe a &quot;junior task&quot; keyword in bugzilla would do
+</I>&gt;&gt;&gt;<i> the trick)
+</I>&gt;&gt;&gt;<i> -- small bugs to fix
+</I>&gt;&gt;&gt;<i> -- new small packages to import in the distribution
+</I>&gt;&gt;&gt;<i> -- backports
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> - promote mentoring (empower users into contributers. Working with the
+</I>&gt;&gt;&gt;<i> marketing team would be great I think):
+</I>&gt;&gt;&gt;<i> -- make the mentoring program known (MLs, forums, web, etc.)
+</I>&gt;&gt;&gt;<i> -- look for new apprentices
+</I>&gt;&gt;&gt;<i> -- look for new mentors
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Some useful skills:
+</I>&gt;&gt;&gt;<i> - be autonomous (ie no need to check that you're doing the work)
+</I>&gt;&gt;&gt;<i> - good written english (communication is very important in this job)
+</I>&gt;&gt;&gt;<i> - knowledge about packaging is a plus but not mandatory (the key aspects
+</I>&gt;&gt;&gt;<i> can be taught to you)
+</I>&gt;&gt;&gt;<i> - being or having been a mentor, or having been mentored would be a plus,
+</I>&gt;&gt;&gt;<i> but not mandatory
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> More information about the job:
+</I>&gt;&gt;&gt;<i> - does not require a big amount of work, but real committment to the task
+</I>&gt;&gt;&gt;<i> and regularity
+</I>&gt;&gt;&gt;<i> - remember that you have a coordination role, not an authoritative role.
+</I>&gt;&gt;&gt;<i> The difference in that is that you're not here to give orders but to
+</I>&gt;&gt;&gt;<i> facilitate the mentoring program.
+</I>&gt;&gt;&gt;<i> - you don't have to be alone to do this job if it's too much for one
+</I>&gt;&gt;&gt;<i> person: you can find other helpful people wanting to help you if needed
+</I>&gt;&gt;&gt;<i> and rely on the other teams (but finding them *is* part of your job ;)
+</I>&gt;&gt;&gt;<i> ).
+</I>&gt;&gt;&gt;<i> - this &quot;job offer&quot; concerns everything that revolves around the
+</I>&gt;&gt;&gt;<i> mentoring of new packagers, but if it's successful maybe other teams can
+</I>&gt;&gt;&gt;<i> follow the same approach (i18n, QA, etc... ).
+</I>&gt;&gt;&gt;<i> - depending on your level of confidence, experience and will, you could
+</I>&gt;&gt;&gt;<i> be helped in your work. Maybe someone from the council can supervise and
+</I>&gt;&gt;&gt;<i> help you at least at the beginning; or, if no one steps up, I can help
+</I>&gt;&gt;&gt;<i> you bootstrap and organize your new &quot;job&quot;.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> So, who's in?
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Samuel Verschelde
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> That is an excellent idea, a mentoring program coordinator.
+</I>&gt;&gt;<i> I've had some thoughts along those lines for some time.
+</I>&gt;&gt;<i> I'd be glad to contribute, especially via email and editing the wiki, where
+</I>&gt;&gt;<i> I could almost always respond the same day.
+</I>&gt;&gt;<i> But my time zone availability (generally after 22h utc) puts me at a
+</I>&gt;&gt;<i> disadvantage for irc communications and meetings.
+</I>&gt;&gt;<i> (But as part of a coordinating team, that should work well.)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Maintaining the mentor/apprentice database, as Kharec suggested, is to me a
+</I>&gt;&gt;<i> key part of the role. Information such as mentors available, and their
+</I>&gt;&gt;<i> strengths/focus, usual time zones available, communication modes
+</I>&gt;&gt;<i> preferred, languages spoken, and current apprentices, Would-be apprentices
+</I>&gt;&gt;<i> should have similar information listed.
+</I>&gt;&gt;<i> Not much different from the information currently in variously wiki pages,
+</I>&gt;&gt;<i> but maintained by the coordinator in one location.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> &lt;aside&gt;
+</I>&gt;&gt;<i> One thing that occurred to me is that there is no imperative that mentoring
+</I>&gt;&gt;<i> process happens only in English. If an apprentice is more comfortable in
+</I>&gt;&gt;<i> another language, and they find a mentor speaking that language, why not ?
+</I>&gt;&gt;<i> Sure, it is useful to have basic English knowledge, but it is evident
+</I>&gt;&gt;<i> that many (if not most) contributors speak English as a second language.
+</I>&gt;&gt;<i> &lt;/aside&gt;
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Experience packaging, either as a mentor or apprentice is highly
+</I>&gt;&gt;<i> recommended in my view, at least for the key person. (My experience is as
+</I>&gt;&gt;<i> a apprentice with Shikamaru -- an excellent mentor, btw -- and my time
+</I>&gt;&gt;<i> zone availability is probably why I haven't officially completed the
+</I>&gt;&gt;<i> process.) Also some programming experience could be useful. (I imagine
+</I>&gt;&gt;<i> that most candidates would have that.)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> But also mentoring can apply to other things than packaging. So maybe we
+</I>&gt;&gt;<i> should give a broader scope to the mentoring coordinator job ?
+</I>&gt;&gt;<i> Including bugteam, QA, as well as packaging.
+</I>&gt;&gt;<i> That would make it more useful, as well as more interesting.
+</I>&gt;&gt;<i> (I would be very interested in contributing to something like that.)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So what does everyone think ?
+</I>&gt;<i>
+</I>&gt;<i> Thanks for the input, but there's one point that's still unclear to me : do
+</I>&gt;<i> you candidate for the job ? :p
+</I>&gt;<i>
+</I>&gt;<i> (the timezone question can be a problem, but not necessarily a blocking one)
+</I>&gt;<i>
+</I>&gt;<i> Samuel
+</I>
+Yes :)
+It's an important task, and I think I would do it well.
+With my (albeit somewhat limited) packaging experience and getting to better know the community, I
+have a much better understanding of the whole Mageia development process than I did even a few
+months ago. And how this fits in.
+
+--
+Andr&#233;
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005513.html">[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator
+</A></li>
+ <LI>Next message: <A HREF="005819.html">[Mageia-dev] &quot;Job offer&quot; : mentoring program coordinator
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5586">[ date ]</a>
+ <a href="thread.html#5586">[ thread ]</a>
+ <a href="subject.html#5586">[ subject ]</a>
+ <a href="author.html#5586">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>