infrastructure team rules
  Home FAQ Contact Sign in
linux.debian.project only
 
Advanced search
POPULAR GROUPS

more...

linux.debian.project Profile…
 Up
infrastructure team rules         


Author: Josip Rodin
Date: Oct 15, 2007 16:30

Hi,

I pondered a bit about that old subthread about infrastructure teams the
other day... what follows is what I was intending to post to debian-vote.
But I'll post it to debian-project first, hoping that people improve it
before we get to the stage where everyone posts GPG-signed messages :)

-----

This originates from this debian-project mailing list discussion
http://lists.debian.org/debian-project/2007/06/msg00020.html

Proposed general resolution - Project infrastructure team procedures

Debian developers acknowledge the following:
* The Debian Project infrastructure is run by people who volunteer their
time and knowledge in a good-faith effort to help the Debian Project.
* Infrastructure...
Show full article (3.98Kb)
26 Comments
Re: infrastructure team rules         


Author: Lucas Nussbaum
Date: Oct 15, 2007 23:50

On 16/10/07 at 01:20 +0200, Josip Rodin wrote:
> Hi,
>
> I pondered a bit about that old subthread about infrastructure teams the
> other day... what follows is what I was intending to post to debian-vote.
> But I'll post it to debian-project first, hoping that people improve it
> before we get to the stage where everyone posts GPG-signed messages :)
>
> -----
>
> This originates from this debian-project mailing list discussion
> http://lists.debian.org/debian-project/2007/06/msg00020.html
>
> Proposed general resolution - Project infrastructure team procedures
>
> Debian developers acknowledge the following:
> * The Debian Project infrastructure is run by people who volunteer their
> time and knowledge in a good-faith effort to help the Debian Project.
> * Infrastructure teams are groups of developers who deal with project
> infrastructure and have access to resources in ways other than ...
Show full article (2.64Kb)
no comments
Re: infrastructure team rules         


Author: Raphael Hertzog
Date: Oct 16, 2007 00:20

On Tue, 16 Oct 2007, Josip Rodin wrote:
> I pondered a bit about that old subthread about infrastructure teams the
> other day... what follows is what I was intending to post to debian-vote.
> But I'll post it to debian-project first, hoping that people improve it
> before we get to the stage where everyone posts GPG-signed messages :)

Good initiative. You might take some inspiration in the "Team guidelines"
that I drafted earlier this year:
http://wiki.debian.org/Teams/Guidelines
> * The practice of existing members of a team finding people to join in
> and help is the original and natural way of changing team membership.

Yeah, although in practice it's a mix of "people reply to help request"
and "people spontaneously volunteer and ask what they can do to help".
Maybe you can make that clearer.
> * Infrastructure teams have to decide to mark old members who don't
> sufficiently contribute to the team effort as latent.
> * Latent team members count for 50%% of an empty seat in the team.
> They can be unmarked as such every four months.
> * Team decisions regarding latent team members have to be communicated to
> the Debian Project Leader or to the developers in general.
Show full article (4.24Kb)
no comments
Re: infrastructure team rules         


Author: Josip Rodin
Date: Oct 16, 2007 00:30

On Tue, Oct 16, 2007 at 06:31:30AM +0200, Lucas Nussbaum wrote:
>> * Infrastructure teams are groups of developers who deal with project
>> infrastructure and have access to resources in ways other than
>> the standard practice of uploading Debian packages.
>
> Which teams do you currently have in mind? That applies to DSA,
> obviously, ftp-master, but also well-functionning teams such as the
> release team?
> But it could also apply to every team that has a unix group, even if
> it's used to maintain a very small part of Debian infrastructure.

Yes. They should all have a mechanism to stop them from calcifying.
>> [...]
>> * Intervention by Debian Project Leaders is not a practical solution
>> to resolve issues with infrastructure teams.
>
> Before acknowledging that, it would be great to know the status of the
> discussions between the DPL and DSA members.
Show full article (2.74Kb)
no comments
Re: infrastructure team rules         


Author: Josip Rodin
Date: Oct 16, 2007 01:00

[will check the wiki page, but I deleted the quote by mistake :)]

On Tue, Oct 16, 2007 at 09:13:38AM +0200, Raphael Hertzog wrote:
>> * Infrastructure teams have to decide to mark old members who don't
>> sufficiently contribute to the team effort as latent.
>> * Latent team members count for 50%% of an empty seat in the team.
>> They can be unmarked as such every four months.
>> * Team decisions regarding latent team members have to be communicated to
>> the Debian Project Leader or to the developers in general.
>
> The concept of "latent" team member is a somewhat strange. I agree
> something like that is needed because one can't be expected to be fully
> invested in a team 100%% of the time. But your mathematics are strange, why
> would a latent member count only for 50%% of a "empty seat" ?

That's simply for later calculation of how much they have to repopulate :)
> I think teams should be free to coopt new members at any time as usual,
> but additionally there would be those nominations rounds so that
> candidates have an occasion to get a decision and a rationale (at least
> they can know what they were doing wrong and can try to improve) instead
> of the usual lack of answer.
Show full article (5.44Kb)
no comments
Re: infrastructure team rules         


Author: Stefano Zacchiroli
Date: Oct 16, 2007 04:40

