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