Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <0117C5C5-2ACE-46CF-92FC-7D86C01E850F@gmail.com>
References: 
 <CAK2iWdTWvhDAWyZY7H7aLg8t3N0KGAT9==MFZmvEAPh-MUvhfQ@mail.gmail.com>
	<0117C5C5-2ACE-46CF-92FC-7D86C01E850F@gmail.com>
Date: Thu, 30 Jul 2015 09:28:18 +0200
Message-ID: 
 <CAK2iWdSo3HD-cNQcdbpxLbSg5oC0tO83CiT-9JVm0XunZrz99w@mail.gmail.com>
Subject: Re: Criteria for becoming committer in Corinthia.
From: jan i <jani@apache.org>
To: "dev@corinthia.incubator.apache.org" <dev@corinthia.incubator.apache.org>
Content-Type: multipart/alternative; boundary=f46d044287d8ad1100051c12a5c8

--f46d044287d8ad1100051c12a5c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tuesday, July 28, 2015, Louis Su=C3=A1rez-Potts <luispo@gmail.com> wrote=
:

>
> > On 28 Jul 15, at 10:24, jan i <jani@apache.org <javascript:;>> wrote:
> >
> > Hi.
> >
> > As was obvious from other discussions (in private), we need to agree on
> > what are the "rules"
> > for being accepted as a committer. It is also obvious that there are ro=
om
> > for diversity in how
> > we apply the rules.
>
> Note: first, I like your framework and like, too, the flexibility
> implicit. I also dislike rules that bind actions into rituals even when t=
he
> originating context has faded. I don=E2=80=99t think your suggestions do.
>
> However=E2=80=A6.
> mild rant/
>
> Do we need rules? I=E2=80=99d think that in a small project, "rules" are =
better
> understood as "conventions," or even "agreements." The difference is simp=
ly
> that a step toward the codification of practice in the form of scripted
> rules often=E2=80=94but not inevitably=E2=80=94doesn=E2=80=99t really add=
 to the working of the
> project. Unless I=E2=80=99m missing something here? I can see that when C=
orinthia
> has more people and=E2=80=94one can only hope=E2=80=94diverging opinions =
and the
> wherewithal to back them up=E2=80=94then bureaucratic and transparent sys=
tems will
> be useful, as these are designed to minimise arbitrariness. But right now=
?
> Of course, as Dennis enthusiastically +1=E2=80=99d, no doubt I=E2=80=99m =
missing something
> here, and it really is the case that Corinthia needs rules now, as oppose=
d
> to, well, common sense modulo open source collaboration subjunctive Apach=
e.
>
> /end mild rant
>
> All that said, I find nothing objectionable in the clear description you
> offer=E2=80=94thanks.

it is a good suggestion, let us talk about "conventions".

Maybe we should also add a convention about what happens if a single PPMC
do not want
to work towards consensus (of course after ample time to discuss).

rgds
jan i

>
> Louis
>
>
> >
> > For me life is very simple, we are a small project, and should use any
> > chance to grow. This
> > means, I believe we should look at:
> >
> > 1) Candidate has been active on dev@ and shown interest for the project
> > 2) Candidate has submitted patches (not necessarily through dev@)
> > 3) Candidate has otherwise done work to help corinthia.
> >
> > The proposer must make clear which of the 3 the candidate fulfills (1 i=
s
> > enough), in
> > case of 3) the proposer must make it clear to the others what work was
> done
> > and
> > what the benefit will be for the project.
> >
> > If there is general consensus after a discussion, that the candidate is
> > beneficial for the project,
> > we run a vote (needed formally, at least until we become TLP). The vote
> > should be a formality,
> > but in case someone votes -1, the following should happen
> >
> > 1) The reasons for the -1 must be discussed, and may cause others to
> change
> > their
> >    opinion.
> >
> > We need to think about, how to handle a -1 from a person that either
> give a
> > non serious reason,
> > or did not participate in the discussion.
> >
> > Please accept this for what it is, a suggestion from me, I hope for and
> > expect changes.
> >
> > rgds
> > jan i.
>
>

--=20
Sent from My iPad, sorry for any misspellings.

--f46d044287d8ad1100051c12a5c8--