[ 
https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916450#action_12916450
 ] 

Grant Ingersoll commented on LUCENE-2562:
-----------------------------------------

How many contributors have there been to Luke outside of the ASF?  I know 
Andrzej and Mark.  I know I have put up a patch, I think.  Was explicit 
permission given to use?  I guess it comes down to ownership.  I suppose you 
could split out where those patches were applied to, as well.  Given that we 
are dropping the Thinlet stuff, anything that was changed there doesn't matter.

> Make Luke a Lucene/Solr Module
> ------------------------------
>
>                 Key: LUCENE-2562
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2562
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Mark Miller
>         Attachments: luke1.jpg, luke2.jpg, luke3.jpg
>
>
> see
> http://search.lucidimagination.com/search/document/ee0e048c6b56ee2/luke_in_need_of_maintainer
> http://search.lucidimagination.com/search/document/5e53136b7dcb609b/web_based_luke
> I think it would be great if there was a version of Luke that always worked 
> with trunk - and it would also be great if it was easier to match Luke jars 
> with Lucene versions.
> While I'd like to get GWT Luke into the mix as well, I think the easiest 
> starting point is to straight port Luke to another UI toolkit before 
> abstracting out DTO objects that both GWT Luke and Pivot Luke could share.
> I've started slowly converting Luke's use of thinlet to Apache Pivot. I 
> haven't/don't have a lot of time for this at the moment, but I've plugged 
> away here and there over the past work or two. There is still a *lot* to do.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to