[
https://issues.apache.org/jira/browse/LUCENENET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465234#comment-16465234
]
Shad Storhaug commented on LUCENENET-601:
-----------------------------------------
As pointed out in the sponsorship document Stefan linked to, most of the money
goes to the Apache infrastructure. The actual Lucene.NET contributors would see
none of it unless you specifically request to do so and Apache agrees. Although
donating to Apache might also be a worthy cause, it would be unlikely to move
the Lucene.NET project forward from where it is now.
I would be interested in picking this up again (even part-time) if I were being
personally sponsored for it. I worked on this project full-time for over a year
and a half, and would like to see all of that work go to good use. I stopped
just after the 1st of the year because it was unrealistic to keep going without
at least being able to cover my minimum expenses.
The main things that need finishing on Lucene.NET 4.8.0 are:
# Recently reported bugs
# The ICU (International Components for Unicode) functionality
# API documentation
# An update to the web site
# Updating the WIKI (personally, I found it confusing what to keep and what to
throw out there)
The ICU functionality was what I was working on last. I created a fresh port of
the [ICU4J project|http://site.icu-project.org/] and was hoping to submit my
.NET contribution back to them. I ported about 40% of the project (just the
parts that Lucene.NET depends on) at version 60.1, and have successfully made
all Lucene.NET tests green. That version was released on November 1, 2017, but
since then the ICU project is nearing completion of version 62. However, when
refactoring APIs I realized how much work there was to get ICU to really
interoperate with .NET. It follows the Java API (and is actually intended to
replace the functionality in some of the Java classes). To really follow their
lead, those APIs would need to be .NET-like (for example, have the same API as
{{System.Char}} instead of {{java.text.Character}}). In addition, it would work
best to subclass the .NET {{CultureInfo}} class to be able to make the extended
functionality into a direct replacement for {{CultureInfo}}, and some
additional work would be required to work out how to make the functionality
context-sensitive as it is in the rest of .NET.
That said, the ICU functionality doesn't apply to everyone. I can see uses for
some of the functionality (even in the English-speaking world) but if push came
to shove we could do a release without it and possibly add it at a later point.
We could also realistically release without the web site and WIKI.
Please send an email to me at *shad \-\-AT\-\- shadstorhaug.com* to discuss the
direction of the project from here and financial contributions that would
actually help to get Lucene.NET 4.8.0 (and possibly future versions) released.
> How does one provide monetary donations / sponsorship for your project?
> -----------------------------------------------------------------------
>
> Key: LUCENENET-601
> URL: https://issues.apache.org/jira/browse/LUCENENET-601
> Project: Lucene.Net
> Issue Type: Task
> Components: ASF Process
> Reporter: Rob Reynolds
> Priority: Major
>
> Hi [~NightOwl888] / [~itamar]!
>
> We have just kicked off our philanthropy to give back to FOSS projects in the
> Windows and .NET space. We've decided to start with projects that we use.
> We'd love to discuss more on this. Can you provide us donation link or paypal
> email please?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
