Re: The future of the PyLucene project

[Andi Vajda]

So it does look like there are users of PyLucene who would like the project 
to continue, after all. As long as there is interest I'm happy to continue 
with it as well.


Thank you all who responded to this thread !

Andi..

On Wed, 28 Feb 2024, Andi Vajda wrote:



Hi PyLucene users and Lucene PMC,

A week ago, on Wednesday February 21st, I started a voting thread for 
qualifying a new PyLucene release candidate to catch-up with the recent 
Lucene 9.10.0 release and fix a bug in JCC.


Usually these voting threads get a couple of +1 for PyLucene users before 
getting votes from a couple of people on the Lucene PMC, always the same ones 
;-) Three PMC +1 votes -> a release can happen.


This time, crickets, the voting thread has been completely quiet.

If there are no PyLucene users anymore, maybe it's time to shut the project 
down ? Personally, I think that the "software value" in the project is all in 
JCC. PyLucene itself is 99% machine generated by JCC around Java Lucene.


Of course, having Java Lucene available that way from Python is pretty cool 
so I don't want diminish PyLucene's "usage value", but from a software 
engineering standpoint, the itch, if you prefer, all the cool stuff is done 
in JCC.


If the Lucene PMC agrees and no PyLucene users come forward, I propose the 
following:

 - shutdown the PyLucene project
 - fork JCC to my gitlab (https://gitlab.pyicu.org/main) where it can
   get the occasional fix or improvement before being released to PyPI.
   JCC has been distributed from PyPI forever,
 https://pypi.org/project/JCC/#history
   so JCC users shouldn't even notice this...

What do you all think ?
This message is not a vote, I'm just trying to gauge interest in PyLucene and 
JCC.


Andi..

ps: for those who have never heard of PyLucene, it is a sub-project of
   Apache Lucene hosted here:
 https://lucene.apache.org/pylucene/index.html
pps: for those who have never heard of JCC, it is a sub-project of PyLucene
 hosted here: https://lucene.apache.org/pylucene/jcc/index.html

Re: The future of the PyLucene project

[Bart Moelans]

Dear Andi

I probably missed the mail to vote, I apoligize for that. At Antwerp University 
we still use PyLucene for several purposes on production services. So please 
continue the good work.

Best regards

Bart

dr. Bart Moelans  
(he/him/his)
Technologisch Manager

[8P7IGoY8iEEZwASUVORK5CYII=]
Bibliotheek UAntwerpen
Stadscampus - Lokaal Ve35.304
Venusstraat 35 - 2000 Antwerpen - België
bart.moel...@uantwerpen.be
T +32 486 78 01 85
[phgdtZ4L+dRbHxpMAR8wBJRU5ErkJggg==]


From: Andi Vajda 
Date: Wednesday, 28 February 2024 at 20:48
To: pylucene-dev@lucene.apache.org , 
priv...@lucene.apache.org 
Subject: The future of the PyLucene project
CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


  Hi PyLucene users and Lucene PMC,

A week ago, on Wednesday February 21st, I started a voting thread for
qualifying a new PyLucene release candidate to catch-up with the recent
Lucene 9.10.0 release and fix a bug in JCC.

Usually these voting threads get a couple of +1 for PyLucene users before
getting votes from a couple of people on the Lucene PMC, always the same
ones ;-) Three PMC +1 votes -> a release can happen.

This time, crickets, the voting thread has been completely quiet.

If there are no PyLucene users anymore, maybe it's time to shut the project
down ? Personally, I think that the "software value" in the project is all
in JCC. PyLucene itself is 99% machine generated by JCC around Java Lucene.

Of course, having Java Lucene available that way from Python is pretty cool
so I don't want diminish PyLucene's "usage value", but from a software
engineering standpoint, the itch, if you prefer, all the cool stuff is done
in JCC.

If the Lucene PMC agrees and no PyLucene users come forward, I propose the
following:
   - shutdown the PyLucene project
   - fork JCC to my gitlab 
