----- Original Message -----
From: "Karsten 'quaid' Wade"
<kwade(a)redhat.com>
To: "Kiril Nesenko" <kiril(a)redhat.com>
Cc: infra(a)ovirt.org
Sent: Tuesday, May 7, 2013 9:34:25 PM
Subject: Re: Joining Infra team
On 05/07/2013 04:36 AM, Kiril Nesenko wrote:
> We need to update this page -
>
http://www.ovirt.org/Infrastructure_team_administrators
> 1. rmiddle - is not active anymore
We don't have any current policy about inactivating members. Did Robert
send out email saying he was no longer active, remove him as a
maintainer, etc.?
This page doesn't mention anything about inactivity:
http://www.ovirt.org/Becoming_a_maintainer
IIUC, the above page talks about pkgs maintainers and not infra.
I think we should look at
http://www.ovirt.org/Becoming_an_Infrastructure_team_member
It may simply be up to us to decide if we want a policy around
inactivity. It seems to make sense that Infrastructure would be more
strict around this - unlike code contribution under git, root access to
servers can be destructive if an inactive Infra member has their key
compromised, etc.
We should have such policy for sure.
> 2. oschreib - is not maintaining infra
He was at one point, probably when we formed the Infra group. As above,
we don't have any policy for this.
If we're worried about proliferation of sshkeys with sudo access and
less active Infra members, perhaps we can control specifically who has
access to what rather than "everyone, everything." If someone goes
inactive we can remove their sshkey access, but leave the rest (user ~/,
voting privileges, etc.)
+1
I recall asking Carl Trieloff about this when he and JimJag were
drafting the initial governance for oVirt. I was worried that a Board
and maintainers that grew without much attrition would be unwieldy. They
reassured me it worked out fine - there is no reason to retire people,
if they are not active then they just stop debating and voting, but they
can always come back as per the merit that got them maintainership in
the first place. I haven't seen so far a reason to doubt their reasoning.
The purpose of maintainer is to be active as much as possible and to be involved in most
infra tasks/changes/designs.
Maintainer needs to attend meetings in a weekly basis, etc...
So if the person who was a maintainer is inactive anymore, so we should change his status
- to apprentice(for example) etc...
But as you mentioned, we need a policy for that.
[Adding Carl]
> 3. Need to add obasan as apprentice.
So far it appears that new apprentices are added by suggesting of an
existing maintainer. Perhaps we want to make that a more formal
sponsorship arrangement? Each new apprentice needs a sponsor to help get
them started, etc.
That's how it should work ! +1
Cheers - Karsten
> Ohad, please post your ssh pub key.
>
> - Kiril
>
> ----- Original Message -----
>> From: "Karsten 'quaid' Wade" <kwade(a)redhat.com>
>> To: infra(a)ovirt.org
>> Sent: Tuesday, May 7, 2013 12:07:43 AM
>> Subject: Re: Joining Infra team
>>
>> On 05/06/2013 01:26 PM, Dave Neary wrote:
>>> Hi all,
>>>
>>> I updated the "Joining the infra team" wiki page earlier todday
with my
>>> ubnderstanding of what was discussed and agreed several months ago.
>>> Please have a look and review it (and edit it in place), as it's
>>> entirely possible I've forgotten important things there.
>>>
http://www.ovirt.org/Becoming_an_Infrastructure_team_member
>>
>> Great, thanks. I just threw in some changes and additions, let me know
>> what you think. Mainly I wanted to give more stuff to do as an apprentice.
>>
>> One thing that isn't addressed is the final step, which I briefly
>> touched upon in my update. How do we want to handle proposing that
>> apprentices move to maintainership? Just when it occurs to us? On a
>> quarterly basis? When someone asks for the switch and it's obviously
>> time to do it?
>>
>> In that vein, how do I propose that Alexander Rydekull and Dave Neary be
>> pulled from apprentice to maintainer? Presuming they also feel ready, etc.
>>
>> Moran, are you still active and interested? I've lost track of who on
>> the team from Red Hat Engineering is working on Infrastucture bits
>> quietly ...
>>
>> - Karsten
>> --
>> Karsten 'quaid' Wade
>>
http://TheOpenSourceWay.org .^\
http://community.redhat.com
>> @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
>>
>>
>> _______________________________________________
>> Infra mailing list
>> Infra(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/infra
>>
--
Karsten 'quaid' Wade
http://TheOpenSourceWay.org .^\
http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra