You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Karl Wright <kw...@metacarta.com> on 2010/03/08 15:13:38 UTC
Proposed status
Here's a swag at the proposed status, in wiki form. Please let me know what should be added/removed/clarified, etc.
Thanks,
Karl
=== Description ===
Lucene Connector Framework is an incremental crawler framework and set of connectors designed to pull documents from various
kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC),
FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content.
Lucene Connector Framework also provides components for individual document security within a target search engine, so that
repository security access conventions can be enforced in the search results.
Lucene Connector Framework has been in incubation since January, 2010.
=== A list of the three most important issues to address in the move towards graduation ===
1. Need to include README, LICENSE, NOTICE, etc. at the project level
1. End-user documentation needs to be converted into a usable form
1. Apache2 plugin source needs a build mechanism
=== Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? ===
1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since
we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support
LiveLink, Meridio, SharePoint, RSS, and Web connectors properly.
=== How has the community developed since the last report? ===
So far, most of the activity has been from the mentors and the committers, but given the nascent state of the project this is
not surprising, and we expect interest to continue growing.
=== How has the project developed since the last report? ===
Lucene Connector Framework was voted into the Incubator in January 11, 2010. The following has been done since then:
* Mailing lists set up
* Site created
* SVN area set up
* Code grant from MetaCarta accepted in early February, including Apache 2.0 headers on all pertinent files, and was committed
to SVN at that time
* An ant build system for the Java code was created and tested
* Code was MetaCarta de-branded
* Code was formatted in accordance with Apache standards
* Issues related to upstream propagation of features into other Apache projects were opened
* Documentation for building and hand setup was committed
At this point the project is buildable and usable.
Re: Proposed status
Posted by Karl Wright <kw...@metacarta.com>.
Grant Ingersoll wrote:
> This looks good to me.
>
OK, I committed it. Please sign off after a final review, if you think it's still OK.
Thanks,
Karl
>
> On Mar 8, 2010, at 9:13 AM, Karl Wright wrote:
>
>> Here's a swag at the proposed status, in wiki form. Please let me know what should be added/removed/clarified, etc.
>>
>> Thanks,
>> Karl
>>
>>
>> === Description ===
>> Lucene Connector Framework is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. Lucene Connector Framework also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results.
>>
>> Lucene Connector Framework has been in incubation since January, 2010.
>>
>> === A list of the three most important issues to address in the move towards graduation ===
>> 1. Need to include README, LICENSE, NOTICE, etc. at the project level
>> 1. End-user documentation needs to be converted into a usable form
>> 1. Apache2 plugin source needs a build mechanism
>>
>> === Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? ===
>> 1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web connectors properly.
>>
>> === How has the community developed since the last report? ===
>> So far, most of the activity has been from the mentors and the committers, but given the nascent state of the project this is not surprising, and we expect interest to continue growing.
>>
>> === How has the project developed since the last report? ===
>> Lucene Connector Framework was voted into the Incubator in January 11, 2010. The following has been done since then:
>>
>> * Mailing lists set up
>> * Site created
>> * SVN area set up
>> * Code grant from MetaCarta accepted in early February, including Apache 2.0 headers on all pertinent files, and was committed to SVN at that time
>> * An ant build system for the Java code was created and tested
>> * Code was MetaCarta de-branded
>> * Code was formatted in accordance with Apache standards
>> * Issues related to upstream propagation of features into other Apache projects were opened
>> * Documentation for building and hand setup was committed
>>
>> At this point the project is buildable and usable.
>>
>>
>>
>
Re: Proposed status
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Mar 9, 2010 at 3:22 PM, Grant Ingersoll <gs...@apache.org> wrote:
> This looks good to me.
+1 from me too.
One note though, mostly something to keep in mind for the next report:
On Mar 8, 2010, at 9:13 AM, Karl Wright wrote:
> === A list of the three most important issues to address in the move towards graduation ===
> 1. Need to include README, LICENSE, NOTICE, etc. at the project level
> 1. End-user documentation needs to be converted into a usable form
> 1. Apache2 plugin source needs a build mechanism
The Incubator graduation criteria don't refer to technical quality or
status, so strictly speaking the points about documentation and build
system are not required here. The size and diversity of the
development community is a more important consideration for
graduation.
BR,
Jukka Zitting
Re: Proposed status
Posted by Grant Ingersoll <gs...@apache.org>.
This looks good to me.
On Mar 8, 2010, at 9:13 AM, Karl Wright wrote:
>
> Here's a swag at the proposed status, in wiki form. Please let me know what should be added/removed/clarified, etc.
>
> Thanks,
> Karl
>
>
> === Description ===
> Lucene Connector Framework is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. Lucene Connector Framework also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results.
>
> Lucene Connector Framework has been in incubation since January, 2010.
>
> === A list of the three most important issues to address in the move towards graduation ===
> 1. Need to include README, LICENSE, NOTICE, etc. at the project level
> 1. End-user documentation needs to be converted into a usable form
> 1. Apache2 plugin source needs a build mechanism
>
> === Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? ===
> 1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web connectors properly.
>
> === How has the community developed since the last report? ===
> So far, most of the activity has been from the mentors and the committers, but given the nascent state of the project this is not surprising, and we expect interest to continue growing.
>
> === How has the project developed since the last report? ===
> Lucene Connector Framework was voted into the Incubator in January 11, 2010. The following has been done since then:
>
> * Mailing lists set up
> * Site created
> * SVN area set up
> * Code grant from MetaCarta accepted in early February, including Apache 2.0 headers on all pertinent files, and was committed to SVN at that time
> * An ant build system for the Java code was created and tested
> * Code was MetaCarta de-branded
> * Code was formatted in accordance with Apache standards
> * Issues related to upstream propagation of features into other Apache projects were opened
> * Documentation for building and hand setup was committed
>
> At this point the project is buildable and usable.
>
>
>