(https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.pyicu.org%2Fmain=05%7C02%7CBart.Moelans%40uantwerpen.be%7C5963406229204f43d03f08dc389639d9%7C792e08fb2d544a8eaf72202548136ef6%7C0%7C0%7C638447465066808772%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=YMILZApLUKkHQxaI03oq%2ByJgHY9i%2FORWGIVQxRkS9kw%3D=0)
 where it can
 get the occasional fix or improvement before being released to PyPI.
 JCC has been distributed from PyPI forever,
   
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2FJCC%2F%23history=05%7C02%7CBart.Moelans%40uantwerpen.be%7C5963406229204f43d03f08dc389639d9%7C792e08fb2d544a8eaf72202548136ef6%7C0%7C0%7C638447465066816875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=NfACVt8r1kQYc9XVELlQFJwI0ZkHSGxJjI5pufLWDLY%3D=0
 so JCC users shouldn't even notice this...

What do you all think ?
This message is not a vote, I'm just trying to gauge interest in PyLucene
and JCC.

Andi..

ps: for those who have never heard of PyLucene, it is a sub-project of
 Apache Lucene hosted here:
   
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flucene.apache.org%2Fpylucene%2Findex.html=05%7C02%7CBart.Moelans%40uantwerpen.be%7C5963406229204f43d03f08dc389639d9%7C792e08fb2d544a8eaf72202548136ef6%7C0%7C0%7C638447465066822626%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=MvzYQSDXSZen%2FCzO5YLhPETTEDKZQX5UqGk6vcp5y1I%3D=0
pps: for those who have never heard of JCC, it is a sub-project of PyLucene
   hosted here: 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flucene.apache.org%2Fpylucene%2Fjcc%2Findex.html=05%7C02%7CBart.Moelans%40uantwerpen.be%7C5963406229204f43d03f08dc389639d9%7C792e08fb2d544a8eaf72202548136ef6%7C0%7C0%7C638447465066827160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=zVv97tOHJurSW2psjdBhd16xFasiZGbjaCX2D3xFY3s%3D=0

Re: The future of the PyLucene project

[Jeff Breidenbach]

My excuse is I'm increasingly bad at reading email. Still using. Still
encouraging.


On Wed, Feb 28, 2024 at 9:32 PM Aric Coady  wrote:

> On Feb 28, 2024, at 2:29 PM, Andi Vajda  wrote:
> > Of course anyone can vote !
> > Anyone interested in this project can and should vote !
> > If no one does, how do we know anyone cares ?
>
> +0.5. I’m still maintaining a docker image (coady/pylucene:rc), a homebrew
> formula, and a dependent project (lupyne). But the state of that project is
> much the same - I don’t know how much interest there still is in it.
>
> I feel like Lucene should have python bindings in principle, but I don’t
> personally have a use case anymore. Thanks for your work on this, whatever
> you decide.
>
>

Re: The future of the PyLucene project

[Aric Coady]

On Feb 28, 2024, at 2:29 PM, Andi Vajda  wrote:
> Of course anyone can vote !
> Anyone interested in this project can and should vote !
> If no one does, how do we know anyone cares ?

+0.5. I’m still maintaining a docker image (coady/pylucene:rc), a homebrew 
formula, and a dependent project (lupyne). But the state of that project is 
much the same - I don’t know how much interest there still is in it.

I feel like Lucene should have python bindings in principle, but I don’t 
personally have a use case anymore. Thanks for your work on this, whatever you 
decide.

Re: The future of the PyLucene project

[Andi Vajda]

On Wed, 28 Feb 2024, Erik Groeneveld LPV wrote:

I always followed new releases and checked the change log for both 
PyLucene and Lucene. I never felt entitled to vote however.


This seems to be a common misconception.
Everyone can vote on a release, everyone is entitled to.
It's just an Apache Rule that 3 PMC +1 votes are required to make a release.

Look at it this way: if a non-PMC user votes +1, it's a sign of interest.
If such a user votes -1, it's even more: a sign of participation and a 
non-binding veto to the release.
Sure, according to the rules, one can ignore it and go ahead with the 
release but what does that say to your user community ?


Of course anyone can vote !
Anyone interested in this project can and should vote !
If no one does, how do we know anyone cares ?

Andi..



I can still vote, but I think it would be more appropriate if Thijs does 
that.


Keep up the good work!
Erik