On Tue, Oct 16, 2007 at 09:28:30AM +0200, Josip Rodin wrote:
>> Debian developers resolve that some teams (pick up at least one
>> amongst DSA, ftpmaster, DAM) are not functionning properly, and
>> empower the DPL to take all necessary actions to restore normal
>> behaviour.
> What will that ad hoc intervention accomplish in the long run?
> Does the history of teams persistently losing activity/members
> teach us nothing?

I don't see Lucas' proposal as ad-hoc.

Once we have resolved something as he propose the DPL will be empowered
to solve the problem with any team in the present and in the future. A
big part of our current problem is that some team do not feel they are
under the authority of the DPL whereas IMO the should be.

Indeed reading the first part of your proposal (btw, thanks for that!) I
was expecting a second part precisely on the lines of Lucas' POV. What I
had in mind is something like: the developer body resolves that whatever
team is under the authority of the DPL.

Cheers.
Show full article (1.51Kb)
no comments
Re: infrastructure team rules         


Author: Josip Rodin
Date: Oct 16, 2007 05:00

On Tue, Oct 16, 2007 at 01:34:15PM +0200, Stefano Zacchiroli wrote:
> Once we have resolved something as he propose the DPL will be empowered
> to solve the problem with any team in the present and in the future.

Sorry, but that won't work. The Constitution already empowers the DPL to do
things that nobody else is explicitly in charge of, yet none of them ever
did anything substantial to e.g. bop DSA to be more active. If we explicate
that ability of theirs, that won't necessarily make them more efficient,
or at least I don't see any proof for that.
> A big part of our current problem is that some team do not feel they are
> under the authority of the DPL whereas IMO the should be.
>
> Indeed reading the first part of your proposal (btw, thanks for that!) I
> was expecting a second part precisely on the lines of Lucas' POV. What I
> had in mind is something like: the developer body resolves that whatever
> team is under the authority of the DPL.

This argument is a red herring, but an apparently successful one.
Well, at least my proposal resolves as the first matter of business
that the DPL decides whether a team is governed by these rules, and
the set of rules is then resolved by the developers.
Show full article (1.68Kb)
no comments
Re: infrastructure team rules         


Author: Josip Rodin
Date: Oct 16, 2007 05:20

On Tue, Oct 16, 2007 at 09:13:38AM +0200, Raphael Hertzog wrote:
> Good initiative. You might take some inspiration in the "Team guidelines"
> that I drafted earlier this year:
> http://wiki.debian.org/Teams/Guidelines

Okay, my proposal was aimed primarily at the process of composition, these
guidelines go further and advise about communication and documentation.
The first matter to consider is - whether these two things are as important
at this point as the composition is, sufficient to be part of general
resolution; and if so, which parts :)

I'm thinking that if we extend beyond composition, the GR will become too
long and intricate, with more possibly contentious issues. But, one general
resolution point could be made about the rest:

* With regard to communication and documentation, infrastructure teams
should try to work under the guidelines laid out in
the Debian Developer's Reference.

The DR sounds like a good place to refer to - wiki.d.o inherently can't be
a stable reference, unless we protect the page :) but even then, devref has
BTS support where issues can be hashed out, whereas a wiki page doesn't
(at this time at least).
Show full article (1.37Kb)
no comments
Re: infrastructure team rules         


Author: Lucas Nussbaum
Date: Oct 16, 2007 05:30

On 16/10/07 at 09:28 +0200, Josip Rodin wrote:
> On Tue, Oct 16, 2007 at 06:31:30AM +0200, Lucas Nussbaum wrote:
>>> * Infrastructure teams are groups of developers who deal with project
>>> infrastructure and have access to resources in ways other than
>>> the standard practice of uploading Debian packages.
>>
>> Which teams do you currently have in mind? That applies to DSA,
>> obviously, ftp-master, but also well-functionning teams such as the
>> release team?
>> But it could also apply to every team that has a unix group, even if
>> it's used to maintain a very small part of Debian infrastructure.
>
> Yes. They should all have a mechanism to stop them from calcifying.

I really don't think that the qa group, the webwml group, the list
admins, etc need such bureaucracy ... According to your definition, your
proposal apply to them too (they have a unix group, and have access to
resources in ways other than the standard practice).
Show full article (4.04Kb)
no comments
Re: infrastructure team rules         


Author: Josip Rodin
Date: Oct 16, 2007 05:50

On Tue, Oct 16, 2007 at 02:29:08PM +0200, Lucas Nussbaum wrote:
>>> Which teams do you currently have in mind? That applies to DSA,
>>> obviously, ftp-master, but also well-functionning teams such as the
>>> release team?
>>> But it could also apply to every team that has a unix group, even if
>>> it's used to maintain a very small part of Debian infrastructure.
>>
>> Yes. They should all have a mechanism to stop them from calcifying.
>
> I really don't think that the qa group, the webwml group, the list
> admins, etc need such bureaucracy ... According to your definition, your
> proposal apply to them too (they have a unix group, and have access to
> resources in ways other than the standard practice).

Well, let's put it this way - do you think that the hordes of people anxious
to see changes in the design of the web site think that we should keep the
webwml group as it is? :)
Show full article (3.57Kb)
no comments
1 2 3