Re: infrastructure team procedures (third edit)
Kevin Mark <kevin.mark@verizon.net> writes:
> On Tue, Oct 23, 2007 at 11:10:52AM +0200, Josip Rodin wrote:
>> Hi,
>>
>> Take three, minor copyedit, plus the rule explicitly handling all-latent
>> teams.
>
> Thanks for the work on this effort!
>
>
> A.
>> * Infrastructure teams have an ongoing responsibility to maintain a level
>> of service that is generally acceptable to the developer body.
> B.
>> * Existing team members who don't sufficiently contribute to the team
>> effort have to be marked by the rest of the team as latent.
>
> WRT to point B, what if the team members dont/wont mark someone as
> latent but the developer body considers them latent? You say the team
> members are the only people to do this but WRT point A, the developer
> body should expect a certain level of functioning. So should there be an
> option for some non-team member (some DDs, DPL, all DDs) to mark some
> team member as latent?
Personally I think DPL would be the best person to do that. He could
be asked by us (DDs) to do that if needed.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Reply to: