Re: [VOTE] Apache Lucene.Net graduation from the incubator
+1 On Sat, Jul 21, 2012 at 12:40 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey all, The Lucene.Net community feels ready to graudate. Our internal vote was a success (~40 +1's and a bit of a mess because we had a number of mailing lists which spread our vote out - sorry about that spam). We had some concerns regarding the size and activity of our community, however, with addition of two new committers just recently we feel that we are still growing as a community and that graduating will only help us build our community further. Dev Mailing List: http://s.apache.org/FQF User Mailing List: http://s.apache.org/P6f Our [Proposal] Resolution thread in general (http://s.apache.org/Qv6) didn't garner many comments, but we take silence as your proposal looks good Once again our resolution is located: https://cwiki.apache.org/confluence/display/LUCENENET/Graduation+-+Resolution+Template I'll leave this vote open for at least 72 hours: [+1] We need some time apart to appreciate each other [-1] We'd like you to stay because... Thanks all, ~Prescott - 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: including external code under apache 2.0
Itamar, The easiest way to submit the CLA is via email. Grab the form here: http://www.apache.org/licenses/icla.txt Print, then sign, then scan and email the image to secret...@apache.org (or do a digital signature on the PDF version... http://www.apache.org/licenses/icla.pdf ) Thanks, Troy On Sat, Apr 28, 2012 at 2:16 PM, Itamar Syn-Hershko ita...@code972.com wrote: That mail from Stephan got lost in my inbox, so I never followed up on that. I guess now would be a good chance to tie up all loose ends. How do I do the ICLA? On Sat, Apr 28, 2012 at 1:11 AM, Troy Howard thowar...@gmail.com wrote: My understanding is that we can include the code as long as we have a ICLA from Itamar. This was discussed at length in January for another contribution that the same contributor wanted to donate. Stephan (Bodewig, our Incubation mentor) laid out what needed to be done really clearly in that context. Here's the link to the final message on that thread where Stephan recaps the relevant points: http://s.apache.org/HZa I don't know if Itamar ever followed up after that and filed a ICLA. If he did, we're good and just need to commit the code.. Otherwise, we'll need him to do the ICLA first. Thanks, Troy On Fri, Apr 27, 2012 at 2:30 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey all, We've had a community member port a library for Lucene.Net that we'd like to include in our contrib packages. The package is under the apache 2.0 license, so we think we are in the clear to include the code into our contrib package - but we weren't sure and just wanted to double check. The contrib project is located here: https://github.com/synhershko/Spatial4n Thanks for your guidance~Prescott - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: including external code under apache 2.0
My understanding is that we can include the code as long as we have a ICLA from Itamar. This was discussed at length in January for another contribution that the same contributor wanted to donate. Stephan (Bodewig, our Incubation mentor) laid out what needed to be done really clearly in that context. Here's the link to the final message on that thread where Stephan recaps the relevant points: http://s.apache.org/HZa I don't know if Itamar ever followed up after that and filed a ICLA. If he did, we're good and just need to commit the code.. Otherwise, we'll need him to do the ICLA first. Thanks, Troy On Fri, Apr 27, 2012 at 2:30 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey all, We've had a community member port a library for Lucene.Net that we'd like to include in our contrib packages. The package is under the apache 2.0 license, so we think we are in the clear to include the code into our contrib package - but we weren't sure and just wanted to double check. The contrib project is located here: https://github.com/synhershko/Spatial4n Thanks for your guidance~Prescott - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release NPanday 1.3-incubating
Regarding: I cannot read the tar.gz files with my normal tools (hexdump shows that they are in RAR format), and the hashes have got spurious lines in them which break automated checkers. Looks like you guys are a) building the release packages on Windows, and b) using Microsoft's FCIV tool to generate MD5 and SHA1 hashes. This is something I tried to do at first as well. To get a standard output for that, you should use the standard Unix tools... You can download gnu coreutils binaries compiled for Windows from here: http://s.apache.org/rV Install that package, and use the included md5.exe/sha1.exe programs to generate your checksums, and it will be exactly Apache's standard for that (instead of messing around with munging the output from FCIV).. Plus you get a bunch of other handy standard unix commandline apps without needingt to install cygwin... Thanks, Troy On Wed, Mar 16, 2011 at 2:25 AM, sebb seb...@gmail.com wrote: On 15 March 2011 11:22, Adelita Padilla apadi...@maestrodev.com wrote: Hi, On Tue, Mar 15, 2011 at 12:05 PM, sebb seb...@gmail.com wrote: On 15 March 2011 03:27, Brett Porter br...@apache.org wrote: On 14/03/2011, at 10:49 PM, sebb wrote: On 14 March 2011 06:05, Adelita Padilla apadi...@g2ix.net wrote: Hi, The Apache NPanday community has approved the 1.3-incubating release and we are now looking for the approval of the IPMC to publish the release. These are the major changes included in this release: * Visual Studio 2010 and .Net 4.0 Framework support * Removal of UAC and PAB directories Subversion tag: https://svn.apache.org/repos/asf/incubator/npanday/tags/npanday-1.3-incubating/ NOTICE file still says 2011 Fixed in SVN. Not a blocker for the release, I imagine. There is no DISCLAIMER anywhere I could find. Fixed in SVN. Liit, I suggest you add that to the release tarballs and re-sign them. It seems like overkill to start the release over for this. I've added the DISCLAIMER.txt to the tarballs and I've uploaded them to http://people.apache.org/~apadilla I cannot read the tar.gz files with my normal tools (hexdump shows that they are in RAR format), and the hashes have got spurious lines in them which break automated checkers. Also the MSI file has not been updated, so presumably its LICENSE file has not been updated. Nor on the website, for that matter, though there is an Incubator logo. Top right of http://incubator.apache.org/npanday/docs/1.3-incubating/index.html and http://incubator.apache.org/npanday/index.html ? Yes, the logos are (still) there. I'm assuming you were looking at the old docs from the last release currently linked from the site (since it was rolled back), which points out it came from Codeplex. I am looking at the current website. The pages you mention above have the Incubator logo, but no disclaimer that I could find. For an example of how it can be done, see: http://incubator.apache.org/rat/ The first paragraph starts: Apache RAT is an effort undergoing incubation at The Apache Software Foundation (ASF) ... I've redeployed the website and it now contains the disclaimer, see: http://incubator.apache.org/npanday/ OK, looks fine. I think this is a blocker. Staging repository: http://vmbuild.apache.org/archiva/repository/staged-npanday/ Distribution files are located here: http://people.apache.org/~apadilla/npanday/1.3-incubating/ The key is registered with public servers, but the name etc. should ideally have some reference to Apache: gpg: searching for 0X7580DCDB from hkp server pgp.mit.edu (1) apadilla (adelita) apadi...@maestrodev.com 2048 bit RSA key 7580DCDB, created: 2011-01-14 I cannot find the KEYS file. https://svn.apache.org/repos/asf/incubator/npanday/project/KEYS http://www.apache.org/dist/incubator/npanday/KEYS Added apadi...@apache.org to http://www.apache.org/dist/incubator/npanday/KEYS OK. Thanks, found that later. It would help to include the link in VOTE emails. I don't think all users mention Apache, but it'd be good for Liit to add her ASF email address onto the key and resubmit it. The repository-builder files seem to contain chunks of a repository, and contain many non-ASF files. It's not clear if these all have compatible licences, and anyway they don't seem to be mentioned in the LICENSE file (or NOTICE, where necessary). Potential blocker. The MSI file also contains lots of 3rd party jars. I referenced this here: http://markmail.org/message/sjlmw66a76phyn25 It's not ideal, but they are all redistributable in accordance with the legal policy. Do any of them require attribution in the NOTICE file? It appears that NUnit does (from updated LICENSE.txt): If you use this software in a product, an acknowledgment (see the following) in the product documentation is required. Unless they all use the
Re: [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC2
ant, You're right. We will address this in the next release. There is a CHANGES.TXT in ~/src in the source release .zip. It unfortunately a bit out of date, and is does not list a few changes/bugfixes that are found in SVN. Also, it seems ot be the change log from Lucene, not Lucene.Net... I assume it's in sync with the changes and was part of a patch, but I know that we have had bug fixes/minor changes separate from Lucene's development. It's also not included in the binary .zip, since the ~/src folder is not included. We are in the process of restructuring the folders/file locations. We'll move the change log to the root directory, and ensure it's kept up to date and reflects Lucene.Net specific changes, as well as Lucene's... Thanks, Troy On Sat, Mar 5, 2011 at 12:11 AM, ant elder ant.el...@gmail.com wrote: Looks good to me, +1. It would be nice to include some sort of release notes or changes file within the distributions ...ant On Wed, Mar 2, 2011 at 8:17 AM, Troy Howard thowar...@gmail.com wrote: All, I'm happy to announce that Lucene.Net 2.9.2-incubating-RC2 is available and ready for your testing and voting. This will be our first release since returning to the Incubator. We look forward to your input. Release candidate artifacts: http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/ SVN tag revision: http://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 PPMC Vote Thread: http://bit.ly/eGcbYY The vote is open for 72 hours and passes if a majority of at least three +1 Lucene.Net PMC votes are cast. Please cast your votes! [ ] +1 Release this package as Apache Lucene.Net 2.9.2-incubating [ ] -1 Do not release this package because... Thanks to everyone involved for the hard work and contributions which made this release possible. Thanks, Troy - 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
[RESULT] [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC2
All, This vote passes with four (4) positive IMPC votes. Apache Lucene.Net 2.9.2-incubating-RC2 will be officially released as Apache Lucene.Net 2.9.2-incubating. We sincerely appreciate everyone who contributed to making our first release under our new status a success. Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC2
All, I'm happy to announce that Lucene.Net 2.9.2-incubating-RC2 is available and ready for your testing and voting. This will be our first release since returning to the Incubator. We look forward to your input. Release candidate artifacts: http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/ SVN tag revision: http://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 PPMC Vote Thread: http://bit.ly/eGcbYY The vote is open for 72 hours and passes if a majority of at least three +1 Lucene.Net PMC votes are cast. Please cast your votes! [ ] +1 Release this package as Apache Lucene.Net 2.9.2-incubating [ ] -1 Do not release this package because... Thanks to everyone involved for the hard work and contributions which made this release possible. Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC2
Oops, typo! ... and passes if a majority of at least three +1 Lucene.Net PMC votes are cast. should have been : ... and passes if a majority of at least three +1 Incubator PMC votes are cast. Thanks, Troy On Wed, Mar 2, 2011 at 12:17 AM, Troy Howard thowar...@gmail.com wrote: All, I'm happy to announce that Lucene.Net 2.9.2-incubating-RC2 is available and ready for your testing and voting. This will be our first release since returning to the Incubator. We look forward to your input. Release candidate artifacts: http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/ SVN tag revision: http://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 PPMC Vote Thread: http://bit.ly/eGcbYY The vote is open for 72 hours and passes if a majority of at least three +1 Lucene.Net PMC votes are cast. Please cast your votes! [ ] +1 Release this package as Apache Lucene.Net 2.9.2-incubating [ ] -1 Do not release this package because... Thanks to everyone involved for the hard work and contributions which made this release possible. Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Rave project
My point was: Bill made a statement, which though rather neutral and ambiguous, seemed to indicate that he (or perhaps a silent mass of others) did not think the proposal was such a good idea, due to the risks associated with a significant amount of corporate support and involvement. At least, that's how I interpreted it. Since then, the response has been fairly one sided, supporting the project, and unfortunately, Bill has not responded to fairly direct questions about his intent or reasoning. I'd much rather be hearing more from him about this issue than continuing to express my opinions. In fact, some of the respondents have stated clearly that they missed his point. To me, his point is obvious. He's expressing that perhaps the known risks (which were accurately described in the proposal) might be significant enough that no one is willing to vocally support the proposal. Maybe they aren't significant enough to cause outcry, but significant enough to cause unspoken concerns and a lack of direct support because of it. Again, I don't agree with that opinion, but I also don't think it should be dismissed. So, supposing Bill does indeed have that assumed perspective, and supposing that it is a valid perspective, and that there may be other folks who aren't speaking up who have that perspective, my point was that, in good faith, the project make a concerted effort to address that concern, in the same way they would address issues with the code: by making a JIRA issue for it, scheduling it and resolving it. Now, back to my opinion... worthy or not as it may be. Clearly a lack of response cannot be taken as positive or negative, a silent mass is just that -- silent. No consent nor dissent expressed. Is that sufficient to move forward? In this case, I think so, and I agree with Upayavira's initial statements. I doubt if there is a large group of people out there, silently disapproving and not speaking up. That's very un-Apache, and thus, very unlikely for this situation. More than likely, people are just too busy to give an encouraging word. But, if someone does give voice to a concern, shouldn't that be taken to heart? The responses I saw from Ross seemed dismissive, and that raised enough concern, from my point of view that I felt like typing up my opinion + solution, and hitting 'Send'. Assuming silent consent is fine, but being dismissive of a voiced concern is not. Again, that's my 'strong opinion, weakly held'. Honestly, I have already said far more about this topic than I had any intention to. Hopefully this lengthy message provides enough detail into the inner workings of my mind that it satisfies any further confusion as to what the heck I was talking about. Thanks, Troy On Thu, Feb 24, 2011 at 5:33 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Troy, I am not really sure what your point is. So you believe that: I think the 'Known Risks' section in the proposal enumerates that pretty clearly, so I won't repeat it. ... yet you raise an objection for somebody else who might think otherwise? Is that because you anticipate an objection and you want to prevent that by suggesting a solution that my prevent the objection to occur in the first place? [...] My statements were meant to speak to the folks who think otherwise, as a reasonable compromise (assuming Bill's stance, and anyone who is quietly in agreement, is to not allow it into the Incubator). Why not let the guys who have an objection speak for themselves? Regarding Bill's message, I didn't see him raising an objection, just making a valid point. Ate explained already both that it was addressed and the rationale for the wording in the proposal. I don't think my vote counts for much, but I'm a +1. ;) Well, the vote is on now. If I misunderstood your intentions I am sorry, but they are not very clear. Cheers, Hadrian - 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: [VOTE] Accept Rave into the Incubator
+1 On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma a...@douma.nu wrote: Given the feedback received so far I think the Rave proposal is in good shape so I'd like to bring up the vote for accepting Rave into the Incubator. The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also copied as text below. Please vote. [ ] +1 Accept Rave into the incubator [ ] +0 Don't care' [ ] -1 Reject for the following reason: I'll close the vote at Tuesday morning 1st March CET to accommodate for the coming weekend. That's a little over 5 days from now. Regards, Ate - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal - = Apache Rave Proposal = == Abstract == Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an out-of-the-box as well as an extendible lightweight Java platform to host, serve and aggregate (Open)Social Gadgets and services through a highly customizable and Web 2.0 friendly front-end. Rave is targeted as engine for internet and intranet portals and as building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites and (social) network oriented services and platforms. For the [[http://www.opensocial.org/|OpenSocial]] container and services the (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a later stage further generalization is envisioned to also transparently support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using [[http://incubator.apache.org/wookie/|Apache Wookie]]. == Proposal == The reason for starting Rave is to bring together and combine several existing projects and teams currently working towards more or less the same or overlapping goals but each in their own small(er) target audience and community. The goal for Rave is to become a lightweight and open-standards based extendible platform for using, integrating and hosting !OpenSocial and W3C Widget related features, technologies and services. It will also provide strong context-aware personalization, collaboration and content integration capabilities and a high quality out-of-the-box installation as well as be easy to integrate in other platforms and solutions. The initial features for Rave will at least be based on the current capabilities from the contributing external projects, for which they will provide the necessary code contributions. However, the code base for Rave will be built anew with strong focus on generalization, customization and extendibility to support the intended multi-purpose adoption and integration. The contributing external projects will start using and switch to the new Rave based solution as soon as the initial features become available to ensure the continued participation and interest from their side as well as their own communities. The intended initial features include: '''Core Features''' 1. Advanced !OpenSocial compliance and optional features support 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation 1. Self-service application administration including security, gadget management and page templates 1. User and group management with full privacy model 1. Gadget repository with life-cycle management (install/update/remove) and extended meta data (categories, comments, ratings, etc.) 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, layouts, navigation) 1. Full OAuth support 1. Support for security restrictions on both Gadgets and page/tag/layout customizations 1. Set of common and general purpose Gadgets to be usable out-of-the-box 1. Support for inter-gadget messaging with examples '''Extensible Features''' 1. Pluggable persistence 1. Pluggable security model with example modules for authentication and authorization 1. Support for !OpenSocial extensions not (yet) defined in the specification 1. Support for other (non-standard, yet) pluggable container services and extensions Beyond these initial features the vision and scope for Rave goes much further and includes integrating and providing other highly desired/needed features like: * native W3C Widgets support through [[http://incubator.apache.org/wookie|Apache Wookie]] * pluggable and extendible content integration and management services * space extensions and management features, like http://wiki.opensocial.org/index.php?title=Space_extension * context aware features and extensions integration for personalized and social network and (mobile) device oriented sites and channels * enhanced client-side widget messaging, coordination and co-location support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry * space, page and Gadget based linking, navigation, coordination and collaboration * inline widget rendering, like http://issues.apache.org/jira/browse/SHINDIG-1402 *
Re: [PROPOSAL] Apache Rave project
In my opinion, a reasonable compromise would be to set it as a project goal to reduce corporate dependency on the committers list. I would take that so far as to treat it as a bug, place an issue in JIRA to that effect, and schedule a date/version for the issue to be resolved. This will remind everyone to remain focused on attracting a diverse set of independent individuals, without corporate attachment, as contributors and eventually as committers. That said, they are more likely to attract that community as an Apache Incubator Podling. I would make resolution of the JIRA issue a blocking task to graduation however. Resolving these kinds of issues is sort of the point of the Incubator, correct? Thanks, Troy On Thu, Feb 24, 2011 at 9:31 AM, Craig L Russell craig.russ...@oracle.com wrote: I'm looking forward to a vote on this proposal. I've read the thread and I think it's good to know **up front** that there are going to be corporate contributions, not just from one corporation. Craig On Feb 21, 2011, at 3:18 PM, Ate Douma wrote: I would like to propose the Apache Rave project to the Incubator PMC. Our draft proposal is appended to the end of this email and is available at: http://wiki.apache.org/incubator/RaveProposal The Apache Rave project proposal is a joined effort of Hippo, the MITRE Corporation, the Open Gateway Computing Environments project (OGCE), the SURFnet SURFConext Portal project, OSS Watch, and several other individuals. == Abstract == Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an out-of- the-box as well as an extendible lightweight Java platform to host, serve and aggregate (Open)Social Gadgets and services through a highly customizable and Web 2.0 friendly front-end. Rave is targeted as engine for internet and intranet portals and as building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites and (social) network oriented services and platforms. For the OpenSocial container and services the (Java) Apache Shindig will be integrated. At a later stage further generalization is envisioned to also transparently support W3C Widgets using Apache Wookie. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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] Apache Rave project
I think the 'Known Risks' section in the proposal enumerates that pretty clearly, so I won't repeat it. I don't know why anyone would take exception to it be included in the Incubator. It seems like a good fit, as long as the stated known risks are addressed during incubation. My statements were meant to speak to the folks who think otherwise, as a reasonable compromise (assuming Bill's stance, and anyone who is quietly in agreement, is to not allow it into the Incubator). I don't think my vote counts for much, but I'm a +1. ;) Thanks, Troy On Thu, Feb 24, 2011 at 3:18 PM, Ross Gardler rgard...@apache.org wrote: On 24/02/2011 23:11, Troy Howard wrote: In my opinion, a reasonable compromise would be to set it as a project goal to reduce corporate dependency on the committers list. I'm really confused where this is coming from. The goal of incubation is to generate sufficient diversity in contributions to ensure that the community is viable even with the departure of a number of active parties. This proposal is coming *into* the incubator with more diversity than is typically required to graduate (not that I'm suggesting there are shortcuts for incubation here). Why on earth is having this diversity being seen as a problem? Nobody has explained that to me yet and unless someone does so I, as a mentor, am going to ask the champion to call the vote. Ross I would take that so far as to treat it as a bug, place an issue in JIRA to that effect, and schedule a date/version for the issue to be resolved. This will remind everyone to remain focused on attracting a diverse set of independent individuals, without corporate attachment, as contributors and eventually as committers. That said, they are more likely to attract that community as an Apache Incubator Podling. I would make resolution of the JIRA issue a blocking task to graduation however. Resolving these kinds of issues is sort of the point of the Incubator, correct? Thanks, Troy On Thu, Feb 24, 2011 at 9:31 AM, Craig L Russell craig.russ...@oracle.com wrote: I'm looking forward to a vote on this proposal. I've read the thread and I think it's good to know **up front** that there are going to be corporate contributions, not just from one corporation. Craig On Feb 21, 2011, at 3:18 PM, Ate Douma wrote: I would like to propose the Apache Rave project to the Incubator PMC. Our draft proposal is appended to the end of this email and is available at: http://wiki.apache.org/incubator/RaveProposal The Apache Rave project proposal is a joined effort of Hippo, the MITRE Corporation, the Open Gateway Computing Environments project (OGCE), the SURFnet SURFConext Portal project, OSS Watch, and several other individuals. == Abstract == Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an out-of- the-box as well as an extendible lightweight Java platform to host, serve and aggregate (Open)Social Gadgets and services through a highly customizable and Web 2.0 friendly front-end. Rave is targeted as engine for internet and intranet portals and as building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites and (social) network oriented services and platforms. For the OpenSocial container and services the (Java) Apache Shindig will be integrated. At a later stage further generalization is envisioned to also transparently support W3C Widgets using Apache Wookie. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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
Lucene.Net Branding, Logo, and Promotional Activities
All, We've recently been working to update the Lucene.Net website to reflect our new status as an Incubator Podling and just generally get up to date. During that process we have been discussing the project branding and logo. The discussion can be found in the comments here: https://issues.apache.org/jira/browse/LUCENENET-379 We're thinking about having a logo design contest to engage our community by help us improve our branding. This was recently done by Apache CouchDB and with great results. We're hoping for a similar experience. We'd like to know if there is anything we should be considering about our promotional activities as a Incubator Podling. My understanding is that there are some restrictions regarding the process involved in staging this kind of thing. Specifically the documentation for Podlings/Branding/Publicity activities says: Podlings MUST coordinate with the Apache Public Relations Committee on all publicity activities by a podling. What is the best way to proceed? Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Lucene.Net Branding, Logo, and Promotional Activities
Ok, I guess by recently done by Apache CouchDB I meant, done in 2007, before it was an Apache product, and it wasn't so much a contest but a single line call for submissions in a very large blog post about technical matters. But regardless, they ended up with a great logo. Thanks, Troy On Fri, Feb 18, 2011 at 1:45 AM, Troy Howard thowar...@gmail.com wrote: All, We've recently been working to update the Lucene.Net website to reflect our new status as an Incubator Podling and just generally get up to date. During that process we have been discussing the project branding and logo. The discussion can be found in the comments here: https://issues.apache.org/jira/browse/LUCENENET-379 We're thinking about having a logo design contest to engage our community by help us improve our branding. This was recently done by Apache CouchDB and with great results. We're hoping for a similar experience. We'd like to know if there is anything we should be considering about our promotional activities as a Incubator Podling. My understanding is that there are some restrictions regarding the process involved in staging this kind of thing. Specifically the documentation for Podlings/Branding/Publicity activities says: Podlings MUST coordinate with the Apache Public Relations Committee on all publicity activities by a podling. What is the best way to proceed? Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Lucene.Net Branding, Logo, and Promotional Activities
Good advice. Will do that. Thanks, Troy On Fri, Feb 18, 2011 at 8:47 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Troy, I think it would be good to send the below to trademarks@ and to start there. HTH, Chris On Feb 18, 2011, at 3:13 AM, Troy Howard wrote: Ok, I guess by recently done by Apache CouchDB I meant, done in 2007, before it was an Apache product, and it wasn't so much a contest but a single line call for submissions in a very large blog post about technical matters. But regardless, they ended up with a great logo. Thanks, Troy On Fri, Feb 18, 2011 at 1:45 AM, Troy Howard thowar...@gmail.com wrote: All, We've recently been working to update the Lucene.Net website to reflect our new status as an Incubator Podling and just generally get up to date. During that process we have been discussing the project branding and logo. The discussion can be found in the comments here: https://issues.apache.org/jira/browse/LUCENENET-379 We're thinking about having a logo design contest to engage our community by help us improve our branding. This was recently done by Apache CouchDB and with great results. We're hoping for a similar experience. We'd like to know if there is anything we should be considering about our promotional activities as a Incubator Podling. My understanding is that there are some restrictions regarding the process involved in staging this kind of thing. Specifically the documentation for Podlings/Branding/Publicity activities says: Podlings MUST coordinate with the Apache Public Relations Committee on all publicity activities by a podling. What is the best way to proceed? Thanks, Troy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - 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: [VOTE] Accept Lucene.Net for incubation
All, Being well over 72 since the vote was initiated, and with 16 positive votes, 3 of which are binding and no negative or neutral votes, this vote passes, and is now closed. Thanks for your participation and for allowing us back into the Incubator to start next phase of life for Lucene.Net. Further gratitude goes to our helpful Mentors who are already guiding us in the needed steps to make this transition. I look forward to my next post announcing our first release under a new status. Til then, Troy On Fri, Feb 4, 2011 at 2:23 PM, Doug Cutting cutt...@apache.org wrote: +1 Doug On 01/26/2011 10:05 PM, Troy Howard wrote: All, Since posting the Lucene.Net Incubator proposal announcement on Jan 12th, we now have three mentors signed up and would like to call a vote to accept Lucene.Net into the Apache Incubator. The proposal is included below and can also be found at: http://wiki.apache.org/incubator/Lucene.Net%20Proposal Please cast your votes: [ ] +1 Accept Lucene.Net for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: Thanks, Troy = 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 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
Re: Lucene.Net ready for vote?
Much appreciated, Benson! Thanks, Troy On Wed, Jan 26, 2011 at 1:02 PM, Benson Margulies bimargul...@gmail.com wrote: I guess I could sign up as Mentor. On Wed, Jan 26, 2011 at 1:15 PM, Lombard, Scott slomb...@kingindustries.com wrote: Grant, The proposal is done, how do you feel about putting Lucene.Net to a vote with 2 mentors? Scott -Original Message- From: Grant Ingersoll [mailto:gsing...@apache.org] Sent: Tuesday, January 25, 2011 10:43 AM To: general@incubator.apache.org Subject: 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 This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you, King Industries, Inc. - 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
[VOTE] Accept Lucene.Net for incubation
All, Since posting the Lucene.Net Incubator proposal announcement on Jan 12th, we now have three mentors signed up and would like to call a vote to accept Lucene.Net into the Apache Incubator. The proposal is included below and can also be found at: http://wiki.apache.org/incubator/Lucene.Net%20Proposal Please cast your votes: [ ] +1 Accept Lucene.Net for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: Thanks, Troy = 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 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 or in coordination roles. Troy, Chris, Sergey and Prescott are currently committers on a Lucene.Net fork known as Lucere, and as such are intimately familiar with the code base and share a vision for the future direction of the project. Scott Lombard and Michael Herndon are passionate about Lucene.Net as well and have already contributed significantly in terms of project organization and direction and discussions on the mailing list. All of the proposed committers are familiar with the challenges faced with starting and maintaining a project over time. We also understand that opportunity
Re: [PROPOSAL] Lucene.Net return to the Incubator
Gianugo - Thanks so much for offering to mentor us! It's really appreciated and we look forward to enjoying the benefits of your guidance in the future. 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? Thanks, Troy On Wed, Jan 12, 2011 at 4:08 PM, Gianugo Rabellino gian...@rabellino.it wrote: On Wed, Jan 12, 2011 at 2:43 PM, Troy Howard thowar...@gmail.com wrote: All, Please review our proposal for moving the Lucene.Net project back to the Incubator. I am happy to support this proposal and signed up as a mentor. -- Gianugo Rabellino - gianugo at rabellino dot it Blog: http://boldlyopen.com - 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
[PROPOSAL] Lucene.Net return to the Incubator
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 or in coordination roles. Troy, Chris, Sergey and Prescott are currently committers on a Lucene.Net fork known as Lucere, and as such are intimately familiar with the code base and share a vision