On Wed, Feb 28, 2024 at 21:08, Dawid Weiss <[dawid.we...@gmail.com](mailto:On Wed, Feb 
28, 2024 at 21:08, Dawid Weiss < wrote:


Hi Andi,

This time, crickets, the voting thread has been completely quiet.




For me - and it's not an excuse at all - you hit winter holidays, I'm
really sorry!


If the Lucene PMC agrees and no PyLucene users come forward, I propose the
following:
- shutdown the PyLucene project
- fork JCC to my gitlab (https://gitlab.pyicu.org/main) where it can
get the occasional fix or improvement before being released to PyPI.
JCC has been distributed from PyPI forever,
https://pypi.org/project/JCC/#history
so JCC users shouldn't even notice this...



I think open source is mostly about the community and folks coding together
for fun... And not many of us seem to be
able to help you with PyLucene development - I can't, for that matter,
because my Python is really limited.

Your plan sounds good to me. And you'd get more freedom from procedural
release
requirements at Apache too, which sounds like an added benefit?... :)

I also hope that, regardless of the status of PyLucene and JCC, you remain
with the Lucene project.

Dawid

--
Seecr is een kleine groep zeer ervaren full cycle software engineers. We
specialiseren ons in Linux, search en dataverwerking met de laatste
technieken. Wilt u weten meer weten? Kijk op seecr.nl .

Re: The future of the PyLucene project

[Erik Groeneveld LPV]

Hi Andy,

Thank you very much for PyLucene!

Seecr uses PyLucene extensively in all kinds of projects, in production systems.

A few weeks ago I sold the company, but I am sure they still use PyLucene and 
will continue doing so. I cc’d the new owner, Thijs.

I always followed new releases and checked the change log for both PyLucene and 
Lucene. I never felt entitled to vote however.

I can still vote, but I think it would be more appropriate if Thijs does that.

Keep up the good work!
Erik

On Wed, Feb 28, 2024 at 21:08, Dawid Weiss <[dawid.we...@gmail.com](mailto:On 
Wed, Feb 28, 2024 at 21:08, Dawid Weiss < wrote:

> Hi Andi,
>
> This time, crickets, the voting thread has been completely quiet.
>>
>
> For me - and it's not an excuse at all - you hit winter holidays, I'm
> really sorry!
>
>> If the Lucene PMC agrees and no PyLucene users come forward, I propose the
>> following:
>> - shutdown the PyLucene project
>> - fork JCC to my gitlab (https://gitlab.pyicu.org/main) where it can
>> get the occasional fix or improvement before being released to PyPI.
>> JCC has been distributed from PyPI forever,
>> https://pypi.org/project/JCC/#history
>> so JCC users shouldn't even notice this...
>>
>
> I think open source is mostly about the community and folks coding together
> for fun... And not many of us seem to be
> able to help you with PyLucene development - I can't, for that matter,
> because my Python is really limited.
>
> Your plan sounds good to me. And you'd get more freedom from procedural
> release
> requirements at Apache too, which sounds like an added benefit?... :)
>
> I also hope that, regardless of the status of PyLucene and JCC, you remain
> with the Lucene project.
>
> Dawid
>
> --
> Seecr is een kleine groep zeer ervaren full cycle software engineers. We
> specialiseren ons in Linux, search en dataverwerking met de laatste
> technieken. Wilt u weten meer weten? Kijk op seecr.nl .

Re: The future of the PyLucene project

[Dawid Weiss]

Hi Andi,

This time, crickets, the voting thread has been completely quiet.
>

For me - and it's not an excuse at all - you hit winter holidays, I'm
really sorry!


> If the Lucene PMC agrees and no PyLucene users come forward, I propose the
> following:
>- shutdown the PyLucene project
>- fork JCC to my gitlab (https://gitlab.pyicu.org/main) where it can
>  get the occasional fix or improvement before being released to PyPI.
>  JCC has been distributed from PyPI forever,
>https://pypi.org/project/JCC/#history
>  so JCC users shouldn't even notice this...
>

I think open source is mostly about the community and folks coding together
for fun... And not many of us seem to be
able to help you with PyLucene development - I can't, for that matter,
because my Python is really limited.

Your plan sounds good to me. And you'd get more freedom from procedural
release
requirements at Apache too, which sounds  like an added benefit?... :)

I also hope that, regardless of the status of PyLucene and JCC, you remain
with the Lucene project.

Dawid