Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pylucene-dev@lucene.apache.org
From: Andi Vajda <vajda@apache.org>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Thu, 12 Jan 2017 08:37:45 -0800
Subject: Re: Installing PyLucene
Message-Id: <ED74F864-839D-446B-A3F2-0B73775B5A95@apache.org>
References: <CABEbM3-721M64eR_Uiaw3H=V+9EsetG4P+gWLxaKtEB2B7gV1g@mail.gmail.com> <EB59FA6F-A0EC-41F2-A7B4-CEFDF7F1DE49@apache.org> <CABEbM38RbPr4xnh8R9jk+G5C4K9ez=U4DFbFMdSgE6jOwt0XeQ@mail.gmail.com> <BA92E76A-4E34-41F4-B847-9E6B8C39C7CB@apache.org> <CABEbM39s=39y_QEAcVYt9j_GTgXcJkedOhwDjQ+oWXW6Vc+KNA@mail.gmail.com> <98964B54-E4FE-4392-89D3-0D736A99346A@orbiteam.de> <6B53D03F-4132-4E6F-B53E-7D0FAE534898@apache.org> <4ECFFB97-6F2A-4050-8633-79682F29E2F7@orbiteam.de> <263B8000-CF4E-4EAE-9A3E-57BE4014E675@cominvent.com> <965977D4-0957-4B98-81E1-0FC64C92E4C3@orbiteam.de> <E4DE9D35-430E-458A-9707-1641F9DD96FB@cominvent.com>
In-Reply-To: <E4DE9D35-430E-458A-9707-1641F9DD96FB@cominvent.com>
To: pylucene-dev@lucene.apache.org
archived-at: Thu, 12 Jan 2017 16:37:58 -0000


> On Jan 12, 2017, at 03:47, Jan H=C3=B8ydahl <jan.asf@cominvent.com> wrote:=

>=20
>=20
>>> The (sub)project will survive only to the extent that its current users i=
nvest in it.
>> so is this different to how the main (Java)Lucene project works? just cur=
ious =E2=80=A6
>=20
> This is the case for all ASF projects and sub projects. If a project is un=
able to produce
> new releases, usually due to too few developers, or loss of interest, or l=
ack of users,
> the project will end up in the Attic. For a TLP it would be the Board inte=
rvening, while
> for sub projects I believe it is the TLPs responsibility to make sure thin=
gs are healthy.
>=20
>>> For an ASF Open Source Project, the only thing that is required to get g=
oing is user/developer
>>> involvement and teamwork. While Andi started the project due to needs at=
 the time, and became
>>> a committer, he is no longer an active user, so perhaps time has come fo=
r other users to step ut and take
>>> responsibility.
>>>=20
>> That=E2=80=99s first time I hear this (bad) news. So if Andi is no longer=
 an active user - who is the maintainer of PyLucene/JCC?
>=20
> I may have misunderstood myself, but it is quite normal for a commiter=E2=80=
=99s availability to vary over the years,
> and for that reason it would be a big benefit for PyLucene to have at leas=
t two other active devs voted in
> as committers. As I understand it, PyLucene does not require much effort t=
o keep up to date, except when
> there are major changes such as Py3 or porting tests etc.
>=20
> I=E2=80=99m not a user myself, so I=E2=80=99m a bit on the sideline here, b=
eing on the PMC.
>=20
>> We developed and provided the patch (which already took some time) for re=
view and further adaption and really hope now for other users to step in. Th=
is is our current position for several reasons an after internal discussions=
 which I cannot disclose here. Sorry. On the other hand, if we=E2=80=99d be t=
he only user(s) interested/willing to push Python3 support (and Pylucene/JCC=
 as a whole) then this project could not survive anyway I fear.
>=20
> Absolutely, you have done =E2=80=9Cyour share=E2=80=9D and more, and that i=
s what such a project needs, and right
> now PyLucene needs more than one guy who can jump in and make Py3 happen.
> I guess what I was trying to get across is that if Andi will forever be th=
e one guy everyone depend on
> to get the smallest contribution landed in the codebase, it will not be su=
stainable going forward, and
> probably not ideal for Andi nor the other users.=20
>=20
> So what would it take to bring one other developer up to a =E2=80=9Cpro" l=
evel, and are there anyone who have such a desire?

Just as on the Lucene project: repeated sizable contributions, an understand=
ing on how projects function in the Apache community, a commitment to work w=
ithin it and a successful committership vote.

If someone were to donate time to make the JCC 3 patch work with trunk and s=
ubmitted that and showed interest in the project in general, over time, not j=
ust doing a one time code drop, they'd be well qualified to become a committ=
er.

Andi..

>=20
> --
> Jan H=C3=B8ydahl, search solution architect
> Cominvent AS - www.cominvent.com