> On Jan 12, 2017, at 03:47, Jan Høydahl wrote:
>
>
>>> The (sub)project will survive only to the extent that its current users
>>> invest in it.
>> so is this different to how the main (Java)Lucene project works? just
>> curious …
>
> This is the case for all ASF projects and sub projects.
> On Jan 12, 2017, at 02:22, Thomas Koch wrote:
>
> Dear Jan,
> thanks for your explanations.
>
>> PyLucene is driven by its own community, and user involvement and
>> contributions is a must.
> I’m quite familiar with community contributions - have already submitted code
> and feedback, tes
>> The (sub)project will survive only to the extent that its current users
>> invest in it.
> so is this different to how the main (Java)Lucene project works? just curious
> …
This is the case for all ASF projects and sub projects. If a project is unable
to produce
new releases, usually due to
Dear Andi,
many thanks for your review of the patch and helpful comments.
As mentioned in my previous mail to the list I’m afraid to let you know that we
currently cannot put more effort into this task. This may change in the future
of course.
However, with „funding“ my idea was to look for op
Dear Jan,
thanks for your explanations.
> PyLucene is driven by its own community, and user involvement and
> contributions is a must.
I’m quite familiar with community contributions - have already submitted code
and feedback, tested Pylucene releases, did provide support to other users and
vo
Dear Petrus,
thanks for your feedback - good to know that it’s useful for you application.
And at least one more user who asks for Python3 Support in JCC ,-)
best regards,
Thomas
—
> Am 11.01.2017 um 23:14 schrieb Petrus Hyvönen :
>
> Dear Thomas,
>
> Thanks for the patch files, I am not usin
