Content-Type: text/plain;
	charset=utf-8
Precedence: list
Mime-Version: 1.0 (1.0)
Subject: Re: [alpine-devel] [PATCH 2/2] Rework the base team description
From: Ted Trask <ttrask01@yahoo.com>
In-Reply-To: <20190409050210.20217-3-sir@cmpwn.com>
Date: Tue, 9 Apr 2019 07:44:17 -0400
Cc: alpine-devel@lists.alpinelinux.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2137E1D-EF43-4109-9015-17199BBFC2D8@yahoo.com>
References: <20190409050210.20217-1-sir@cmpwn.com> <20190409050210.20217-3-sir@cmpwn.com>
To: Drew DeVault <sir@cmpwn.com>

Any scheme that would result in Natanael being removed from the base team af=
ter three years would not get my vote. As far as I am concerned, ncopa shoul=
d be Alpine Linux=E2=80=99s Benevolent Dictator For Life. Completely serious=
.

Ted

> On Apr 9, 2019, at 1:02 AM, Drew DeVault <sir@cmpwn.com> wrote:
>=20
> It's important to firmly establish the authority of the base team. The
> guiding principles to which the base team holds itself are out-of-scope
> for this document and better served elsewhere.
> ---
> modules/Teams/pages/index.adoc | 28 ++++++++++++----------------
> 1 file changed, 12 insertions(+), 16 deletions(-)
>=20
> diff --git a/modules/Teams/pages/index.adoc b/modules/Teams/pages/index.ad=
oc
> index 9560dc3..f3cfe1d 100644
> --- a/modules/Teams/pages/index.adoc
> +++ b/modules/Teams/pages/index.adoc
> @@ -26,13 +26,24 @@ There is no distinction between technical and non-tech=
nical team members. Both a
>=20
> =3D=3D Team Structure
>=20
> +=3D=3D The Base team
> +
> +The Base team has ownership over Alpine Linux and is the last authority i=
n any decision-making.
> +For day-to-day operations, additional teams are established at the pleasu=
re of the base team and given the authority necessary to conduct themselves.=

> +
> +The Base team consists of 3 elected members, guaranteeing a quorum.
> +Members of this team serve 3 year terms, staggered such that one member s=
teps down per year.
> +Each year, an election is held through a project-wide {votelink}[Vote].
> +Members of the Base team cannot serve consecutive terms, but may be re-el=
ected after a one year break.
> +
> =3D=3D=3D Internal Organization
> Teams organize themselves internally however they want.
> However, all teams must have at least 1 admin, and at most 3.
> This document does contain multiple recommendations, which, if followed, w=
ill make external relations easier.
> -Further, team administrators must follow non-team-local expectations.
> +Further, team administrators must follow the policies of other teams when=
 working in their domain.
>=20
> =3D=3D=3D Creating a New Team
> +The base team needn't be involved in establishing every team - the projec=
t as a whole is permitted to self-govern in this respect.
> An existing team member within the project may propose creating a new team=
.
> In that scenario, the process will be the same as in <<_becoming_a_team_ad=
ministrator>>.
> If the vote passes, the new team is formed, with the sponsor member as the=
 only administrator.
> @@ -42,21 +53,6 @@ A team is dissolved if it has no more members.
> If a team has no more administrators, one must be nominated, as in <<_beco=
ming_a_team_administrator>>.
> If the vote does not pass, the team is dissolved as well.
>=20
> -=3D=3D The Base Team
> -The Base team is purely an administrative one.
> -It is also the only team that shall not have admins, and has a static num=
ber of members.
> -The Base team must always have exactly 3 members, to guarantee quorum.
> -The Base team technically owns Alpine.
> -Alpine's policies apply to them, but they have the power to bypass them i=
n case of extreme need.
> -
> -It is expected that the Base team does not do anything unless prompted.
> -Violation of this without there being a strong need is effectively a viol=
ation of trust of the entire rest of the project.
> -Similarly, the Base team is expected to trust team admins and members to d=
o the correct thing on their own.
> -
> -Base team members are elected through a project-wide {votelink}[Vote].
> -A term is 3 years long, and the terms are staggered (each year, a new Bas=
e team member must be elected).
> -Term cycling is allowed - you cannot replace yourself, but you can replac=
e the next person to rotate out.
> -
> =3D=3D Membership
>=20
> =3D=3D=3D Being a Member
> --=20
> 2.21.0
>=20
>=20
>=20
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>=20



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---