Re: [VOTE] Apache Drill 0.6.0-incubating release
Not sure, and maybe a bit pedantic, but is the NOTICE file a little thin (practically non-existent) given the number of 3rd party libs present? I'm not an expert on what is required there, but when I compare it to projects I'm familiar with like Solr and Mahout, they are vastly different. I _believe_ the NOTICE file is where you are supposed to put NOTICES from licenses that require it. (someone else here can probably help) Beyond that, and I'm not sure if it is a blocker or not, things look good to the extent I tested (packaging, keys, basic run through) So, -1 if the NOTICE thing is a thing that needs to be dealt with now. +1 if it is not. In either case, that would be binding. -Grant On Oct 5, 2014, at 2:14 PM, Steven Phillips s...@apache.org wrote: I would like to present the Apache Drill 0.6.0-incubating release to the general incubator list for a vote. This set of artifacts have passed our drill-dev vote and incorporate a number of improvements with over 30 JIRAs closed in the last month. The vote thread can be found here:http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201410.mbox/%3CCAA_-67fAJFB20wGX462wm7BYvoSy3PvydCPgY9uNSEj3HpQRmg%40mail.gmail.com%3E The vote passed with: +9 binding +3 non-binding You can find the artifacts for the release at this location:http://people.apache.org/~smp/apache-drill-0.6.0.rc0/ I look forward to your feedback. Thanks, Steven
Re: [VOTE] first milestone release of Apache Drill (incubating)
+1, binding On Sep 17, 2013, at 6:29 PM, Ted Dunning ted.dunn...@gmail.com wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release
Re: [VOTE] Accept Drill into the Apache Incubator
On Aug 7, 2012, at 10:41 PM, Ted Dunning wrote: I would like to call a vote for accepting Drill for incubation in the Apache Incubator. The full proposal is available below. Discussion over the last few days has been quite positive. Please cast your vote: [ ] +1, bring Drill into Incubator +1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] cTAKES for the Apache Incubator
of the developers are not paid to work specifically on cTAKES, so there is little reliance on salaried developers. === Relationships with Other Apache Products === NLP is often used in search and other algorithms that work with unstructured data, thus cTAKES is likely to be useful to the Lucene and Solr communities. It also aligns nicely with both Mahout and UIMA as well as OpenNLP. === A Excessive Fascination with the Apache Brand === We think the project aligns nicely with the goals of the ASF to disseminate source code to the public free of charge. Clinical NLP has long been the subject of cutting edge research, but is often lacking in community and shared knowledge. We believe that by bringing cTAKES to the ASF, the Apache brand will help deliver clinical NLP capabilities to a much larger audience and likewise a cutting edge project like cTAKES can further the ASF brand by providing users with tried and true, as well as new, natural language processing capabilities. == Documentation == * https://wiki.nci.nih.gov/display/VKC/cTAKES+2.0 * http://en.wikipedia.org/wiki/CTAKES == Initial Source == The source code is maintained in SVN on SourceForge: cTAKES: http://sourceforge.net/projects/ohnlp/ == Source and Intellectual Property Submission Plan == The cTAKES source code is already open source under the AL 2.0. == External Dependencies == ||'''Library''' style=text-align: center'''License''' style=text-align: center'''Description''' || ||libsvm style=text-align: centerBSD style=text-align: centerMachine Learning Library || ||UIMA style=text-align: centerAL 2.0 style=text-align: centerUnstructured Information Management Architecture || ||Lucene Core style=text-align: centerAL 2.0 style=text-align: centerPlain Text Search Engine Library || ||OpenNLPstyle=text-align: centerAL 2.0 style=text-align: centerGeneral Purpose Natural Language Processing Library|| ||HSQLDBstyle=text-align: centerBSDstyle=text-align: centerIn Memory DB|| ||JDOMstyle=text-align: centerApache Stylestyle=text-align: centerJava XML Manipulation Libraryv|| ||Open AI FSMstyle=text-align: centerApache Stylestyle=text-align: centerFinite State Machines Toolset|| == Cryptography == cTAKES neither provides nor uses any cryptography. == Required Resources == === Mailing lists === * ctakes-dev * ctakes-private * ctakes-user * ctakes-commits === Subversion Directory === https://svn.apache.org/repos/asf/incubator/ctakes === Issue Tracking === Jira: cTAKES === Other Resources === == Initial Committers == ||'''Name''' style=text-align: center'''Email''' style=text-align: center'''CLA''' || ||Pei J Chen style=text-align: centerpei.c...@childrens.harvard.edu style=text-align: centeryes || ||Sean Finan style=text-align: centersean.fi...@childrens.harvard.edu style=text-align: centerno || ||Guergana K. Savova style=text-align: centerguergana.sav...@childrens.harvard.edu style=text-align: centerno || ||James J Masanz style=text-align: centermasanz.ja...@mayo.edu style=text-align: centerno || == Affiliations == == Sponsors == === Champion === Jörn Kottmann === Nominated Mentors === * Jörn Kottmann * Grant Ingersoll * Chris A Mattmann === Sponsoring Entity === The Apache Incubator On 05/30/2012 11:59 PM, Chen, Pei wrote: Hi All, We would like to propose cTAKES to be an Apache Incubator project. cTAKES: (clinical Text Analysis and Knowledge Extraction System) is an natural language processing tool for information extraction from electronic medical record clinical free-text. Additional information is available at http://en.wikipedia.org/wiki/CTAKES and https://wiki.nci.nih.gov/display/VKC/cTAKES+2.5 . The draft proposal document is available at http://wiki.apache.org/incubator/cTAKESProposal We're excited about the opportunity to work with ASF and the community to create an Incubator project for Natural Language Processing for the clinical domain. We'll welcome all feedback on the proposal. Thanks. --- Pei Chen Lead Application Development Specialist Childrens Hospital Boston / Harvard Medical School 300 Longwood Avenue, Enders 142 Boston, MA 02115 tel: (617) 919-4423 fax: (617) 730-0057 pei.c...@childrens.harvard.edu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Re: How to submit IP Clearance
On Aug 8, 2011, at 4:19 AM, Simon Willnauer wrote: hey folks, the apache lucene project currently works on a code donation for Kuromoji Japanese Analyzer [1]. ICLA, CLA and code grant have been received and as far as I know we now need to submit the ip-clearance.xml file to the incubator website. I am wondering how I submit this or who is going to commit this. I think as a member I can commit to the incubator svn but I don't want to do this without explicit permission though. As a Member, you can ask to be on the Incubator PMC, which should then give you the karma once accepted. Otherwise, I'd be happy to do the commit. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release ManifoldCF 0.2-incubating, RC2
On May 9, 2011, at 4:34 AM, Karl Wright wrote: Hi - just to clarify, we did not include the HTTPD extension in the release, but it remains available in source control for backwards compatibility. Most people use the Active Directory Authority at the moment. But thank you for compiling it. As for the RAT report, the skins question is known and a ticket is open for that. The other files are temporary files resulting from your test run and I will open a ticket to exclude those from the rat-source target. We've still received zero binding evaluations from incubator for this release, FWIW. Sorry, I presumed my PPMC vote would count here as well, so +1 (binding) from me. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache opennlp-1.5.1-incubating-rc7
+1 (binding) On Apr 29, 2011, at 6:35 AM, Jörn Kottmann wrote: Hi all, please review and vote on approving our first release of Apache OpenNLP. OpenNLP is a machine learning based toolkit for the processing of natural language text. It supports the most common NLP tasks, such as tokenization, sentence segmentation, part-of-speech tagging, named entity extraction, chunking, parsing, and coreference resolution. The OpenNLP community approved the release of opennlp-1.5.1-rc7 in this vote thread with 4 binding and 2 non-binding +1 votes and we received no 0 or -1 votes: http://mail-archives.apache.org/mod_mbox/incubator-opennlp-dev/201104.mbox/%3c4dba8705.8060...@gmail.com%3e The release artifacts and rat reports can be found here: http://people.apache.org/~joern/releases/opennlp-1.5.1-incubating/rc7/ Our release contains multiple sub-projects, the rat reports have been generated for each of these sub-projects. We will try to improved that for our next release, any hints about that are welcome. Many thanks for your support, Jörn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
adding committers to a project
Does adding a committer to a incubating project require an IPMC vote (assuming the PPMC vote passes)? Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Lucene.Net for incubation
the work of the Lucy project into Lucene.Net at some point as well. There is also a strong interest in creating .NET ports of ASF's Solr, Tika, Hadoop, and others. While that would fall outside of the scope of this project, there may be overlap in terms of the committers between those projects and sharing of code and methodologies pioneered in the Lucene.Net project. === An Excessive Fascination with the Apache Brand === Our desire to maintain Lucene.Net's affiliation with Apache has less to do with the brand and more to do with our conviction that developing the project 'The Apache Way' under Apache institutions is in Lucene.Net's best interests. However, we have to acknowledge that during its time as a Lucene subproject, Lucene.Net has not always fulfilled certain key requirements for an Apache project. In particular, it has failed to release early, release often. Also, despite making significant progress in expanding its user community, it has failed to engage with the community and remain responsive to community needs. By rebooting the project with a new list of motivated and enthusiastic committers, we expect to avoid the trap that ensnared Lucene.Net's first incarnation: we will release early, release often, accumulate users, nurture contributors, and grow our community. == Documentation == * Current Lucene.Net website: http://lucene.apache.org/lucene.net/ * Current Lucene.Net Subversion repository: http://svn.apache.org/repos/asf/lucene/lucene.net/ * Current Lucene.Net mailing lists: http://lucene.apache.org/lucene.net/ (See info under Mailing Lists heading) == Initial Source == We will continue working with the existing Lucene.Net codebase located at: http://svn.apache.org/repos/asf/lucene/lucene.net/ We will also attempt to contact the coordinators of the following Lucene.Net forks and incorporate their work into the Lucene.Net project: * Lucere - http://lucere.codeplex.com/ * Lucille - http://lucille.codeplex.com/ * Aimee.Net - http://aimee.codeplex.com/ == Source and Intellectual Property Submission Plan == All source code referred to in this project (existing codebase and that of forks) is already licensed under the Apache 2.0 License. There should be no conflicts in this regard. == External Dependencies == The only external dependencies represented in any of the proposed code are on unit testing and mocking frameworks, all of which have ASF compatible licenses. == Required Resources == === Mailing lists === * lucene-net-dev * lucene-net-commits * lucene-net-users Lucene.Net already has lucene-net-dev, lucene-net-users, and lucene-net-commits mailing lists under lucene.apache.org. While these could be deactivated and the memberships migrated to the appropriate lists under incubator.apache.org, leaving the lucene.apache.org archives as read-only, we would prefer to keep the mailing lists the same, rather than moving to incubator.apache.org. The purpose of that would be to remain engaged with our community, with minimal disruption. === Subversion Directory === Lucene.Net already has a Subversion directory at https://svn.apache.org/repos/asf/lucene/lucene.net. In keeping with naming conventions, it could be moved to http://svn.apache.org/repos/asf/incubator/lucene.net. === Issue Tracking === Lucene.Net already has a JIRA tracker: Lucene.Net (LUCENENET) === Other Resources === Lucene.Net already has a MoinMoin wiki at http://wiki.apache.org/jakarta-lucene/lucene.Net. It can be moved to standard Incubator wiki placement. There is currently no content of value in the wiki. == Initial Committers == ||'''Name''' ||'''Email''' ||'''CLA''' || ||Chris Currens ||currens.chris AT gmail DOT com ||Yes || ||DIGY ||digydigy AT gmail DOT com ||Yes || ||Michael Herndon ||mherndon AT wickedsoftware DOT net ||Yes || ||Prescott Nasser ||prescott.nasser AT hotmail DOT com ||Yes || ||Scott Lombard ||lombardenator AT gmail DOT com ||Yes || ||Sergey Mirvoda ||sergey AT mirvoda DOT com ||Yes || ||Troy Howard ||thoward37 AT gmail DOT com ||Yes || == Affiliations == * Troy Howard and Chris Currens both work for discover-e Legal, LLC and will work on Lucene.Net as part of their paid work. discover-e Legal uses the current Lucene.Net build in their products and so, has a vested interest in seeing the project continue. Beyond that, the reason Lucene.Net was chosen by Troy initially for the discover-e Legal products is due to his strong interest in the project. This interest was well established before working for discover-e Legal, and is independent of its needs. The same is true for Chris Currens. So, even though there is commercial support for their work on this project it is not the primary reason or motivator for their interest. == Sponsors == === Champion === * Grant Ingersoll (gsingers AT apache DOT org) === Nominated Mentors === * Gianugo Rabellino * Stefan Bodewig * Benson Margulies
Re: [VOTE] Release Apache ManifoldCF 0.1 incubating, RC8
+1 (binding), just as voted on ManifoldCF. -Grant On Jan 20, 2011, at 9:48 PM, Karl Wright wrote: Calling the official vote for release of ManifoldCF 0.1 incubating, RC8, which can be found at http://people.apache.org/~kwright . The community has voted for release of the new RC, so we're ready to go ahead with an incubator vote on the same. Thanks in advance! Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Lucene.Net return to the Incubator
Troy, If you have the proposal done, the next thing to do would be to call a vote to accept it. -Grant On Jan 20, 2011, at 8:55 AM, Stefan Bodewig wrote: On 2011-01-18, Troy Howard wrote: If I recall correctly we need at least two mentors before the Incubator PMC can vote on our proposal. Is there anyone else willing to help us out as Mentor? Yes, me. I've just added my name to the propsal page. Stefan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Lucene.Net return to the Incubator
Although, it does look like you need one more Mentor. On Jan 12, 2011, at 5:43 PM, Troy Howard wrote: All, Please review our proposal for moving the Lucene.Net project back to the Incubator. Lucene.Net is currently a Lucene sub-project, however, for reasons detailed in the proposal and various mailing list discussions, we have decided that a move back to the Incubator, with the intent of future graduation as a TLP is the best for the Lucene.Net project. We are pleased to say that Grant Ingersoll has agreed to be our Champion for this proposal, however we are still in need of Mentors from the Incubator community. We'd appreciate help from anyone who is interested. The proposal, in raw text form follows this email and the wiki is located here: http://wiki.apache.org/incubator/Lucene.Net%20Proposal Thanks, Troy Howard = FINAL = 'Subitted on Wednesday, January 12th, 2011' = Lucene.Net - A .NET port of Lucene = == Preface == Lucene.Net is a sub-project which is being spun off from the Lucene TLP but is not yet ready for graduation. We propose to address certain needs of the project by transitioning to an Incubator Podling. == Abstract == Lucene.Net will be a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Proposal == Lucene.Net has three aims. First, it will maintain the existing line-by-line port from Java to C#, fully automating and commoditizing the process such that the project can easily synchronize with the Java Lucene release schedule. Second, it will be a high-performance C# search engine library. Third, it will maximize its usability and power when used within the .NET runtime. To that end, it will present a highly idiomatic, carefully tailored API that takes advantage of many of the special features of the .NET runtime. == Background == Lucene.Net, began as a independent project focused on creating a line-by-line, API for API port of Java Lucene to C#. It continued successfully in this way and eventually became a ASF Incubator project in April of 2006 and graduated as a sub-project of Lucene in October of 2009. The last year has been challenging for the project. The committers who originally lead the project have stopped maintaining it and development has stagnated since June of 2010. The user community has spoken out requesting a change in philosophy and direction for the project, but those requests have been unheeded. This has led to a number of forks outside of the ASF. We would like to bring those forks back in as branches and be responsive to the needs of community without the need for multiple non-ASF forks. The Lucene PMC wants to see the project continue to thrive and has indicated that a return to the Incubator is an appropriate step, with the end goal to build of building a new team of committers and maintaining a steady release cycle meeting the previously stated goals. Because Lucene is working to move away from being an umbrella project, a long term goal of the Lucene.Net project is to graduate to an ASF TLP. == Rationale == There is great need for a search engine library in the mode of Lucene within the .NET runtime. Individuals naturally wish to code in their language of choice. Organizations which do not have significant Java expertise may not want to support Java strictly for the sake of running a Lucene installation. Developers may want to take advantage of C#'s unique language features and the .NET runtime's unique execution and interoperability model. Lucene.Net will meet all these demands. Apache is a natural home for our project given the way it has always operated: user-driven innovation, lively and amiable mailing list discussions, strength through diversity, and so on. We feel comfortable here, and we believe that we will become exemplary Apache citizens. == Initial Goals (to be completed before Feb 2011) == * Build a new list of committers * Make a 2.9.2 compatible release as quickly as possible (this already exists, it just needs to be packaged correctly) * Update website, documentation, etc. * Create a well documented repeatable and fully automated language porting process * Start a .NET style API branch, either by incorporating some or all existing fork projects or by starting a new branch to this end == Current Status == === Meritocracy === We understand meritocracy and will fully embrace this concept in our project management methodology. One of the proposed committers, DIGY, has been a committer on the current Lucene.Net project since November 2008. Prescott Nasser has been a contributor on the project, submitting patches, documentation, and website enhancements. Three of the other proposed initial committers, Troy Howard, Chris Currens and Sergey Mirvoda are both already actively involved in other open source projects, either as committers of code
Re: ManifoldCF - jars should not be stored in SVN
This seems a bit over the top. I prefer them in SVN so I can get them all at once, which is especially nice when one is working offline. On Jan 9, 2011, at 5:53 PM, sebb wrote: I've just noticed that there are lots of jars stored in SVN under http://svn.apache.org/repos/asf/incubator/lcf/branches/release-0.1-branch AIUI, SVN should not be used for storing library jars. == The way other projects manage this is to define the jar dependencies in a build file, and get the build process to download the jars. If using Maven, this is trivial, as declared dependencies are automatically downloaded. It's not that difficult when using Ant either - see for example the Tomcat or JMeter projects. There is also an Ant Maven task: http://maven.apache.org/ant-tasks/examples/dependencies.html and Apache Ivy http://ant.apache.org/ivy/ though I've not used either of those. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache ManifoldCF 0.1
Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenNLP for incubation
On Nov 19, 2010, at 4:48 AM, Jörn Kottmann wrote: Hi, lets vote on the acceptance of the OpenNLP Project for incubation at the Apache Incubator. The proposal is on the wiki http://wiki.apache.org/incubator/OpenNLPProposal and a copy is included below. The discussion thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-general/201011.mbox/%3c4ce4f1f4.3010...@gmail.com%3e Please cast your votes: [ ] +1 Accept OpenNLP for incubation +1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenNLP Project
As can be seen by my willingness to mentor/champion, I think OpenNLP would make a good ASF project. -Grant On Nov 18, 2010, at 4:29 AM, Jörn Kottmann wrote: Hello all, we would like to propose OpenNLP as a new incubator project. OpenNLP is a machine learning based toolkit for the processing of natural language text. It supports the most common NLP tasks, such as tokenization, sentence segmentation, part-of-speech tagging, named entity extraction, chunking, parsing, and coreference resolution. These tasks are usually required to build more advanced text processing services. The proposal can be found here: http://wiki.apache.org/incubator/OpenNLPProposal We are looking forward to hear your comments. Best Regards, Jörn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework
I have this vote passing 6 to 4 (binding). -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Role of Incubator PMC Votes
Presumably, the PMC's job is to be the eyes and ears of the Board, so if project is doing something wrong, the PMC should let it know. In this case, the project specifically is asking for guidance from the PMC as to whether the name change is acceptable to the PMC and thus to the ASF, assuming the Board doesn't intervene. We really do not want to go through another name change, so I really would hope all people view this as a speak now or forever hold your peace kind of thing and we can move on to the matters of graduation. -Grant On Sep 9, 2010, at 8:30 AM, Tim Williams wrote: I'm watching the renaming vote thread and I find it odd that folks are -1-ing the project's vote. I've read the role of the IPMC[1] and the policy[2] and can't find the basis for our (IPMC) doing anything other than ack-ing they're vote. It seems like votes from the IPMC should only be relevant/binding when the matter in question is release/legal/trademark/etc-type issues that could [legally] effect the foundation. I dunno, this seems purely a project matter to me (like a logo, code, etc.) - second-guessing a project team on these sort of subjective things seems counter-productive to grooming self-sustaining projects to me. So, is this normal - why does the IPMC really get anything more than an advising role in these sorts of matters (and why is that healthy)? Thanks, --tim [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29 [2] - http://incubator.apache.org/incubation/Incubation_Policy.html#Incubation+Policy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Grant Ingersoll http://lucenerevolution.org Apache Lucene/Solr Conference, Boston Oct 7-8 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework
On Sep 9, 2010, at 8:57 AM, ant elder wrote: On Thu, Sep 9, 2010 at 1:32 PM, Karl Wright daddy...@gmail.com wrote: Grant proposed that we simply go from LCF to ACF at that time, and posted accordingly to this group. He received several positive responses, and only one that raised any concerns. After a week's delay, we presumed that all was well, That may be the cause of all this - there was a concern raised but instead of being taken on board it was ignored. What was ignored? I don't follow you here. We discussed at length both here and on the connectors mailing list. Just because someone has a concern doesn't mean they overrule everyone else. -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework
Hi, After much debate both here and on the connectors mailing list, the LCF community has voted (see http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/201008.mbox/browser) and would like to officially change our name to be the Apache Connectors Framework. We would like the Incubator PMC to vote to make this official. [] +1 Change the Lucene Connector Framework to the Apache Connector Framework [] 0 Don't care [] -1 Don't change it Since this is a procedural vote (http://www.apache.org/foundation/voting.html), it is a majority rule vote with binding votes coming from IPMC members. The vote is open for 72 hours. Here's my +1 (binding). Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
On Aug 25, 2010, at 10:26 AM, Upayavira wrote: On Wed, 2010-08-25 at 09:50 -0400, Grant Ingersoll wrote: So, how does this get resolved? Shall I call a formal vote for the IPMC? I rather like the name, but (somewhat) understand the objections. That being said, I'm not all that clever at naming, so... You rather like which name?? ACF My take: 1. come up with a name. 2. check for exixting uses of that name 3. if it passes #2 then get support of your PPMC 4. Propose it to IPMC. 5. Vote on the IPMC about the name. If you want, you can add #4a: discuss with IPMC whether a vote is really required for this, in which case you might be able to skip #5, but that process would probably be slower in the end! Well, I would argue we did all that, with the exception of a formal IPMC vote (although we did ask here). It seemed to pass muster until a week later, a fair amount of time after we went and made the changes. Upayavira On Aug 25, 2010, at 7:42 AM, Upayavira wrote: On Wed, 2010-08-25 at 06:49 -0400, Grant Ingersoll wrote: Sure would have been nice if these objections (other than David's) would have been brought up last week before we went and changed everything (after waiting several days for feedback) b/c we were working under the assumption that no one thought it was a problem. At any rate, we'll go discuss. I apologise for that. Unfortunately it was (for me) one of those situations when it takes a resonable volume of mail before it attracts my attention enough to read what is being said. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Grant Ingersoll http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
On Aug 26, 2010, at 12:09 PM, David Jencks wrote: On Aug 26, 2010, at 3:41 AM, Grant Ingersoll wrote: On Aug 25, 2010, at 10:26 AM, Upayavira wrote: On Wed, 2010-08-25 at 09:50 -0400, Grant Ingersoll wrote: So, how does this get resolved? Shall I call a formal vote for the IPMC? I rather like the name, but (somewhat) understand the objections. That being said, I'm not all that clever at naming, so... You rather like which name?? ACF My take: 1. come up with a name. 2. check for exixting uses of that name 3. if it passes #2 then get support of your PPMC 4. Propose it to IPMC. 5. Vote on the IPMC about the name. If you want, you can add #4a: discuss with IPMC whether a vote is really required for this, in which case you might be able to skip #5, but that process would probably be slower in the end! Well, I would argue we did all that, with the exception of a formal IPMC vote (although we did ask here). It seemed to pass muster until a week later, a fair amount of time after we went and made the changes. I responded within 5 hours of the proposal. AFAICT the PPMC members have not responded to that post at all. Agreed, you did indeed respond. We had the discussion on the Connectors mailing list. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
Sure would have been nice if these objections (other than David's) would have been brought up last week before we went and changed everything (after waiting several days for feedback) b/c we were working under the assumption that no one thought it was a problem. At any rate, we'll go discuss. On Aug 25, 2010, at 4:32 AM, Pid wrote: On 24/08/2010 22:55, Upayavira wrote: But people aren't going to be thinking about governing TLPs when making assumptions about a name. Does this project actually relate to Lucene or not? Apache Connectors Framework tells me it is either a generic connectors framework for connecting anything to anything, or it is for connecting httpd to something else, neither of which I suspect are what it is all about. Exactly. If the name is going to change (which sounds like a good idea) I'd suggest going for something more abstract, to which you can give meaning: Apache Connecto, or some such. +1 from me too. p Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org 0x62590808.asc - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
So, how does this get resolved? Shall I call a formal vote for the IPMC? I rather like the name, but (somewhat) understand the objections. That being said, I'm not all that clever at naming, so... On Aug 25, 2010, at 7:42 AM, Upayavira wrote: On Wed, 2010-08-25 at 06:49 -0400, Grant Ingersoll wrote: Sure would have been nice if these objections (other than David's) would have been brought up last week before we went and changed everything (after waiting several days for feedback) b/c we were working under the assumption that no one thought it was a problem. At any rate, we'll go discuss. I apologise for that. Unfortunately it was (for me) one of those situations when it takes a resonable volume of mail before it attracts my attention enough to read what is being said. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
On Aug 21, 2010, at 6:30 AM, Pid * wrote: Isn't there a risk of causing confusion with the Apache HTTPD mod_jk / Tomcat Connector? Looks pretty distinct to me. p On 18 Aug 2010, at 16:17, Grant Ingersoll gsing...@apache.org wrote: Do you think this requires a formal IPMC vote or can we just do it? Thankfully, I think most of our mailing lists, etc. are already generic, so we shouldn't really need to change much in terms of branding other than the primary website. On Aug 16, 2010, at 7:49 PM, Noel J. Bergman wrote: Grant Ingersoll wrote: The Lucene Connectors Framework committers are voting to rename our project from Lucene Connectors Framework to Apache Connectors Framework, and to cease being a subproject of Lucene. What is the process for doing something like this? LCF is not a subproject of Lucene at the moment, since it is in the Incubator. Nothing else project wise would change other than the name at this point. Unless there is an objection, I don't see a problem. Nothing in Apache Connectors Framework smacks of a possible trademark issue. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
Do you think this requires a formal IPMC vote or can we just do it? Thankfully, I think most of our mailing lists, etc. are already generic, so we shouldn't really need to change much in terms of branding other than the primary website. On Aug 16, 2010, at 7:49 PM, Noel J. Bergman wrote: Grant Ingersoll wrote: The Lucene Connectors Framework committers are voting to rename our project from Lucene Connectors Framework to Apache Connectors Framework, and to cease being a subproject of Lucene. What is the process for doing something like this? LCF is not a subproject of Lucene at the moment, since it is in the Incubator. Nothing else project wise would change other than the name at this point. Unless there is an objection, I don't see a problem. Nothing in Apache Connectors Framework smacks of a possible trademark issue. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Name change from Lucene Connectors Framework to Apache Connectors Framework
On Aug 16, 2010, at 9:59 AM, karl.wri...@nokia.com karl.wri...@nokia.com wrote: Hi, The Lucene Connectors Framework committers are voting to rename our project from Lucene Connectors Framework to Apache Connectors Framework, and to cease being a subproject of Lucene. What is the process for doing something like this? Just to clarify, LCF is not a subproject of Lucene at the moment, since it is in the Incubator. The Lucene PMC was sponsoring LCF and is willing to continue to do so. Nothing else project wise would change other than the name at this point. Upon graduation, it likely make sense for LCF/ACF to be a TLP. -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator Board Report June 2010
was accepted into the incubator on 11 May 2010. Status information is available at http://incubator.apache.org/projects/whirr.html. Progress since entry into the incubator: All the initial Incubator infrastructure items are now complete. The code hosted in the Hadoop contrib area has been moved to Whirr's subversion tree. Associated JIRAs have been moved to Whirr's JIRA. Plans for the next period: * Import the Whirr Java source Top three items to resolve before graduation: * Increase community involvement in the project * Make several incubating releases * Support at least three services on Whirr Any Issues that the Incubator PMC (IPMC) or ASF Board need to be aware of? None at this time. = Zeta Components = Zeta Components is a high-quality library of loosely-coupled PHP components. It has entered incubation on 2010-05-21. Therefore the project is still in ramp up phase. 3 most important issues to be tackled: * Create initial incubating infrastructure. * Move project and community to ASF. * Get developement based in ASF moving again. Mailing lists have already been created. Available are: * dev zeta-...@incubator.apache.org * user zeta-comm...@incubator.apache.org * commits zeta-us...@incubator.apache.org * private zeta-priv...@incubator.apache.org Website space has been reserved. Jira has been requested. All CLAs have been sent. Most of them have been processed and therefore most user accounts have been requested. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Grant Ingersoll http://www.lucidimagination.com/ Search the Lucene ecosystem using Solr/Lucene: http://www.lucidimagination.com/search - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Anyone using ASF software in bio-informatics?
Lucene is used in a number of places for bio-informatics. Hadoop as well and I've heard rumors of Mahout as well. I can send pointers here or offline and also have some contacts if you'd like. -Grant On Mar 10, 2010, at 4:55 AM, Ross Gardler wrote: I've been invited to keynote at the Open bio-informatics conference in July, wearing my ASF hat. their invite said: Is anyone here using ASF software in this space? Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Anyone using ASF software in bio-informatics?
For starters: Lucene: http://gmod.org/wiki/Lucegene/ I also know of several big Pharma companies using it, but can't say names. You can likely guess, as they are instantly recognizable global brands. TREC Genomics focused on info retrieval on genome data. Lucene is used by NIST to setup the relevance pool, etc. I know many people that use it to search PubMed and the like and then correlate it with outputs from internal documents/experiments/etc. Hadoop One I saw: http://www.slideshare.net/cloudera/hw09-hadoop-for-bioinfomatics I'm sure others in the Hadoop community can name some more. I recall seeing some others go by my radar, but don't see URLs. These days, when your talking TBs of data for a single sequencing run (or others), you need large scale data crunching capabilities Mahout I'd ask on mahout-u...@lucene.a.o. Nothing comes to mind, but we have a lot of lurkers there, so it might hit home. Mahout is a very likely candidate for this kind of work. Some basic searching for Lucene genetics, etc. will lead you to a good deal of results. HTH, Grant On Mar 10, 2010, at 10:35 AM, Mattmann, Chris A (388J) wrote: Hey Grant, Here here on that. Some of the same systems we use OODT on use Lucene as well, I'd be happy to provide some feedback, let me know. Cheers, Chris On 3/10/10 7:18 AM, Grant Ingersoll gsing...@apache.org wrote: Lucene is used in a number of places for bio-informatics. Hadoop as well and I've heard rumors of Mahout as well. I can send pointers here or offline and also have some contacts if you'd like. -Grant On Mar 10, 2010, at 4:55 AM, Ross Gardler wrote: I've been invited to keynote at the Open bio-informatics conference in July, wearing my ASF hat. their invite said: Is anyone here using ASF software in this space? Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Droid IP clearance?
I'm not involved anymore, but that strikes me as really weird given that Droids started in Labs and was wholly developed there before going to Incubator. On Feb 17, 2010, at 4:33 PM, Doug Cutting wrote: Incubator PMC, On reading this month's report to the Board from the Incubator, the Board was curious what, if anything, is blocking Droid's IP clearance process and requested that I look into this. Is someone actively pursuing this? If so, are there any difficulties in obtaining the clearance? Thanks! Doug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833409#action_12833409 ] Grant Ingersoll commented on INCUBATOR-106: --- The IP Clearance vote has passed: 82cc9b39-ba44-42da-a95d-cdd391cd5...@apache.org on gene...@incubator.apache.org. This should be good to commit to the appropriate place in SVN. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP Clearance] MetaCarta Software Grant for Lucene Connector Framework
Lazy consensus implies this has passed. On Feb 10, 2010, at 9:14 AM, Grant Ingersoll wrote: Please review and vote (lazy consensus) on accepting the MetaCarta Software grant as per the description in https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/connectors-metacarta.xml +1 from me. Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833426#action_12833426 ] Grant Ingersoll commented on INCUBATOR-106: --- I'd just unzip it in trunk and hit SVN add and then commit. Then apply patches from there. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831987#action_12831987 ] Grant Ingersoll commented on INCUBATOR-106: --- Couple of notes just to follow up here: Postgres is BSD so it is fine to include. LGPL dependencies are optional and may not be included in the distribution. We should look to replace over time. We may not need the Sun libs, but I believe those are all included by other ASF projects, so they should be fine MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831999#action_12831999 ] Grant Ingersoll commented on INCUBATOR-106: --- That's fine, it pretty much falls in with the libs that one needs for Documentum, etc. We can't redistribute them. In this case, though, it is dead simple to automate the downloading of it via Ant (or Maven) so the user will still be able to build it. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832004#action_12832004 ] Grant Ingersoll commented on INCUBATOR-106: --- Might also look at http://commons.apache.org/vfs/filesystems.html, as there seems to be some work there on a CIFS implementation. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] MetaCarta Software Grant for Lucene Connector Framework
Please review and vote (lazy consensus) on accepting the MetaCarta Software grant as per the description in https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/connectors-metacarta.xml +1 from me. Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830220#action_12830220 ] Grant Ingersoll commented on INCUBATOR-106: --- I'm still showing a lot of files w/o licenses that should be licensed. Let me upload a simple build script that you can use to help determine the files. You'll need to get RAT: http://incubator.apache.org/rat/ and copy over the two JAR files to your ANT lib directory: apache-rat-0.7-SNAPSHOT.jar and apache-rat-tasks-0.7-SNAPSHOT.jar Then, you can copy the build.xml file to a root directory containing the untarred files and run ant rat-sources MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Updated: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated INCUBATOR-106: -- Attachment: build.xml simple rat-sources target for checking license files MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830243#action_12830243 ] Grant Ingersoll commented on INCUBATOR-106: --- Looks like the main issues are in the JSP files and a few other Java files MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[
https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830250#action_12830250
]
Grant Ingersoll commented on INCUBATOR-106:
---
Here's what my output looks like:
{quote}
188 Unknown Licenses
[rat:report]
[rat:report] ***
[rat:report]
[rat:report] Unapproved licenses:
[rat:report]
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/mcsqa/tests/meridio-testing-package/com/metacarta/crawler/connectors/meridio/meridiowrapper/MeridioTestWrapper.java
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/commands/Makefile.am
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/viewspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-agents-base-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-agents-incr-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-tomcat-base-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-tomcat-incr-size
{quote}
I doubt the *-size files need to be modified, but the jsp files should be.
MetaCarta Lucene Connector Framework code grant
---
Key: INCUBATOR-106
URL: https://issues.apache.org/jira/browse/INCUBATOR-106
Project: Incubator
Issue Type: New Feature
Reporter: Karl Wright
Assignee: Grant Ingersoll
Attachments: apache-lcf-software-grant.tar.gz,
apache-lcf-software-grant.tar.gz, build.xml
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep
coreutils
ii coreutils 6.10-6
The GNU core utilities
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum
apache-lcf-software-grant.tar.gz
1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$
--
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: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Issue Comment Edited: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[
https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830250#action_12830250
]
Grant Ingersoll edited comment on INCUBATOR-106 at 2/5/10 7:39 PM:
---
Here's what my output looks like:
{quote}
188 Unknown Licenses
[rat:report]
[rat:report] ***
[rat:report]
[rat:report] Unapproved licenses:
[rat:report]
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/mcsqa/tests/meridio-testing-package/com/metacarta/crawler/connectors/meridio/meridiowrapper/MeridioTestWrapper.java
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/commands/Makefile.am
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/viewspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-agents-base-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-agents-incr-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-tomcat-base-size
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/documentumconnector-tomcat-incr-size
{quote}
I doubt the *-size files need to be modified, but the jsp files should be as
well as a few Java stragglers. We're getting there.
was (Author: gsingers):
Here's what my output looks like:
{quote}
188 Unknown Licenses
[rat:report]
[rat:report] ***
[rat:report]
[rat:report] Unapproved licenses:
[rat:report]
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/mcsqa/tests/meridio-testing-package/com/metacarta/crawler/connectors/meridio/meridiowrapper/MeridioTestWrapper.java
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/authorities/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/commands/Makefile.am
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/editspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/headerspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/postspec.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM/viewconfig.jsp
[rat:report]
/Users/grantingersoll/projects/lucene/lcf/grant/products/connectors/documentum/connectors/DCTM
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830257#action_12830257 ] Grant Ingersoll commented on INCUBATOR-106: --- What happened to all the dependencies? The Makefiles seem to indicate they exist, but is expecting them in /usr/share/java.Will these need to be available in order to compile/build? MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830261#action_12830261 ] Grant Ingersoll commented on INCUBATOR-106: --- In other words, we will need to check them in, which means we need to know what they are now to see if they can be checked in. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[
https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12830265#action_12830265
]
Grant Ingersoll commented on INCUBATOR-106:
---
These are the two remaining questions:
{quote}
tr
td-..-../td
tdCheck and make sure that for all items included with the
distribution that is not under the Apache license, we have
the right to combine with Apache-licensed code and
redistribute./td
/tr
tr
td-..-../td
tdCheck and make sure that all items depended upon by the
project is covered by one or more of the following approved
licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or
something with essentially the same terms./td
/tr
{quote}
MetaCarta Lucene Connector Framework code grant
---
Key: INCUBATOR-106
URL: https://issues.apache.org/jira/browse/INCUBATOR-106
Project: Incubator
Issue Type: New Feature
Reporter: Karl Wright
Assignee: Grant Ingersoll
Attachments: apache-lcf-software-grant.tar.gz,
apache-lcf-software-grant.tar.gz, build.xml
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep
coreutils
ii coreutils 6.10-6
The GNU core utilities
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum
apache-lcf-software-grant.tar.gz
1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz
kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$
--
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: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829099#action_12829099 ] Grant Ingersoll commented on INCUBATOR-106: --- Hi Karl, Can you go through and add ASF license headers to all text-based files that can be modified to accept comments? I see a lot of python files, etc. that don't have headers. This used to be not such a big deal and could have been resolved at commit time, but due to some other projects having copyright/license issues, we'd like to make sure they all are properly licensed in the donation. Thanks, Grant MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829106#action_12829106 ] Grant Ingersoll commented on INCUBATOR-106: --- OK. Just so you don't have to go back more than once, here's the form I need to fill out: http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml And here is my start on it: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/connectors-metacarta.xml So, we need to do whatever is appropriate to be able to satisfy all of those elements. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829111#action_12829111 ] Grant Ingersoll commented on INCUBATOR-106: --- For files that would be broken (i.e. binary, diffs, etc.), no need for the header. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12828128#action_12828128 ] Grant Ingersoll commented on INCUBATOR-106: --- Note, before this can be committed, we'll need to add ASL headers to lots of files (python files, etc.). No need to do just yet, I don't think, but am checking with others at the incubator. MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
IP Clearance Question
The IP Clearance form says: Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. What exactly is the new ASF copyright? Is it our standard license header? Is it really a requirement of a grant before it's even committed? Can't this be something done during committing the code in question or before release? -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Assigned: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned INCUBATOR-106: - Assignee: Grant Ingersoll MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
On Jan 12, 2010, at 1:47 PM, Alan D. Cabrera wrote: On Jan 12, 2010, at 7:27 AM, Grant Ingersoll wrote: On Jan 12, 2010, at 10:12 AM, Emmanuel LŽcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. Just curious, if there's no Hadoop tech in the project then why have it sponsored by Hadoop? I'd add, I think most in Hadoop land view Hadoop as one of the primary places for large scale distributed computing at Apache. Map Reduce is one approach and it does not fit all situations, so I think you'll see other things arise there, possibly JPPF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Lucene Connector Framework Kickoff
On Jan 12, 2010, at 5:55 AM, Karl Wright wrote: Hi Grant, For those of us new to working with apache, could you give a quick overview of the best way to communicate among group members? Specifically, what sorts of posts should be sent to gene...@incubator, and what sorts should go to gene...@lucene? We should have the connectors mailing list in a few days or less, at which point we can use those. For now, we should use gene...@incubator.apache.org. I CC'd gene...@lucene.a.o so that people who are in the Lucene community who don't subscribe to incubator would be aware. Also, I am in the process of determining the strategy and the exact list of files for the software grant from MetaCarta, and I'd love to get people's feedback as to what should be included, and how. What list would be appropriate for that? Should we set one up? connectors-...@incubator.a.o will be the place for this. -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? On Jan 12, 2010, at 7:24 AM, Emmanuel Lecharny wrote: Hi guys, On behalf of the JPPF community, I'd like to bring the following proposal for discussion within the Incubator. I had a meeting with Laurent last week when he investigated about using MINA into JPPF, and I suggested that this project could be a good fit for the Incubator. We will need mentors for this proposal WDYT ? Thanks! http://wiki.apache.org/incubator/JppfProposal --- Current Wiki Text below --- = JPPF : a parallel processing framework for Java = === Abstract === JPPF enables applications with large processing power requirements to be run on any number of computers, in order to dramatically reduce their processing time. This is done by splitting an application into smaller parts that can be executed simultaneously on different machines. === Proposal === JPPF aims at facilitating the parallelization of computation-intensive applications, with a focus on ease of use, performance and reliability. To achieve these goals, the framework comes with a number of outstanding features: - Comprehensive, easy to use APIs: passing from a single-threaded application model to a grid-based parallel model can be a daunting task. JPPF facilitates this work by providing developers with a set of APIs that are simple, can be learned quickly and require a minimal or no modification to the existing code. - No configuration usage: in most environments, JPPF can be deployed without any additional configuration burden. Nodes and application clients will automatically dicover the servers on the network. The server will automatically adapt to workload changes and optimize the throughput. Required code and libraries will be automatically deployed where they are needed. - Dynamic grid scaling and self-repair: the JPPF grid is fault-tolerant, meaning that the failure of a node, or even a server, does not compromise the jobs currently executing or scheduled. In most cases, the performance degradation will be barely noticeable, as JPPF automatically adapts to topology and workload changes. Furthermore, nodes and servers can be dynamically started and will be automatically recognized, allowing JPPF to function in crunch mode. In addition to this, JPPF components benefit from automatic recovery functionalities. - Job-level SLA: each job submitted to the JPPF grid runs within limits defined by its own SLA (service level agreement). This allows to specify the characteristics (i.e. available memory, processors, disk space, operating systems, etc.) of the nodes a job can run on, as well as how many nodes it can run on. As many functionalities in JPPF, this one can be dynamically adjusted, manually or automatically. - Advanced Management and monitoring: full-fledged management and monitoring features are provided out of the box: server and nodes status monitoring, detailed statistics and events, remote administration, job-level real-time monitoring and management, charts, cpu utilization (for billing). These functionalities are available via a graphical user interface as well as from the JPPF APIs. - Integration with leading application and web servers: by complying with the Java Connector Architecture 1.5 specification, JPPF integrates seamlessly with and completes the offering of leading J2EE application servers: Apache Geronimo, JBoss, Glassfish, IBM Websphere, Oracle Weblogic, Oracle OC4J. JPPF also integrates with GigaSpaces eXtreme Application Platform and Apache Tomcat web server - Extensibility: JPPF offers a number of hooks and extension points that allow users to extend the framework and adapt it to their own requirements and needs. Such extension mechanisms are available for custom management and monitoring MBeans, startup classes for grod components, network data transformation/encryption, additional load-balancing algorithms, alternate object serialization mechanisms. === Background === JPPF is a project being actively developed at SourceForge. It was created to address a class of problems called embarassingly parallel, which groups computational problems that can be decomposed into many smaller sub-problems, that are independant from each other and that can thus be executed in parallel. === Rationale === Given these last years' emergence of technologies that make commodity hardware, virtualization and cloud computing available to a fast-growing computing ecosystem, the project answers the need to execute applications ever faster, with a low entry cost, while at the same time preserving historical technological investments. == Current Status == === Meritocracy === MWe acknowledge that a meritocratic governance is the only way for the project to grow and expand, in the spirit of open source and the ASF. It will benefit the project, its communities, the
Re: Lucene Connector Framework Kickoff
FYI: I've started putting together a basic site w/ the same skin as most of the other Lucene sites, but w/ Incubator branding. On Jan 11, 2010, at 5:40 PM, Grant Ingersoll wrote: Hi All, (Please keep replies to general@incubator.apache.org) I opened the following JIRA issues for starting LCF: https://issues.apache.org/jira/browse/INFRA-2431 I need two volunteers from the list of committers to be moderators. Please signify your willingness to be a committer by adding your name to the JIRA ticket. Confluence Wiki: https://issues.apache.org/jira/browse/INFRA-2432 JIRA project https://issues.apache.org/jira/browse/INFRA-2433 I added SVN at: https://svn.apache.org/repos/asf/incubator/lcf/ The following people need to submit iCLAs: Brian Pinkerton Karl Wright (kwright at metacarta) Josiah Strandberg (jstrandberg at metacarta) Ken Baker (bakerkj at metacarta) Marc Meadows (mam at metacarta) Once they are on file, I can request accounts. Everyone else should have permission to commit, as they are existing committers. Cheers, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
On Jan 12, 2010, at 10:12 AM, Emmanuel Lcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Incubate Lucene Connector Framework
I believe this has passed. Any pointers on next steps would be welcome, otherwise, I will go RTM. On Jan 8, 2010, at 11:32 AM, Jukka Zitting wrote: Hi, On Fri, Jan 8, 2010 at 3:51 PM, Grant Ingersoll gsing...@apache.org wrote: On behalf of the Lucene PMC, I'd like to propose incubation for a new Lucene subproject called the Lucene Connector Framework (LCF). [x] +1. Accept LCF into the Incubator. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Lucene Connector Framework Kickoff
Hi All, (Please keep replies to general@incubator.apache.org) I opened the following JIRA issues for starting LCF: https://issues.apache.org/jira/browse/INFRA-2431 I need two volunteers from the list of committers to be moderators. Please signify your willingness to be a committer by adding your name to the JIRA ticket. Confluence Wiki: https://issues.apache.org/jira/browse/INFRA-2432 JIRA project https://issues.apache.org/jira/browse/INFRA-2433 I added SVN at: https://svn.apache.org/repos/asf/incubator/lcf/ The following people need to submit iCLAs: Brian Pinkerton Karl Wright (kwright at metacarta) Josiah Strandberg (jstrandberg at metacarta) Ken Baker (bakerkj at metacarta) Marc Meadows (mam at metacarta) Once they are on file, I can request accounts. Everyone else should have permission to commit, as they are existing committers. Cheers, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Incubate Lucene Connector Framework
Hi, Given the lack of response on the proposal, I'll assume lazy consensus and call a vote. On behalf of the Lucene PMC, I'd like to propose incubation for a new Lucene subproject called the Lucene Connector Framework (LCF). I think we have all the necessary bits in place for the proposal to go forward. Proposal: http://wiki.apache.org/incubator/LuceneConnectorFrameworkProposal [] +1. Accept LCF into the Incubator. [] 0. Don't care. [] -1. Do not accept (and why.) Here's my +1. Thanks, Grant Ingersoll -- Wiki Text Copied Below - Lucene Connector Framework Abstract Many, many search engines, as well as other applications, have a need to connect with content repositories (SharePoint, CMS, Documentum, etc.) in a standard manner. The Lucene Connector Framework (LCF) is a project aimed at building out these connectors in open source under the Apache brand. Proposal The goal of LCF is to create a viable Lucene subproject aimed at delivering a best of breed connector framework under the Apache Lucene name. As a framework, the project will not only provide a way to connect to individual repositories, but also a mechanism for plugging in new connectors or custom connectors in a straightforward manner. A connector framework is vital for search engines and other tools that need to access data located in corporate repositories. By abstracting the problem into a framework, applications can code to a set of well-defined interfaces instead of having to use a different interface for each connector. Connector Framework is an extendible incremental crawler, which uses a database to manage configuration and crawl history, and provides reasonably high performance in accessing content in multiple repositories for the main purpose of search engine indexing. Connector Framework also establishes a repository-specific security model which can be used to limit search user access to repository content based on a user's identity. Connector Framework also includes existing connectors and authorities for: • File system • Windows shares • JDBC-supported databases • RSS feeds • General websites • LiveLink [from OpenText] • Documentum [from EMC] • SharePoint [from Microsoft] • Meridio [from Meridio] • Memex [from Memex] • FileNet [from IBM] Key design points for Connector Framework are as follows: • Extendability - you can add new connectors for new repositories, and new authorities for specific repository security models • Incrementality - the ability to process only what changed between crawls, in a repository-specific manner • Restartability - using a database with ACID properties to insure that crawls are safe against process interruption or machine shutdown • Security - establishing a model of security tokens that allows a search engine to enforce a repository's security model • Limited footprint - ability to operate reliably within a fixed amount of process memory, regardless of configuration • Performance - management of connector-specific resources to maximize overall thoughput • Transparency - ability to generate reports on the activity of all crawls and repository connections Background MetaCarta originally approached Grant Ingersoll from the Lucene PMC about donating their existing connector framework to the Lucene PMC. After some discussion about accepting it as a software grant, the PMC decided it would be best to incubate the project first. Rationale The Connector Framework fills an often significant gap in the Lucene experience, namely, how to get content locked away in a content repository into Lucene/Solr/Nutch/Mahout/Tika. Naturally, many other tools (search engines and others) will also have this same problem. A Connector Framework would also be useful for someone wishing to migrate between content repositories, too. Current Status Connector Framework has been under development and in use in the field for close to five years, deployed on a MetaCarta search appliance. Almost all development of the project has been done by Karl Wright ( kwri...@metacarta.com ). Some individual connectors were developed initially by contractors hired by MetaCarta, Inc., but maintenance and further development is currently handled by the MetaCarta team. Development of Connector Framework can therefore be viewed as core framework development, plus development of individual connectors. Core framework development is currently not a terribly collaborative process, as there are no maintainers of the core functionality other than Mr. Wright. Development of new connectors has been done in the past in a much more collaborative way by supplying a developer with a development kit, and then integrating the resulting connector (with whatever changes might have been necessary) into the source tree. Reasonable efforts have been made to maintain the generality of the code base during the time that MetaCarta has owned it. Nevertheless, certain MetaCarta-specific changes have been made which may require review
[PROPOSAL] Lucene Connector Framework
Hi, On behalf of the Lucene PMC, I'd like to propose incubation for a new Lucene subproject called the Lucene Connector Framework. I think we have all the necessary bits in place for the proposal to go forward, but would appreciate any discussion/questions. Thanks, Grant Ingersoll Proposal: http://wiki.apache.org/incubator/LuceneConnectorFrameworkProposal -- Wiki Text Copied Below - Lucene Connector Framework Abstract Many, many search engines, as well as other applications, have a need to connect with content repositories (SharePoint, CMS, Documentum, etc.) in a standard manner. The Lucene Connector Framework (LCF) is a project aimed at building out these connectors in open source under the Apache brand. Proposal The goal of LCF is to create a viable Lucene subproject aimed at delivering a best of breed connector framework under the Apache Lucene name. As a framework, the project will not only provide a way to connect to individual repositories, but also a mechanism for plugging in new connectors or custom connectors in a straightforward manner. A connector framework is vital for search engines and other tools that need to access data located in corporate repositories. By abstracting the problem into a framework, applications can code to a set of well-defined interfaces instead of having to use a different interface for each connector. Connector Framework is an extendible incremental crawler, which uses a database to manage configuration and crawl history, and provides reasonably high performance in accessing content in multiple repositories for the main purpose of search engine indexing. Connector Framework also establishes a repository-specific security model which can be used to limit search user access to repository content based on a user's identity. Connector Framework also includes existing connectors and authorities for: • File system • Windows shares • JDBC-supported databases • RSS feeds • General websites • LiveLink [from OpenText] • Documentum [from EMC] • SharePoint [from Microsoft] • Meridio [from Meridio] • Memex [from Memex] • FileNet [from IBM] Key design points for Connector Framework are as follows: • Extendability - you can add new connectors for new repositories, and new authorities for specific repository security models • Incrementality - the ability to process only what changed between crawls, in a repository-specific manner • Restartability - using a database with ACID properties to insure that crawls are safe against process interruption or machine shutdown • Security - establishing a model of security tokens that allows a search engine to enforce a repository's security model • Limited footprint - ability to operate reliably within a fixed amount of process memory, regardless of configuration • Performance - management of connector-specific resources to maximize overall thoughput • Transparency - ability to generate reports on the activity of all crawls and repository connections Background MetaCarta originally approached Grant Ingersoll from the Lucene PMC about donating their existing connector framework to the Lucene PMC. After some discussion about accepting it as a software grant, the PMC decided it would be best to incubate the project first. Rationale The Connector Framework fills an often significant gap in the Lucene experience, namely, how to get content locked away in a content repository into Lucene/Solr/Nutch/Mahout/Tika. Naturally, many other tools (search engines and others) will also have this same problem. A Connector Framework would also be useful for someone wishing to migrate between content repositories, too. Current Status Connector Framework has been under development and in use in the field for close to five years, deployed on a MetaCarta search appliance. Almost all development of the project has been done by Karl Wright ( kwri...@metacarta.com ). Some individual connectors were developed initially by contractors hired by MetaCarta, Inc., but maintenance and further development is currently handled by the MetaCarta team. Development of Connector Framework can therefore be viewed as core framework development, plus development of individual connectors. Core framework development is currently not a terribly collaborative process, as there are no maintainers of the core functionality other than Mr. Wright. Development of new connectors has been done in the past in a much more collaborative way by supplying a developer with a development kit, and then integrating the resulting connector (with whatever changes might have been necessary) into the source tree. Reasonable efforts have been made to maintain the generality of the code base during the time that MetaCarta has owned it. Nevertheless, certain MetaCarta-specific changes have
Re: Incubator PMC/Board report for January 2010 (Lucene.Net Developers general@incubator.apache.org)
Hasn't Lucene.Net officially graduated or am I misinformed? On Jan 1, 2010, at 9:00 AM, Marvin wrote: Dear Lucene.Net Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Lucene Connector Framework Proposal - Looking for one more mentor
Hi, The Lucene PMC is looking for one more mentor for a new project we hope to incubate based on some initial code from MetaCarta called the Lucene ConnectorFramework. Most of the details are in http://wiki.apache.org/incubator/LuceneConnectorFrameworkProposal, but we're not quite done there yet to call a vote. One of the things we are missing is one last mentor, so I thought I'd reach out to the community and see if anyone is willing to step up and help mentor. Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] Clearance for IBM Query Parser Software Grant
Please review and provide lazy consensus for IBM's Query Parser Software Grant at https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/lucene-query-parser.xml and https://issues.apache.org/jira/browse/LUCENE-1567 Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP Clearance] Clearance for IBM Query Parser Software Grant
On Jul 21, 2009, at 9:55 AM, Robert Burrell Donkin wrote: On Tue, Jul 21, 2009 at 1:46 PM, Grant Ingersollgsing...@apache.org wrote: Please review and provide lazy consensus for IBM's Query Parser Software Grant at https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/lucene-query-parser.xml there seem to be a number of june dates (eg 2009-06-16) are these typos? (or has it just taken a while...?) It has taken a while... I tried to keep track of things as I did them. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Resolved: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved INCUBATOR-103. --- Resolution: Fixed [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP-CLEARANCE] PyLucene
OK, this has passed/cleared. Thanks! Grant On Jan 5, 2009, at 10:31 PM, Grant Ingersoll wrote: Please (lazily) vote to accept the PyLucene software grant: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/pylucene.xml See also https://issues.apache.org/jira/browse/INCUBATOR-103 Cheers, Grant Ingersoll - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12662123#action_12662123 ] Grant Ingersoll commented on INCUBATOR-103: --- OK, the clearance has passed. Andi, I've setup the SVN for pylucene and I'll send out an announcement on gene...@lucene.a.o. and you can begin the committing process and setting up the website, etc. You can request mailing lists on infrastructure. Let me know if you need help with that stuff. [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660878#action_12660878 ] Grant Ingersoll commented on INCUBATOR-103: --- OK, great. Then I think we are in good shape. I will finish up the grant and then we can do the last steps for IP Clearance. [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP-CLEARANCE] PyLucene
Please (lazily) vote to accept the PyLucene software grant: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/pylucene.xml See also https://issues.apache.org/jira/browse/INCUBATOR-103 Cheers, Grant Ingersoll - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Assigned: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned INCUBATOR-103: - Assignee: Grant Ingersoll [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660080#action_12660080 ] Grant Ingersoll commented on INCUBATOR-103: --- Craig, Sebb, I guess one question I have is, all of this required before acceptance? It was my understanding that these issues just need to be resolved before release, right? -Grant [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12659892#action_12659892 ] Grant Ingersoll commented on INCUBATOR-103: --- Andi, Can you update the headers to be ASL 2.0? And then upload and regen the files. Thanks, Grant [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- 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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Next steps for droids
On Oct 29, 2008, at 7:16 PM, Thorsten Scherler wrote: On Tue, 2008-10-28 at 07:00 -0400, Grant Ingersoll wrote: Sorry, missed that part. At any rate: svn mv -m Move Droids from labs https://svn.apache.org/repos/asf/labs/droids https://svn.apache.org/repos/asf/incubator Committed revision 708523. Just did a checkout and it looks good. One more thing we need is: ssh people.apache.org cd /www/incubator.apache.org/ mkdir droids chown droids:droids droids However if I am doing groups on people I do not get the droids group but I remembered that you said you have set it up. I don't have that Karma. That would have to be a JIRA infra request, I think. I set up a Droids group in the SVN auth. However, I don't think we need an explicit Droids UNIX group (just look at all the others there) What we need is someone in the incubator group to add the directory. I _think_ all Incubator committers can be in that group, judging by the people who are already in that group. Maybe that's just an INFRA request? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Next steps for droids
Sorry, missed that part. At any rate: svn mv -m Move Droids from labs https://svn.apache.org/repos/asf/labs/droids https://svn.apache.org/repos/asf/incubator Committed revision 708523. Just did a checkout and it looks good. On Oct 28, 2008, at 4:16 AM, Thorsten Scherler wrote: On Mon, 2008-10-27 at 22:28 -0400, Grant Ingersoll wrote: OK, I believe I have toggled the necessary switch in the svn authorization files. I added Thorsten, Ryan, Oleg and me to the droids SVN group and gave permissions to /incubator/droids. I also added the Droids group to incubator/public, which seems to be the model for other projects in Incubator, please correct me if I'm wrong. Thorsten, can you give your mv command a try? I did and actually the result was no surprise: # step 1: move project from labs to incubator [EMAIL PROTECTED]:~$ svn mv https://svn.apache.org/repos/asf/labs/droids https://svn.apache.org/repos/asf/incubator svn: CHECKOUT of '/repos/asf/!svn/ver/708466/incubator': 403 Forbidden (https://svn.apache.org) svn: Your commit message was left in a temporary file: svn:'svn-commit.tmp' I do not have the right to create a new folder in the incubator root. That is why I wrote: (side-note: the following step 1 needs to be done from someone that has write access to the incubator rep) Please can you try and then I will take over again. salu2 On Oct 27, 2008, at 6:31 PM, Thorsten Scherler wrote: On Fri, 2008-10-24 at 08:00 +1100, David Crossley wrote: Grant Ingersoll wrote: Thorsten Scherler wrote: like pointed out in the other mail the next things for droids is to move svn, move the issues and setup the mailing lists. I reckon I will need to write to infrastructure to ask for help, right? Regarding the svn move I would like to ask one of the mentors (Ross, Paul or Grant) do do step 1 of [1] since I do not have sufficient rights to do it myself. TIA. I'm happy to help, but I need some mentoring on being a mentor ;-) I have permission to change the SVN auth stuff, but am not sure if this is outside my authority, since I think I'm only supposed to be responsible for Lucene stuff. Just do whatever you need. The link below refers to some Mentor guidelines. The only missing thing is now to move the svn, then we can set up http://incubator.apache.org/droids. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions Sociedad Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U. (SADESI) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Next steps for droids
OK, I believe I have toggled the necessary switch in the svn authorization files. I added Thorsten, Ryan, Oleg and me to the droids SVN group and gave permissions to /incubator/droids. I also added the Droids group to incubator/public, which seems to be the model for other projects in Incubator, please correct me if I'm wrong. Thorsten, can you give your mv command a try? On Oct 27, 2008, at 6:31 PM, Thorsten Scherler wrote: On Fri, 2008-10-24 at 08:00 +1100, David Crossley wrote: Grant Ingersoll wrote: Thorsten Scherler wrote: like pointed out in the other mail the next things for droids is to move svn, move the issues and setup the mailing lists. I reckon I will need to write to infrastructure to ask for help, right? Regarding the svn move I would like to ask one of the mentors (Ross, Paul or Grant) do do step 1 of [1] since I do not have sufficient rights to do it myself. TIA. I'm happy to help, but I need some mentoring on being a mentor ;-) I have permission to change the SVN auth stuff, but am not sure if this is outside my authority, since I think I'm only supposed to be responsible for Lucene stuff. Just do whatever you need. The link below refers to some Mentor guidelines. The only missing thing is now to move the svn, then we can set up http://incubator.apache.org/droids. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Next steps for droids
On Oct 23, 2008, at 2:50 PM, Thorsten Scherler wrote: Hi all, like pointed out in the other mail the next things for droids is to move svn, move the issues and setup the mailing lists. I reckon I will need to write to infrastructure to ask for help, right? Regarding the svn move I would like to ask one of the mentors (Ross, Paul or Grant) do do step 1 of [1] since I do not have sufficient rights to do it myself. TIA. I'm happy to help, but I need some mentoring on being a mentor ;-) I have permission to change the SVN auth stuff, but am not sure if this is outside my authority, since I think I'm only supposed to be responsible for Lucene stuff. I had a look at http://incubator.apache.org/clutch.html but have to admit I need to have a better look on the latest thread around the clutch tool to see how it works. I reckon as soon we set up the svn the start date will appear. The sponsoring organization are the hc and the lucene project. salu2 [1] http://markmail.org/message/wjlondcr6hkyosmz -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Result] [Vote] accept Droids into incubation
On Oct 15, 2008, at 7:59 AM, Thorsten Scherler wrote: On Tue, 2008-10-14 at 09:00 -0400, Grant Ingersoll wrote: I presume this is passed. I suppose we need to setup mailing lists, JIRA, etc. right? Since we are transferring from labs, is there anyway to import the issues from there? Yeah that would be awesome. Have you seen the latest threads on labs about the move? Any thread in particular? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Result] [Vote] accept Droids into incubation
I presume this is passed. I suppose we need to setup mailing lists, JIRA, etc. right? Since we are transferring from labs, is there anyway to import the issues from there? -Grant On Oct 8, 2008, at 7:34 PM, Jukka Zitting wrote: Hi, On Thu, Oct 9, 2008 at 1:19 AM, Thorsten Scherler [EMAIL PROTECTED] wrote: Can the PMC ACK this result and we'll start the next step of the process? No ACK needed, as it was the Incubator PMC itself who just voted. Regarding the svn move ATM there are two trees under development https://svn.apache.org/repos/asf/labs/droids/trunk https://svn.apache.org/repos/asf/labs/droids/branch/LABS-144/ Where the latest has become kind of trunk. We can merge them if this will ease the work of migrating. I don't think you need anything more complicated than an svn move of labs/droids to incubator/droids. Whether or how you want to merge branches is a project decision that's up to you and the other committers. BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] accept Droids into incubation
only one company is known to use Droids in a productive environment however there is a constant interest in a generic robot framework expressed by various Apache committers. For many potential users the existing tools are to complicated or too much focused on a specific usecase which will help to gain a bigger user base. Once the project gets started we can quickly build the wget style droids to a feature level of existing tools based on plugin development that reuses code from sources mentioned below. After that we believe to be able to quickly grow the developer and user communities based on the benefits of a generic framework offering reusable plugins and different droids over custom alternatives. === Inexperience with Open Source === All the initial developers have worked on open source before and many are committers and PMC members within other Apache projects. === Homogenous Developers === The initial developers come from a variety of backgrounds and with a variety of needs for the proposed toolkit. === Reliance on Salaried Developers === Some of the developers are paid to work develop certain functionality on this, but the proposed project is not the primary task for anyone. === Relationships with Other Apache Products === TBN === A Excessive Fascination with the Apache Brand === All of us are familiar with Apache and we have participated in Apache projects as contributors, committers, and PMC members. We feel that the Apache Software Foundation is a natural home for a project like this. == Documentation == The main documentation is distributed with the code * [http://svn.apache.org/viewvc/labs/droids/trunk/docs/ Docu] * [http://people.apache.org/~thorsten/droids/ DocuDeployed] == Initial Source == Droids will start with the code base that have been developed in the Apache Labs project: * [http://svn.apache.org/viewvc/labs/droids/trunk/ code base] == Source and Intellectual Property Submission Plan == All seed code and other contributions will be handled through the normal Apache contribution process. We will also contact other related efforts for possible cooperation and contributions. == External Dependencies == Droids will mainly depend on the Spring core distribution. == Cryptography == Droids itself will not use cryptography, but it is possible that some of the external libraries will include cryptographic code to handle different features. == Required Resources == Mailing lists * [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] Subversion Directory * https://svn.apache.org/repos/asf/incubator/droids Issue Tracking * JIRA Droids (DROIDS) Other Resources * none == Initial Committers == || '''Name''' || '''Email''' || '''CLA'''|| || Thorsten Scherler || thorsten at apache dot org|| yes || || Ryan !McKinley || ryan at apache dot org|| yes || || Grant Ingersoll || gsingers at apache dot org || yes || || Oleg Kalnichevski || olegk at apache dot org|| yes || == Affiliations == || '''Name'''|| '''Affiliation''' || || Thorsten Scherler || Freelancer || == Sponsors == Champion Grant Ingersoll Nominated Mentors * Ross Gardler rgardler at apache dot org * Paul Fremantle pzf at apache dot org * Grant Ingersoll gsingers at a.o Sponsoring Entity * [http://hc.apache.org/ Apache HttpComponents] * [http://lucene.apache.org/ Apache Lucene] -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Droids
FYI, I have sent my request to join the PMC. I will add my name to the Mentor list, which should give us three. On Sep 26, 2008, at 6:42 AM, Thorsten Scherler wrote: On Fri, 2008-09-26 at 16:39 +0800, Niclas Hedhman wrote: On Fri, Sep 26, 2008 at 4:25 PM, Thorsten Scherler [EMAIL PROTECTED] wrote: ...All Mentors must be members of the Incubator PMC http://incubator.apache.org/whoweare.html Grant is not on this page, trying to say Grant cannot be mentor as I understand the rules, or do I miss something? Correct. But IIRC, Grant is a ASF Member and can therefor just send a request to join the PMC. Ah, cheers for the clarification. :) salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Droids
Looks like we need one more mentor. Is it redundant to put myself as one since I'm already the champion and a listed committer? On Sep 22, 2008, at 4:24 PM, Thorsten Scherler wrote: This is a proposal to enter the incubator. See http://wiki.apache.org/incubator/DroidsProposal for the most up-to-date version. As Champion we have Grant Ingersoll gsingers at apache dot org from the ASF. Droids is an Apache Labs project and we are still looking for some mentors for this proposal. We look forward to comments and discussion. = Droids, an intelligent standalone robot framework = === Abstract === Droids aims to be an intelligent standalone robot framework that allows to create and extend existing droids (robots). === Proposal === As a standalone robot framework Droids will offer infrastructure code to create and extend existing robots. In the future it will offer as well a web based administration application to manage and controll the different droids which will communicate with this app. Droids makes it very easy to extend existing robots or write a new one from scratch, which can automatically seek out relevant online information based on the user's specifications. Since the flexible design it can reuse directly all custom business logic that are written in java. In the long run it should become umbrella for specialized droids that are hosted as sub-projects. Where an ultimate goal is to integrate an artificial intelligence that can control a swarm of droids and actively plan/react on different tasks. === Background === The initial idea for the Droids project was voiced in February 2007 from Thorsten Scherler mainly because of personal curiosity and developed as a labs project. The background of his work was that Cocoon trunk (2.2) did not provide a crawler anymore and Forrest was based on it, meaning we could not update anymore till we found a crawler replacement. Getting more involved in Solr and Nutch he saw the request for a generic standalone crawler. For the first version he took nutch, ripped out and modified the plugin/extension framework. However the second version were not based on it anymore but was using Spring instead. The main reason was that Spring has become a standard and helped to make Droids as extensible as possible. Soon the first plugins and sample droids had been added to the code based. === Rationale === There is ever more demand for tools that automatically do determinate tasks. Search engines such as Nuts are normally very focused on a specific functionality and are not focused on extensibility. Furthermore there are manly focused on crawling, requesting certain pages and extract links to other pages, which in our opinion is only one small area for automated robots. While there are a number of existing crawler libraries for various task, each of them comes with a custom API and there are no generic interface for automatically determining which crawler (droids) to use for a specific task. The Droids project attempts to remove this duplication of efforts. We believe that by pooling the efforts of multiple projects we will be able to create a generic robot framework that exceeds the capabilities and quality of the custom solutions of any single project. The focus of Droids is not a single crawler but more to offer different reusable components that custom droids (robots) can use to automate certain tasks. An intelligent standalone robot framework project will not only provide common ground for the developers of crawler but as well for any other automated application (robots) libraries. === Initial Goals === The initial goals of the proposed project are: * Viable community around the Droids codebase * Active relationships and possible cooperation with related projects and communities (e.g. reusing Tika for text extraction) * Generic robot API for crawling, extracting structured text content and/or new task, filtering task and handle the content * Flexible extension and plugin development to create a wide range of functionality * Fuel develop of various droids and bring the current wget style crawler to state-of-the-art level == Current Status == === Meritocracy === All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source codebases. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is not yet a clear Droids community. Instead we have a number of people and related projects with an understanding that an intelligent standalone robot framework project would best serve everyone's interests. The primary goal of the incubating project is to build a self-sustaining community around this shared vision. === Core Developers === The initial set of developers comes from various backgrounds, with different but compatible needs for the proposed project. === Alignment === As a generic robot
Re: [PROPOSAL] Droids
So, I'm new to championing (but read the brief docs on the proposal guide). One question I have is related to the Sponsoring PMC. The proposal indicates two Sponsoring Entities. When does that need to be resolved? Or is this going to be a TLP? Or, does it not matter? -Grant On Sep 22, 2008, at 4:24 PM, Thorsten Scherler wrote: This is a proposal to enter the incubator. See http://wiki.apache.org/incubator/DroidsProposal for the most up-to-date version. As Champion we have Grant Ingersoll gsingers at apache dot org from the ASF. Droids is an Apache Labs project and we are still looking for some mentors for this proposal. We look forward to comments and discussion. = Droids, an intelligent standalone robot framework = === Abstract === Droids aims to be an intelligent standalone robot framework that allows to create and extend existing droids (robots). === Proposal === As a standalone robot framework Droids will offer infrastructure code to create and extend existing robots. In the future it will offer as well a web based administration application to manage and controll the different droids which will communicate with this app. Droids makes it very easy to extend existing robots or write a new one from scratch, which can automatically seek out relevant online information based on the user's specifications. Since the flexible design it can reuse directly all custom business logic that are written in java. In the long run it should become umbrella for specialized droids that are hosted as sub-projects. Where an ultimate goal is to integrate an artificial intelligence that can control a swarm of droids and actively plan/react on different tasks. === Background === The initial idea for the Droids project was voiced in February 2007 from Thorsten Scherler mainly because of personal curiosity and developed as a labs project. The background of his work was that Cocoon trunk (2.2) did not provide a crawler anymore and Forrest was based on it, meaning we could not update anymore till we found a crawler replacement. Getting more involved in Solr and Nutch he saw the request for a generic standalone crawler. For the first version he took nutch, ripped out and modified the plugin/extension framework. However the second version were not based on it anymore but was using Spring instead. The main reason was that Spring has become a standard and helped to make Droids as extensible as possible. Soon the first plugins and sample droids had been added to the code based. === Rationale === There is ever more demand for tools that automatically do determinate tasks. Search engines such as Nuts are normally very focused on a specific functionality and are not focused on extensibility. Furthermore there are manly focused on crawling, requesting certain pages and extract links to other pages, which in our opinion is only one small area for automated robots. While there are a number of existing crawler libraries for various task, each of them comes with a custom API and there are no generic interface for automatically determining which crawler (droids) to use for a specific task. The Droids project attempts to remove this duplication of efforts. We believe that by pooling the efforts of multiple projects we will be able to create a generic robot framework that exceeds the capabilities and quality of the custom solutions of any single project. The focus of Droids is not a single crawler but more to offer different reusable components that custom droids (robots) can use to automate certain tasks. An intelligent standalone robot framework project will not only provide common ground for the developers of crawler but as well for any other automated application (robots) libraries. === Initial Goals === The initial goals of the proposed project are: * Viable community around the Droids codebase * Active relationships and possible cooperation with related projects and communities (e.g. reusing Tika for text extraction) * Generic robot API for crawling, extracting structured text content and/or new task, filtering task and handle the content * Flexible extension and plugin development to create a wide range of functionality * Fuel develop of various droids and bring the current wget style crawler to state-of-the-art level == Current Status == === Meritocracy === All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source codebases. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is not yet a clear Droids community. Instead we have a number of people and related projects with an understanding that an intelligent standalone robot framework project would best serve everyone's interests. The primary goal of the incubating project is to build a self-sustaining community around this shared vision. === Core Developers === The initial set
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631911#action_12631911 ] Grant Ingersoll commented on INCUBATOR-77: -- Note, I created issues in both Lucene and Solr to handle this now that it is in Lucene. I think it makes more sense to track from there. [IP-GRANT] Local Lucene/Solr Code Dump -- Key: INCUBATOR-77 URL: https://issues.apache.org/jira/browse/INCUBATOR-77 Project: Incubator Issue Type: New Feature Environment: lucene.apache.org Reporter: Ian Holsman Attachments: locallucene.tgz.asc $ rpm -qf $(which md5sum) coreutils-5.97-12.1.el5 $ md5sum locallucene.tgz e470f7dfd963994eebb6c5002f810549 locallucene.tgz -- 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]
Re: [IP-Clearance] Local Lucene
Fixed. On Sep 13, 2008, at 3:51 AM, Robert Burrell Donkin wrote: On Fri, Sep 12, 2008 at 1:53 PM, Grant Ingersoll [EMAIL PROTECTED] wrote: Please check https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/local-lucene-solr.xml and vote to accept. AIUI this is a lazy process but it looks good to me :-) so +1 if it's needed a small point but the section id: section id=XYZ+Codebase+Intellectual+Property+%28IP%29+Clearance +Status titleLocal Lucene Codebase Intellectual Property (IP) Clearance Status/title /section is still XYZ not local-lucene - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP-Clearance] Local Lucene
Please check https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/local-lucene-solr.xml and vote to accept. See also https://issues.apache.org/jira/browse/INCUBATOR-77 Thanks, Grant Ingersoll - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628089#action_12628089 ] Grant Ingersoll commented on INCUBATOR-77: -- There also seems to be dependencies on other LGPL code. In the download, I see: ./contrib/demo/localcinema/libs/com/mapitz/gwt/googlemaps_gwt/2_2_1/googlemaps_gwt-2_2_1.jar ./lib/common/geoapi-nogenerics-2.1-M2.jar ./lib/common/gt2-referencing-2.3.1.jar ./lib/common/jsr108-0.01.jar ./lib/common/junit-4.1.jar ./lib/lucene/lucene-core-2.2.0.jar ./lib/solr/apache-solr-1.3-dev.jar ./lib/solr/apache-solr-common-1.3-dev.jar ./target/locallucene.jar ./target/mqspatialbase.jar The geo tools stuff is LGPL and the Geo API stuff appears to be a new license by the Open Geospatial Consortuim. Both of these libraries usages seems to be limited to one or two files. The jsr108 stuff seems like it could be removed, as it doesn't appear to be used (and the JSR seems to be dead: http://jcp.org/en/jsr/detail?id=108 [IP-GRANT] Local Lucene/Solr Code Dump -- Key: INCUBATOR-77 URL: https://issues.apache.org/jira/browse/INCUBATOR-77 Project: Incubator Issue Type: New Feature Environment: lucene.apache.org Reporter: Ian Holsman Attachments: locallucene.tgz.asc $ rpm -qf $(which md5sum) coreutils-5.97-12.1.el5 $ md5sum locallucene.tgz e470f7dfd963994eebb6c5002f810549 locallucene.tgz -- 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]
IP Clearance form re INCUBATOR-77
I'm trying to resolve INCUBATOR-77 and I feel stuck on the wording in the clearance template: Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. and Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. Per the issue mentioned, there is an LGPL dependency right now that is going to be resolved. Thus, I am not sure what to do. Can we fill out this and proceed w/ the checking in the code, knowing that we can't release it until this is resolved or can I truly not finish filling out the IP clearance (https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/local-lucene-solr.xml ) until it is resolved? Part of me thinks, that if we commit, but not release, that we will get some user volunteers to take up the issue of replacing the problematic code. My understanding of the ASF (and based on Doug C.'s comment) is that we could commit as long as we don't release, but the clearance template seems to put up a gate that isn't necessarily there. Please advise. Thanks, Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Etch
FWIW, I'm +1 on the proposal, regardless of the name. On Aug 13, 2008, at 12:58 PM, scott comer wrote: the discussion about names seems somewhat done. it is easy to get the impression from the volume that there is a demand for name change. in my opinion there isn't. certainly names is a rich topic and the discussion would never die down on it's own because it is so much fun. it's a wonder anything gets done... here is a summary of who's responded to our proposal and an indication of the topic. [EMAIL PROTECTED] +1 [EMAIL PROTECTED] +1 (MENTOR) [EMAIL PROTECTED] +1 (TOOMANY, NAME) [EMAIL PROTECTED] +1 (NAME) [EMAIL PROTECTED] +1 (TOOGOOD, TOOMANY, NAME, MENTOR) [EMAIL PROTECTED] +1 [EMAIL PROTECTED] +1 (TOOMANY, MENTOR) [EMAIL PROTECTED] (TOOMANY) [EMAIL PROTECTED] (NAME) [EMAIL PROTECTED] (QUESTION) [EMAIL PROTECTED] (NAME) [EMAIL PROTECTED] (NAME) [EMAIL PROTECTED] (NAME) [EMAIL PROTECTED] (TOOMANY) [EMAIL PROTECTED] (TOOMANY) [EMAIL PROTECTED] (NAME) of the people that mention name (8), only 3 are voting: henning: concerned about confusion with debian. only says we need to be careful and explicit. niall: wants to see the q resolved. likes the name, sees no real objection. niclas: conflict with debian; only worries about it. of the rest, most like the name etch and seem to be just tossing the ball around. the main other concern is that of confusion with Debian Etch vs. Apache Etch. There was some discussion about whether etch could get to the top of the google list. so, can we put the name question to bed? it was suggested that the podling could/should decide the issue for itself, later. is there a problem with that? are there any other concerns about the proposal which aren't addressed? scott out -- Grant Ingersoll http://www.lucidimagination.com Lucene Helpful Hints: http://wiki.apache.org/lucene-java/BasicsOfPerformance http://wiki.apache.org/lucene-java/LuceneFAQ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Etch
On Aug 8, 2008, at 4:28 AM, James Dixson (jadixson) wrote: Simple put: a name change is work. Before I can accept the need to do work, I want to clearly understand the benefits of doing it. Etch, while new to open-source, does have some awareness in a technical community ( http://developer.cisco.com/web/cuae ). We have been publicly pitching and distributing etch in our community for several months now. People have been using the technology and for our current community Etch != Debian. Granted, a couple of months is a short amount of time, but it is something. Imposing a name change on our current community, with the reasoning that the future community, would be unable to differentiate between Apache Etch and the etch release Debian, would be disruptive. I don't think the argument is necessarily that the future community can't distinguish between Apache Etch and Debian, I think the argument is that the future community won't be able to find it, period, which means the future community may well be smaller than it would be w/ a more distinctive name. Put it this way, you search for Hadoop, the top 10 on Google is all Apache Hadoop. You search for Etch and you will be lucky to crack the top 10, me thinks, but who knows maybe you'll get enough rank to displace the Etch-a-Sketch and it will be a non-issue. Of course, the work thing I understand, too, although it seems like a global search and replace wouldn't be that bad. You also certainly could change it over time, even after being accepted into incubation, I think, just as long as it's done before first release. FWIW, I like the name Etch :-) -Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] accept Tashi into the Incubator
+1 On Aug 4, 2008, at 1:48 PM, Doug Cutting wrote: Please vote on accepting Tashi into the Incubator. Tashi's proposal is at: http://wiki.apache.org/incubator/TashiProposal Thanks! Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619203#action_12619203 ] Grant Ingersoll commented on INCUBATOR-77: -- That's fine by me. The one thing I would ask is maybe a status on where it's currently at. Is this something that is almost fixed or nowhere near? [IP-GRANT] Local Lucene/Solr Code Dump -- Key: INCUBATOR-77 URL: https://issues.apache.org/jira/browse/INCUBATOR-77 Project: Incubator Issue Type: New Feature Environment: lucene.apache.org Reporter: Ian Holsman Attachments: locallucene.tgz.asc $ rpm -qf $(which md5sum) coreutils-5.97-12.1.el5 $ md5sum locallucene.tgz e470f7dfd963994eebb6c5002f810549 locallucene.tgz -- 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]
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[
https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617415#action_12617415
]
Grant Ingersoll commented on INCUBATOR-77:
--
{quote}
my understanding is that this code is being replaced with the code in the
mqspatialbase directory, so will not be there in the medium term.
{quote}
It's not clear to me when that needs to take place by. Is it before release of
the contrib or is it before acceptance?
http://incubator.apache.org/ip-clearance/ip-clearance-template.html says to:
{quote}
Check and make sure that for all items included with the distribution that is
not under the Apache license, we have the right to combine with Apache-licensed
code and redistribute.
{quote}
Right now, I don't think I can answer that in the affirmative. So, Im not
sure what to do at this point.
[IP-GRANT] Local Lucene/Solr Code Dump
--
Key: INCUBATOR-77
URL: https://issues.apache.org/jira/browse/INCUBATOR-77
Project: Incubator
Issue Type: New Feature
Environment: lucene.apache.org
Reporter: Ian Holsman
Attachments: locallucene.tgz.asc
$ rpm -qf $(which md5sum)
coreutils-5.97-12.1.el5
$ md5sum locallucene.tgz
e470f7dfd963994eebb6c5002f810549 locallucene.tgz
--
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]
[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump
[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613032#action_12613032 ] Grant Ingersoll commented on INCUBATOR-77: -- Ping. Any progress on the headers? [IP-GRANT] Local Lucene/Solr Code Dump -- Key: INCUBATOR-77 URL: https://issues.apache.org/jira/browse/INCUBATOR-77 Project: Incubator Issue Type: New Feature Environment: lucene.apache.org Reporter: Ian Holsman Attachments: locallucene.tgz.asc $ rpm -qf $(which md5sum) coreutils-5.97-12.1.el5 $ md5sum locallucene.tgz e470f7dfd963994eebb6c5002f810549 locallucene.tgz -- 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]
Local Lucene and Local Solr Donation
The creators of Local Lucene and Local Solr (http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene.htm ) have generously agreed to donate these projects to Lucene. Details of the donation are at http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene.htm The Lucene PMC is working through the details of the software grant (paperwork for the most part.) In the meantime, I would like to open the discussion of where this should live in Lucene. The options are: 1. Split them up and make them each a part of Lucene and Solr and let the committers of those projects decide where things go 2. Create a separate Geo search subproject under Lucene TLP with it's own set of committers, etc. just like any of the other sub projects (Solr, Tika, Java, etc.) 3. Other? -Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Local Lucene and Local Solr Donation
please disregard, wrong general list. Darn email completion! -Grant On Jun 25, 2008, at 10:12 AM, Grant Ingersoll wrote: The creators of Local Lucene and Local Solr (http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene.htm ) have generously agreed to donate these projects to Lucene. Details of the donation are at http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene.htm The Lucene PMC is working through the details of the software grant (paperwork for the most part.) In the meantime, I would like to open the discussion of where this should live in Lucene. The options are: 1. Split them up and make them each a part of Lucene and Solr and let the committers of those projects decide where things go 2. Create a separate Geo search subproject under Lucene TLP with it's own set of committers, etc. just like any of the other sub projects (Solr, Tika, Java, etc.) 3. Other? -Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Hama into the Incubator
+1 On May 13, 2008, at 7:27 PM, Edward J. Yoon wrote: Dear Incubator PMC, There has been some discussion around the Hama proposal, and we would now like to officially propose Hama to the Incubator for consideration, with Grant Ingersoll's +1. Please vote on accepting the Hama project for incubation. The full Hama proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/HamaProposal. We ask the Incubator PMC to sponsor the Hama podling, with myself, Ian Holsman, and Jeff Eastman as the mentors. The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. [ ] +1 Accept Hama as a new podling [ ] -1 Do not accept the new podling (provide reason, please) == Abstract == Hama will develop a parallel matrix computational package based on [http://hadoop.apache.org Hadoop] Map/Reduce. == Proposal == Hama will develop a parallel matrix computational package, which provides an library of matrix operations for the large-scale processing development environment and Map/Reduce framework for the large-scale Numerical Analysis and Data Mining, which need the intensive computation power of matrix inversion, e.g. linear regression, PCA, SVM and etc. It will be also useful for many scientific applications, e.g. physics computations, linear algebra, computational fluid dynamics, statistics, graphic rendering and many more. == Background == Currently, several shared-memory based parallel matrix solutions can provide a scalable and high performance matrix operations, but matrix resources can not be scalable in the term of complexity. And, Hadoop HDFS Files and Map/Reduce can only used by 1D blocked algorithm. == Rationale == Hama approach proposes the use of 3-dimensional Row and Column (Qualifier), Time space and multi-dimensional Columnfamilies of [http://hadoop.apache.org/hbase Hbase], which is able to store large sparse and various type of matrices (e.g. Triangular Matrix, 3D Matrix, and etc.) and utilize the 2D blocked algorithm. its auto-partitioned sparsity sub-structure will be efficiently managed and serviced by Hbase. Row and Column operations can be done in linear-time, where several algorithms, such as ''structured Gaussian elimination'' or ''iterative methods'', run in O(the number of non-zero elements in the matrix / number of mappers) time on Hadoop Map/Reduce. == Current Status == In its current state, the 'hama' is buggy and needs filling out, but generalized matrix interface and basic linear algebra operations was implemented within a large prototype system. In the future, We need new parallel algorithms based on Map/Reduce for performance of heavy decompositions and factorizations. It also needs tools to compose an arbitrary matrix only with certain data filtered from hbase array structure. == Meritocracy == The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project. === Community === Hama seeks to develop developer and user communities during incubation. == Core Developers == The initial set of committers includes folks from the [http://hadoop.apache.org Hadoop] [http://hadoop.apache.org/hbase Hbase] communities. We have varying degrees of experience with Apache-style open source development, ranging from none to ASF Members. == Alignment == The developers of Hama want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components. == Known Risks == === Orphaned products === Most of the active developers would like to become Hama Committers or PMC Members and have long term interest to develop/maintain and '''use''' the code. === Inexperience with Open Source === We has already a good experience with Apache open source development process. === Homogenous Developers === The current list of committers includes developers from several different companies ([http://en.wikipedia.org/wiki/NHN NHN, corp], TMAX software, Korea Research Institute of Bioscience and Biotechnology, Students) plus many independent volunteers. The committers are geographically distributed across the Europe, and Asia. They are experienced with working in a distributed environment. === Reliance on Salaried Developers === It is expected that Hama development will occur on both salaried time and on volunteer time, after hours. While there is reliance on salaried developers (currently from [http://en.wikipedia.org/wiki/NHN NHN, corp], but it's expected that other company's salaried developers will also be involved), the Hama Community is very active and things should balance out fairly quickly. In the meantime, [http://en.wikipedia.org/wiki/NHN NHN, corp] might support the project in the future by dedicating
RESULT [IP CLEARANCE] Mahout Taste Software Grant
OK, looks like this vote has cleared and Taste can now be officially imported into Mahout. Thanks, Grant On May 2, 2008, at 2:35 PM, Grant Ingersoll wrote: Please check clearance on: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/mahout-taste.xml Thanks, Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP CLEARANCE] Mahout Taste Software Grant
Please check clearance on: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/mahout-taste.xml Thanks, Grant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[DISCUSS: IP CLEARANCE] Mahout Taste Software Grant
Hi, This is my first time doing an IP clearance, so I was wondering if one of the incubator veterans could double check the mahout-taste.xml grant located in https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance before I call a vote on it. Thanks, Grant Ingersoll - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
