Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pylucene-dev@lucene.apache.org
From: =?utf-8?Q?Jan_H=C3=B8ydahl?= <jan.asf@cominvent.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_B0AAD1B1-3420-4CCA-A24F-387E14A1807F"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: Installing PyLucene
Date: Fri, 6 Jan 2017 12:32:47 +0100
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>
To: pylucene-dev@lucene.apache.org
In-Reply-To: <4ECFFB97-6F2A-4050-8633-79682F29E2F7@orbiteam.de>
Message-Id: <263B8000-CF4E-4EAE-9A3E-57BE4014E675@cominvent.com>
archived-at: Fri, 06 Jan 2017 11:32:58 -0000

--Apple-Mail=_B0AAD1B1-3420-4CCA-A24F-387E14A1807F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

> I hope you didn=E2=80=99t get this wrong! We all appreciate the =
existence of JCC/PyLucene and especially all the effort you=E2=80=99ve =
put into this. =20


PyLucene is driven by its own community, and user involvement and =
contributions is a must.
The (sub)project will survive only to the extent that its current users =
invest in it.

> So if some funding is required to get this going =E2=80=A6

For an ASF Open Source Project, the only thing that is required to get =
going 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 =
for other users to step ut and take
responsibility.

How =E2=80=9Cfunding=E2=80=9D would look like in the Python3 case is not =
so much sending money to the ASF,
but more for individual companies like your own, to sponsor (through =
developer time) the major
work on the patch, and driving it through to completion. Hopefully other =
users will contribute along
the way too.

You will of course need help from experienced developers, but the ideal =
situation is that after
a couple of such patches that get committed, you (or the developer =
working on the code) will be nominated=20
as committer and can continue developing PyLucene without the need for =
Andi or any other one individual.

> There has been some discussions about the future of PyLucene on this =
list but I still didn't see any conclusion/decision


The discussion sparked some new development and a release, which is a =
success. So the decission I guess is to keep PyLucene alive and try to =
strengthen the community.
As long as the project continues to produce releases, it is (somewhat) =
alive.
If on the other hand another year or two goes by without another =
release, I=E2=80=99m sure the PMC will take action again.

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

> 6. jan. 2017 kl. 10.34 skrev Thomas Koch <koch@orbiteam.de>:
>=20
> Dear Andi,
>=20
> I=E2=80=99ve just sent the link to the public gist with the patch to =
Petrus and this list. As mentioned by Oliver we=E2=80=99d be more than =
happy if a core developer of JCC/PyLucene could review the patch and =
decide what to do with it. It has been developed without intimate =
knowledge of JCC with the goal to make PyLucene(36) usable with Python3. =
It may have some issues or need improvements (also cf. "IMPORTANT NOTES" =
in my last email about current limitations of the patch). That=E2=80=99s =
where export review (and effort) is needed.=20
>=20
> For the future of course a port to newer versions of JCC/PyLucene =
would be more than valuable. I think what Oliver wanted to express is =
that we don=E2=80=99t have that much deep know how of JCC and can thus =
can only provide initial efforts and contributions, but for =
production/release ready code an export review is still needed. Also we =
haven=E2=80=99t watched the development of newer versions of PyLucene as =
we=E2=80=99re still stuck with PyLucene36.
>=20
> I hope you didn=E2=80=99t get this wrong! We all appreciate the =
existence of JCC/PyLucene and especially all the effort you=E2=80=99ve =
put into this. =20
>=20
> However, I fear that Python 3 support is a must-have for a Python tool =
or library that's available today:
> - Python3 is here to stay! (py3.6 has just been released)
> - Most of the popular Python packages do meanwhile provide Python3 =
support - cf. http://py3readiness.org <http://py3readiness.org/>
> - Python2 support will end by 2020 (sounds far away but isn't - cf.  =
https://pythonclock.org <https://pythonclock.org/> )
>=20
> There has been some discussions about the future of PyLucene on this =
list but I still didn't see any conclusion/decision. Without a =
transparent roadmap and ongoing development (i.e. new releases, Python3 =
support etc.) the usage of JCC/PyLucene is most likely unattractive for =
developers who start a new project and this is where the user base =
shrinks and further contributions are stalled (somehow a =
chicken-egg-problem).
>=20
> I'm not sure how far the ASF may help here, but I've read that the =
Python Software Foundation occasionally funds projects to port libraries =
that are widely used but don't have enough of a community to do a port.
> cf. =
https://developers.slashdot.org/story/13/08/25/2115204/interviews-guido-va=
n-rossum-answers-your-questions =
<https://developers.slashdot.org/story/13/08/25/2115204/interviews-guido-v=
an-rossum-answers-your-questions>
>=20
> So if some funding is required to get this going ...
>=20
>=20
>=20
> best regards,
>=20
> Thomas
> =E2=80=94=20
>> Am 04.01.2017 um 19:41 schrieb Andi Vajda <vajda@apache.org>:
>>=20
>>>=20
>>> Note that PyLucene currently lacks official Python3 support!
>>> We've done a port of PyLucene 3.6 (!) to support Python3 and offered =
the patches needed to JCC and PyLucene for use/review on the list - but =
didn't get any feedback so far.=20
>>> cf. =
https://www.mail-archive.com/pylucene-dev@lucene.apache.org/msg02167.html =
<https://www.mail-archive.com/pylucene-dev@lucene.apache.org/msg02167.html=
> =
<https://www.mail-archive.com/pylucene-dev@lucene.apache.org/msg02167.html=
 =
<https://www.mail-archive.com/pylucene-dev@lucene.apache.org/msg02167.html=
>>
>>=20
>> Indeed, re-reading this thread, I remember now. There is no patch =
attached and the tone of the contribution offer is a little off putting. =
It comes across more as a one time abandon-ware contribution as =
something with authors standing behind ready to respond to code review =
comments. I have a similar python 3 jcc patch sitting in an svn branch =
that could be revived. I've stated in the past that I intended to do so =
but lacked time. Interest in a Python 3 jcc has been scant so I haven't =
put much priority into this task.
>>=20
>> Andi..
>>=20
>>=20
>=20


--Apple-Mail=_B0AAD1B1-3420-4CCA-A24F-387E14A1807F--