From: "Karsten 'quaid' Wade"
<kwade(a)redhat.com>
To: "infra" <infra(a)ovirt.org>
Sent: Tuesday, July 17, 2012 4:57:22 AM
Subject: Re: Maintainers list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/16/2012 12:27 PM, Eyal Edri wrote:
>
>> Can you elaborate on the meaning and real time commitment of
>> being an infra maintainer?
About meaning:
*
http://www.ovirt.org/governance/becoming-a-maintainer/
* The Infra team has a growing pool of resources that maintainers get
to use to learn new skills and hone existing skills.
* If you want to learn professional-level sysadmin practices, and
possibly mentor others in the practices you are familiar or expert
in,
you can do this on the Infra team in casual through mission-critical
rolls that don't have the stress associated with $dayjob.
* If you care about how oVirt infrastructure is built and maintained,
being a maintainer gives you full voting rights and the keys to do
things that matter to you.
* Finally, you might want to influence the overall direction of oVirt
from a seat on the Board. That requires being active in contributing
to more than one area of the project, and Infra could be one of them.
About time commitment, ultimately, time will tell. Also, if we're
good
at our jobs, we invest time up front to save time in the future.
Based
on my experience and guesses, I'd say:
* 1 hour a week for the regular meeting
* 30+ to 90+ minutes a week to read and respond to email
* 0+ hours per week to tend to whatever maintenance you have
volunteered for.
* 0+ hours per week to work on new Infra projects/efforts
** Actual projects may take from 2 to 16 hours for an individual
effort; if it's more than that, we should be looking at splitting up
the work or simplifying the project.
* 1+ hour per month to mentor new and existing Infra members
I wouldn't expect every person to have a fixed schedule of activities
beyond the meetings - some of you will want that, some won't.
Still, being a maintainer means doing things. Helping with planned
and
unplanned service outages, upgrades, new services, mentoring, etc. We
don't want to burn people out, but we do expect people to be doing
things over the course of time.
instance and its slaves:
- update master version + plugins from time to time
- handle new job requests
- fix infra errors that arise from time to time
- offer new ideas and upgrades to the Jenkins infra.
though, I'd love to see more people involved with Jenkins maintenance,
as there is a lot of infra and support work to be done there.
Eyal Edri.
- - Karsten
- --
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org .^\
http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iD8DBQFQBMaC2ZIOBq0ODEERAsuQAKCYZdNkDO/tLf6aBq5fYOqqV0X2oACfaIUo
EYwxT9DHAZWdFSDLZ1jG8Mc=
=PMPC
-----END PGP SIGNATURE-----
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra