Re: Missing reports due NOW
The VXQuery report is available now. Apologies for the delay, Till Original-Nachricht > Datum: Sun, 17 Jan 2010 23:28:19 -0500 > Von: "Noel J. Bergman" > An: general@incubator.apache.org > Betreff: Missing reports due NOW > Missing: > > Imperius > Subversion > Thrift > VXQuery > > These were due middle of last week, and are still not present. > > --- 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: [VOTE] Graduate Apache Shindig as an Apache Top Level Project
The vote has passed with 20 +1 votes and no 0 or -1 votes. +1 binding: Matthias Wessendorf Leo Simons Ant Elder Upayavira Dave Santiago Gala Sylvain Wallez Martijn Dashorst Niclas Hedhman Davanum Srinivas Daniel Kulp Felix Meschberger Luciano Resende Bertrand Delacretaz Alan D. Cabrera +1 non binding: Dan Peterson Glen Daniels Kevin Brown Malcolm Edgar Vincent Siveton There were no special remarks regarding the board resolution draft, except that Santiago want to be part on the PMC. Next step: I will send the proposed resolution to the board for approval. Thank you for all the support, this is appreciated. Cheers, Vincent 2010/1/14 Vincent Siveton : > Hi, > > Thanks for the positive feedback on the proposal to graduate Shindig > as a TLP [1]. > > I would like to start an official vote to recommend the graduation of > Apache Shindig as a Top Level Project to the Board. > To that end I have prepared the resolution for the Board below to be > presented for consideration at the upcoming Board meeting. > > Community graduation vote thread: > http://shindig-dev.markmail.org/message/c47amdxjtntkjij5 > > Please cast your vote: > [ ] +1 to recommend Shindig's graduation > [ ] 0 don't care > [ ] -1 no, don't recommend yet, because ... > > The vote will be open for 72 hours. > > Cheers, > > Vincent > > [1] http://apache.markmail.org/message/qvpyymihv6gyh5a7 > > --- Begin Proposed Board Resolution --- > > WHEREAS, the Board of Directors deems it to be in the best interests of the > Foundation and consistent with the Foundation's purpose to establish a Project > Management Committee, charged with the creation and maintenance of open-source > software related to the implementation of an OpenSocial container and > OpenSocial API specifications, for distribution at no charge to the public. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to > be known as the "Apache Shindig PMC", is hereby established pursuant to Bylaws > of the Foundation; and be it further > > RESOLVED, that the Apache Shindig Project be and hereby is responsible for the > creation and maintenance of software related to the OpenSocial API > specifications, based on software licensed to the Foundation; and be it > further > > RESOLVED, that the office of "Vice President, Apache Shindig" be and hereby > is created, the person holding such office to serve at the direction of the > Board of Directors as the chair of Apache Shindig, and to have primary > responsibility for management of the projects within the scope of > responsibility > of the Apache Shindig PMC; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed > to serve as the initial members of the Apache Shindig PMC: > > * Ian Boston (ieb at apache dot org) > * Kevin Brown (etnu at apache dot org) > * Chris Chabot(chabotc at apache dot org) > * Chico Charlesworth (chico at apache dot org) > * Cassie Doll (doll at apache dot org) > * Evan Gilbert (evan at apache dot org) > * John Hjelmstad (johnh at apache dot org) > * Paul Lindner (lindner at apache dot org) > * Daniel Peterson (dpeterson at apache dot org) > * Louis Ryan (lryan at apache dot org) > * Henning Schmiedehausen (henning at apache dot org) > * Vincent Siveton (vsiveton at apache dot org) > * Upayavira (upayavira at apache dot org) > * Adam Winer (awiner at apache dot org) > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Paul Lindner be appointed to the > office of Vice President, Apache Shindig, to serve in accordance with and > subject to the direction of the Board of Directors and the Bylaws of the > Foundation until death, resignation, retirement, removal or disqualification, > or > until a successor is appointed; and be it further > > RESOLVED, that Apache Shindig be and hereby is tasked with the migration > and rationalization of the Apache Incubator Shindig podling; and be it > further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Shindig podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > > --- End Proposed Board Resolution --- > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[contribution] Apache MyFaces Trinidad got a new skin (aka look-and-feel)
Hi, for the Apache MyFaces subproject "Trinidad" we got a new contribution: ==> Adonis Raul Raduca (ICLA on file) contributed a new skin, which is basically a look-and-file (a bunch of CSS selectors and some new images). The code has been uploaded to TRINIDAD-1689. Question is: Do we need a software grant for that contribution ? I (personally) think no, we don't. Why? -The contribution is an "improvement" of the existing look-and-feel; -The contribution is not a "standalone" software / donation. In fact the contributions is pretty tied to the Trinidad subproject. It is actually useless without the Trinidad framework at all. Let me know if you guys agree that we do NOT need a software grant for this contribution. -Matthias (PMC Chair of Apache MyFaces) [1] https://issues.apache.org/jira/browse/TRINIDAD-1689 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Missing reports due NOW
On Jan 17, 2010, at 11:28 PM, Noel J. Bergman wrote: > Missing: > > Imperius > Subversion > Thrift > VXQuery > > These were due middle of last week, and are still not present. Imperius report was created this morning and is on the wiki, now. --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Discuss] Apache Cassandra as a TLP
Greetings, The Cassandra community has successfully voted for graduation[1]. Before calling for a recommendation vote, I'd like to see if anyone here has any concerns or objections, or has any feedback on the draft resolution. Regards, [1] http://thread.gmane.org/gmane.comp.db.cassandra.user/1875 -- Eric Evans eev...@rackspace.com X. Establish the Apache Cassandra Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to fully distributed storage of structured data, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Cassandra Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Cassandra Project be and hereby is responsible for the creation and maintenance of software related to fully distributed storage of structured data; and be it further RESOLVED, that the office of "Vice President, Apache Cassandra" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Cassandra Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Cassandra Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Cassandra Project: * Jonathan Ellis * Eric Evans * Jun Rao * Chris Goffinet NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jonathan Ellis be appointed to the office of Vice President, Apache Cassandra, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Cassandra PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Cassandra Project; and be it further RESOLVED, that the Apache Cassandra Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Cassandra podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Cassandra podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Cassandra as a TLP
Hi, On Mon, Jan 18, 2010 at 4:10 PM, Eric Evans wrote: > ...The Cassandra community has successfully voted for graduation[1] > ...[1] http://thread.gmane.org/gmane.comp.db.cassandra.user/1875 Correct me if I'm wrong, but I don't see a vote from any mentor [1] in that thread. The Incubator PMC counts on the mentors to evaluate the podling's readyness and recommend graduation. Not that we don't trust you, but it's a big part the mentors role - so I'd like to hear from them. -Bertrand [1] http://incubator.apache.org/projects/cassandra.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Cassandra as a TLP
On Mon, 2010-01-18 at 16:23 +0100, Bertrand Delacretaz wrote: > Correct me if I'm wrong, but I don't see a vote from any mentor [1] in > that thread. > > The Incubator PMC counts on the mentors to evaluate the podling's > readyness and recommend graduation. Not that we don't trust you, but > it's a big part the mentors role - so I'd like to hear from them. Sure. There was another thread started on cassandra-private (by a mentor), where the mentors voted. I don't know if that is archived, or who would have access, but I'm sure that either way they'll sound off here. -- Eric Evans eev...@rackspace.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Cassandra as a TLP
On Mon, Jan 18, 2010 at 4:34 PM, Eric Evans wrote: > ...There was another thread started on cassandra-private (by a > mentor), where the mentors voted. I don't know if that is archived, or > who would have access, but I'm sure that either way they'll sound off > here Cool - let's hear what they have to say then! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Kevan, > Time to restart/finish this discussion. I agree. Seems that things have cooled off a bit. > Personally, I'd have been happy to see this move forward either way > 1) IP clearance with implementation work in Commons This works only if we're dealing with a CODEBASE and an existing ASF community that takes over it, albeit with the addition of a small number of new members who are part of, but not the entire, developer base for the code. > 2) Incubator project with graduation to Commons (or other TLP). This is the correct path if we need to incubate a community. Again, to summarize: we CLEAR code, we INCUBATE communities. > We seem to have talked our way into doing nothing. Option 3 is probably not the correct choice. :-) > The Geronimo project is going to need a Bean Validation implementation for EE6 > compliance. So, I'm confident that there is enough interest to create an > implementation at Apache. I'd prefer that it end up in Commons (since this > is really an SE technology). However, I can start discussions in the Geronimo > community, if that's what it takes. That would be great, but given the criteria above, which direction do you feel that this promotes? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report January 2010
The Incubator appears to be running smoothly, with nothing regarding Board level attention. Shindig, Cassandra and UIMA are all talking about graduating. Shindig was voted on last week, with the vote closed this morning in time to try to make the Board meeting. Cassandra, which is not reporting this period, is discussing graduation to TLP status. As noted separately, below, UIMA is preparing to graduate in the very near future. Proposed or newly entered: OODT --- a grid middleware framework for science data processing, information integration, and retrieval Lucene Connector Framework JPPF : a parallel processing framework for Java There is a 4th proposal, which resulted in some discussion regarding (code) clearance vs (community) incubation. It should be resolved shortly so that the project can move forward. Subversion, rather ironically, given the membership of the project, failed to provide a monthly report for January. Thrift also failed to report. Notes on each are below. - = Ace = Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community * Toni Menzel accepted our invitation to become a committer, after considerable contributions since the start of ACE which include support for launching using Pax Runner, various patches and the migration to Maven. * Brian Topping accepted our invitation to become a committer, after learning about ACE at ApacheCon US 2009. Brian is helping out with the migration to Maven. * Jean-Baptiste Onofre accepted our invitation to become a committer, after approaching us to work together on integrating ACE with AutoDeploy/Kalumet. He has since also helped out with the migration to Maven. * Marcel Offermans presented ACE at the ApacheCon US 2009 as part of the OSGi track Software * Migrating from an Ant based build to Maven. Current trunk holds both builds. * Currently its about aligning the Maven output with their Ant originals. After that, the ant project will be moved out/removed. (Overview: ACE-62) * CI build is going to be moved to the Hudson grid. (see ACE-71). Awaiting account creation in INFRA-2419. * Agreed on new terminology for some of the core concepts in ACE after Carsten started a broad discussion about them. Licensing and other issues * None at the moment. Things to resolve prior to graduation * Make a release * Grow the community some more = Bluesky = BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. Last month we tried to pack the release candidate package and place it at http://people.apache.org/~mabowen/. However, we made some mistakes when producing the package, first, a improper version number, second, forget to start a release audit before making the release candidate package. These faults are the things we'd restore the nxet step as soon as possible. top 2 or 3 to resolve prior to graduation: * Complete the release audit and clarify the last legal issues; * Revise the release version number and repack the release candidate; * Start a new round of release vote at bluesky dev-mailing list; = Chemistry = Apache Chemistry is an effort to provide a Java (and possibly others, like !JavaScript) implementation of the upcoming CMIS specification. Chemistry entered incubation on April 30th, 2009. There are currently no issues requiring board or Incubator PMC attention. Community * Another project (OpenCMIS) targetting a Java implementation of CMIS, like Chemistry, has been proposed to the Incubator. Discussions between OpenCMIS and Chemistry developers have identified areas of possible collaboration but the OpenCMIS incubation status has not moved forward. * Chemistry is now being used by companies or individuals outside the initial developers. Development * Development continues at a steady pace, mostly driven by Florent Guillaume. * Chemistry now targets CMIS 1.0 CD 05 draft, soon to be 06. * Nuxeo will contribute a command-line shell for CMIS in a few days. * SOAP bindings are planned in the coming days as well. Issues before graduation * Stabilize the general interest into a sustainable development community. * Set up Hudson builds. * Create an Apache release of the Chemistry codebase. = Clerezza = Clerezza (incubating since November 27th, 2009) is an OSGi-based modular application and set of components (bundles) for building RESTFul Semantic Web applications and services. . The are currently no issues requiring board attention. Recent activity: * All the Clerezza code has been imported in t
Re: Incubator Board Report January 2010
On 01/18/2010 09:35 AM, Noel J. Bergman wrote: The Incubator appears to be running smoothly, with nothing regarding Board level attention. Maybe it doesn't require the boards attention, but Traffic Server would like to resolve the TradeMark issues. Who would be able to make this call? Thanks! -- Leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Imperius 1.0.0 rc6
I downloaded the Unix files, verified signatures, spot checked some files for accuracy and built Imperius. I noticed that your key has not been signed by anyone, although its not a requirement, its nice to have. +1 to release Imperius (binding) On Dec 14, 2009, at 4:41 PM, Neeraj Joshi wrote: > The Imperius community voted on and approved the release of Apache > Imperius 1.0.0. > We would now like to request the approval of the Incubator PMC for this > release. > > Imperius is a rule-based policy evaluation engine based on the CIM-SPL > language from > Distributed Management Task Force (dtmf.org). > > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > notes can be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is 887217 > > In addition, my PGP public code signing key can be found at the MIT > key server (http://pgp.mit.edu/) > > The KEYS file is checked in at > http://svn.apache.org.repos/asf/incubator/imperius/KEYS > > Please vote to publish this release by Tuesday, Dec 17 18:00 EST., > please include the testing you performed to arrive at your vote > [ ] +1 Publish > [ ] 0 Abstain > [ ] -1 Don't publish, because... > > > Below is a summary of the vote on the Imperius mailing list (and further > below is the original vote email) > > Thanks > Neeraj > > > ~ > Neeraj Joshi (knee-rudge) > > IBM WebSphere ComputeGrid > > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/14/2009 03:45 PM > Subject: > [VOTE][RESULT] Imperius 1.0.0 rc6 > > > > Hello All, > > Voting on the Imperius 1.0.0rc6 candidate release has concluded > > Results: > 1 binding +1 vote > > 6 non-binding +1 votes > > Kevan Miller(*) +1 > > David Kaminsky +1 > David Wood +1 > Mark Carlson +1 > Erik Bengston +1 > Xiping Wang +1 > Jorge Lobo +1 > > Comments received: > > 1. Comments from Erik Bengston > >> - In the zip/tar file we have a /log.txt file that should be removed. >> - Inside the jars we have a /META-INF/maven that should be removed too. >> - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt >> - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to >> samples/lib/javaspl-samples-1.0.0.jar >> - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in >> META-INF folder. > > It was concluded that it is too early to make all/any Apache Imperius > artifacts available in the Maven > repository > > The other issues did not violate Apache policies and would be accommodated > > in subsequent releases. > > > > 2. Comments from Kevan Miller > >> I note that the source distribution contains the following file: > imperius-cimsplclientsideprovider/customexpressions.properties which >is > not in the svn tag. The contents of this file are: > >> SPL_CUSTOM_EXPRESSIONS >> SPL_CUSTOM_ACTIONS > > This file is innocuous and gets generated during JUnit testing > > > I will now take this vote to the general mailing list for a final vote. > We still need 2 +1 votes from IPMC members. > > Thanks > Neeraj > > > > ~ > Neeraj Joshi (knee-rudge) > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/04/2009 10:06 AM > Subject: > [VOTE] Imperius 1.0.0 rc6 > > > > Hi All, > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > > notes can > be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is 887217 > > In addition, my PGP public code signing key can be found at the MIT > key server (http://pgp.mit.edu/) > > The KEYS file is checked in at > http://svn.apache.org.repos/asf/incubator/imperius/KEYS > > Please vote to publish this release by Tuesday, Dec 08 18:00 EST., > please include the testing you performed to arrive at your vote > [ ] +1 Publish > [ ] 0 Abstain > [ ] -1 Don't publish, because... > > Upon a positive majority of binding votes and no binding vetoes, the > results of this vote will be brought to the Incubator PMC and voted > upon there. > > Thanks, > -Neeraj > > Change log: > 1. Checked in the build.xml from the release artifact into the SVN tag. > Al
[VOTE] Accept OODT for Incubation
Per the previous proposal that was sent to gene...@incubator, I'd like to now call a vote for accepting OODT into the Incubator. [ ] +1 - Accept OODT into the Incubator [ ] -1 - Do not accept OODT into the Incubator (rationale strongly desired!) Per the proposal below, the mentors for this proposal are myself, Ross, Jean-Frederic, and Ian. Unless there are any extenuating circumstances, I will close this vote on Thursday morning, January 21. Thanks. -- justin http://wiki.apache.org/incubator/OODTProposal OODT, a grid middleware framework for science data processing, information integration, and retrieval. Abstract OODT is a grid middleware framework used on a number of successful projects at NASA's Jet Propulsion Laboratory/California Institute of Technology, and many other research institutions and universities, specifically those part of the: National Cancer Institute's (NCI's) Early Detection Research Network (EDRN) project - over 40+ institutions all performing research into discovering biomarkers which are early indicators of disease. NASA's Planetary Data System (PDS) - NASA's planetary data archive, a repository and registry for all planetary data collected over the past 30+ years. various Earth Science data processing missions, including Seawinds/QuickSCAT, the Orbiting Carbon Observatory, the NPP Sounder PEATE project, and the Soil Moisture Active Passive (SMAP) mission. >From the OODT website: It's middleware for metadata: Transparent access to distributed resources Data discovery and query optimization Distributed processing and virtual archives It's a software architecture: Models for information representation Solutions to knowledge capture problems Unification of technology, data, and metadata Proposal OODT is an established open source project, with 9+ years of existence, and deployment at universities, federal research institutions, other NASA centers, and the NIH (it won runner-up NASA software of the year in 2003). It has a strong community of those that operate and support its growth. Our proposal is to bring OODT into Apache to strengthen its support and its capabilities even further on the laurels of Apache's brand and its growing huge community of developers from all over the world. In short, bringing OODT into Apache will significantly enhance OODT's widespread use, will likely improve its codebase, and furthermore will help Apache philosophy and community spread into OODT's already large community-base reaching across government, academia and industry. OODT will be, to the best of our knowledge, the first grid community project to bear the Apache brand. By grid technology, we mean a technology that provides the ability to create virtual organizations, as originally described by Kesselman and Foster in their seminal paper on grid computing. OODT provides both computational and data grid support, and is built with a component-philosophy. OODT includes components that allow for virtual information integration across organizations (provided by the Profile, Product and Query server components), and that allow for distributed data management and processing across heterogeneous virtual organizations (provided by the Catalog and Archive Service set of components, including File Manager, Workflow Manager and Resource Manager). Each set of components exist as independently organized Maven2 projects, that reference each other (where appropriate), forming a layered set of components and a framework for grid computing. Background OODT is an established project within JPL and in use at several NASA centers, as well as univerities, and other government organizations and industrial collaborations. Chris Mattmann, a JPL employee, and ASF PMC (Lucene) and Committer (Nutch, Tika), has been working for the past 2 years on obtaining the necessary permission from JPL to release OODT into Apache. After initially being stalled, JPL has granted permission to allow OODT into Apache. Through his academic relationship with Justin Erekrantz, Apache President, and through their collective Ph.D. studies, OODT has been discussed between Chris and Justin on several occasions, and Justin offered to help champion OODT into the Apache Incubator when JPL was ready to release OODT. In December 2009, that permission was granted. This proposal is the result of the above efforts and related discussions. Some alternatives to incubation, like Apache Labs came up during the discussions but we believe that taking the project to the Incubator is the best way to start growing a viable Apache-based community to sustain OODT. Furthermore, given its larger code base and existing sub-projects, the goal would be for OODT to leverage the incubator to graduate into Apache's first top-level grid project, rather than graduate into a sub-project of an existing TLP. Rationale Grid computing has been around for the past 10 years and has gained widespread notoriety and attention in industry and academia. Scientific
Re: Missing reports due NOW
On Mon, Jan 18, 2010 at 5:28 AM, Noel J. Bergman wrote: > Missing: > > Subversion Hmm. Something went wrong with the automated notifier as this ball got dropped, I guess. Subversion should have something submitted by this evening. -- justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r900498 - /incubator/public/trunk/site-publish/projects/jspwiki.html
Did you forget to commit the changes to the xml source? iincubator/site-author/projects/jspwiki.xml -David > Author: metskem > Date: Mon Jan 18 18:28:35 2010 > New Revision: 900498 > > URL: http://svn.apache.org/viewvc?rev=900498&view=rev > Log: > issue JSPWIKI-544 (IP Proces Documentation) completed > > Modified: > incubator/public/trunk/site-publish/projects/jspwiki.html > > Modified: incubator/public/trunk/site-publish/projects/jspwiki.html > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/projects/jspwiki.html?rev=900498&r1=900497&r2=900498&view=diff > == > --- incubator/public/trunk/site-publish/projects/jspwiki.html [utf-8] > (original) > +++ incubator/public/trunk/site-publish/projects/jspwiki.html [utf-8] Mon Jan > 18 18:28:35 2010 > @@ -462,7 +462,7 @@ > Project Specific > > > -Project specific items sorted by status, lastupdate. Here is the href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?pid=12310732&fixfor=12313986&sorter/field=priority&sorter/order=DESC";>Complete > List > +Project specific items sorted by status, last update. Here is the href="https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?pid=12310732&fixfor=12313986&sorter/field=priority&sorter/order=DESC";>Complete > List > > >Last Update > @@ -485,12 +485,6 @@ > >2009-05-24 >Open > - Document IP process > - href="https://issues.apache.org/jira/browse/JSPWIKI-544";>JSPWIKI-544 > - > - > - 2009-05-24 > - Open >Project ready to comply with ASF mirroring guidelines > href="https://issues.apache.org/jira/browse/JSPWIKI-557";>JSPWIKI-557 > > @@ -525,6 +519,12 @@ > href="https://issues.apache.org/jira/browse/JSPWIKI-538";>JSPWIKI-538 > > > + 2010-01-18 > + Complete > + Document IP process > + href="https://issues.apache.org/jira/browse/JSPWIKI-544";>JSPWIKI-544 > + > + >2009-10-01 >Complete >Engagement by the incubated community with the other ASF > communities > @@ -715,4 +715,4 @@ > > > > - > + > \ No newline at end of file > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-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] Imperius 1.0.0 rc6
+1 ...ant On Mon, Dec 14, 2009 at 9:41 PM, Neeraj Joshi wrote: > The Imperius community voted on and approved the release of Apache > Imperius 1.0.0. > We would now like to request the approval of the Incubator PMC for this > release. > > Imperius is a rule-based policy evaluation engine based on the CIM-SPL > language from > Distributed Management Task Force (dtmf.org). > > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > notes can be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is 887217 > > In addition, my PGP public code signing key can be found at the MIT > key server (http://pgp.mit.edu/) > > The KEYS file is checked in at > http://svn.apache.org.repos/asf/incubator/imperius/KEYS > > Please vote to publish this release by Tuesday, Dec 17 18:00 EST., > please include the testing you performed to arrive at your vote > [ ] +1 Publish > [ ] 0 Abstain > [ ] -1 Don't publish, because... > > > Below is a summary of the vote on the Imperius mailing list (and further > below is the original vote email) > > Thanks > Neeraj > > > ~ > Neeraj Joshi (knee-rudge) > > IBM WebSphere ComputeGrid > > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/14/2009 03:45 PM > Subject: > [VOTE][RESULT] Imperius 1.0.0 rc6 > > > > Hello All, > > Voting on the Imperius 1.0.0rc6 candidate release has concluded > > Results: > 1 binding +1 vote > > 6 non-binding +1 votes > > Kevan Miller(*) +1 > > David Kaminsky +1 > David Wood +1 > Mark Carlson +1 > Erik Bengston +1 > Xiping Wang +1 > Jorge Lobo +1 > > Comments received: > > 1. Comments from Erik Bengston > >>- In the zip/tar file we have a /log.txt file that should be removed. >>- Inside the jars we have a /META-INF/maven that should be removed too. >>- imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt >>- IMO, the lib/javaspl-samples-1.0.0.jar should be moved to >>samples/lib/javaspl-samples-1.0.0.jar >>- IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in >>META-INF folder. > > It was concluded that it is too early to make all/any Apache Imperius > artifacts available in the Maven > repository > > The other issues did not violate Apache policies and would be accommodated > > in subsequent releases. > > > > 2. Comments from Kevan Miller > >>I note that the source distribution contains the following file: > imperius-cimsplclientsideprovider/customexpressions.properties which >is > not in the svn tag. The contents of this file are: > >>SPL_CUSTOM_EXPRESSIONS >>SPL_CUSTOM_ACTIONS > > This file is innocuous and gets generated during JUnit testing > > > I will now take this vote to the general mailing list for a final vote. > We still need 2 +1 votes from IPMC members. > > Thanks > Neeraj > > > > ~ > Neeraj Joshi (knee-rudge) > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/04/2009 10:06 AM > Subject: > [VOTE] Imperius 1.0.0 rc6 > > > > Hi All, > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > > notes can > be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is 887217 > > In addition, my PGP public code signing key can be found at the MIT > key server (http://pgp.mit.edu/) > > The KEYS file is checked in at > http://svn.apache.org.repos/asf/incubator/imperius/KEYS > > Please vote to publish this release by Tuesday, Dec 08 18:00 EST., > please include the testing you performed to arrive at your vote > [ ] +1 Publish > [ ] 0 Abstain > [ ] -1 Don't publish, because... > > Upon a positive majority of binding votes and no binding vetoes, the > results of this vote will be brought to the Incubator PMC and voted > upon there. > > Thanks, > -Neeraj > > Change log: > 1. Checked in the build.xml from the release artifact into the SVN tag. > All the release artifacts > from previous candidate (r5) are the same. > 2. Updated the SVN revision number. > 3. Left the redundant zip/gz files as is. > ~ > "It is hard enough to remember my opinions, without also remembering my > reasons for them". -Fried
[RESULT] Imperius 1.0.0 rc6
Hi All, We have 3 binding +1 votes Kevan Miller Ant Elder Matt Hogstrom The vote passes! We will work on making the release artifacts publicly available. Thanks Kevan, Ant, Matt and everyone who helped us with this release! Regards Neeraj ~ "It is hard enough to remember my opinions, without also remembering my reasons for them". -Friedrich Wilhelm Nietzsche Neeraj Joshi (knee-rudge) WebSphere XD - Compute Grid AIM, IBM Apache Imperius - http://incubator.apache.org/imperius ~ From: Matt Hogstrom To: general@incubator.apache.org Date: 01/18/2010 02:25 PM Subject: Re: [VOTE] Imperius 1.0.0 rc6 I downloaded the Unix files, verified signatures, spot checked some files for accuracy and built Imperius. I noticed that your key has not been signed by anyone, although its not a requirement, its nice to have. +1 to release Imperius (binding) On Dec 14, 2009, at 4:41 PM, Neeraj Joshi wrote: > The Imperius community voted on and approved the release of Apache > Imperius 1.0.0. > We would now like to request the approval of the Incubator PMC for this > release. > > Imperius is a rule-based policy evaluation engine based on the CIM-SPL > language from > Distributed Management Task Force (dtmf.org). > > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > notes can be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is 887217 > > In addition, my PGP public code signing key can be found at the MIT > key server (http://pgp.mit.edu/) > > The KEYS file is checked in at > http://svn.apache.org.repos/asf/incubator/imperius/KEYS > > Please vote to publish this release by Tuesday, Dec 17 18:00 EST., > please include the testing you performed to arrive at your vote > [ ] +1 Publish > [ ] 0 Abstain > [ ] -1 Don't publish, because... > > > Below is a summary of the vote on the Imperius mailing list (and further > below is the original vote email) > > Thanks > Neeraj > > > ~ > Neeraj Joshi (knee-rudge) > > IBM WebSphere ComputeGrid > > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/14/2009 03:45 PM > Subject: > [VOTE][RESULT] Imperius 1.0.0 rc6 > > > > Hello All, > > Voting on the Imperius 1.0.0rc6 candidate release has concluded > > Results: > 1 binding +1 vote > > 6 non-binding +1 votes > > Kevan Miller(*) +1 > > David Kaminsky +1 > David Wood +1 > Mark Carlson +1 > Erik Bengston +1 > Xiping Wang +1 > Jorge Lobo +1 > > Comments received: > > 1. Comments from Erik Bengston > >> - In the zip/tar file we have a /log.txt file that should be removed. >> - Inside the jars we have a /META-INF/maven that should be removed too. >> - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt >> - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to >> samples/lib/javaspl-samples-1.0.0.jar >> - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in >> META-INF folder. > > It was concluded that it is too early to make all/any Apache Imperius > artifacts available in the Maven > repository > > The other issues did not violate Apache policies and would be accommodated > > in subsequent releases. > > > > 2. Comments from Kevan Miller > >> I note that the source distribution contains the following file: > imperius-cimsplclientsideprovider/customexpressions.properties which >is > not in the svn tag. The contents of this file are: > >> SPL_CUSTOM_EXPRESSIONS >> SPL_CUSTOM_ACTIONS > > This file is innocuous and gets generated during JUnit testing > > > I will now take this vote to the general mailing list for a final vote. > We still need 2 +1 votes from IPMC members. > > Thanks > Neeraj > > > > ~ > Neeraj Joshi (knee-rudge) > Apache Imperius - http://incubator.apache.org/imperius > ~ > > > > From: > Neeraj Joshi/Durham/i...@ibmus > To: > imperius-...@incubator.apache.org > Date: > 12/04/2009 10:06 AM > Subject: > [VOTE] Imperius 1.0.0 rc6 > > > > Hi All, > > The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, > and is ready for a vote. The artifacts, KEYS file, RAT report and release > > > notes can > be found at > > http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ > > The tag from which the release artifacts were generated can be found > at > > http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ > > Revision no is
Re: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Jan 18, 2010, at 11:30 AM, Noel J. Bergman wrote: > Kevan, > >> Time to restart/finish this discussion. > > I agree. Seems that things have cooled off a bit. > >> Personally, I'd have been happy to see this move forward either way > >> 1) IP clearance with implementation work in Commons > > This works only if we're dealing with a CODEBASE and an existing ASF > community that takes over it, albeit with the addition of a small number of > new members who are part of, but not the entire, developer base for the > code. > >> 2) Incubator project with graduation to Commons (or other TLP). > > This is the correct path if we need to incubate a community. > > Again, to summarize: we CLEAR code, we INCUBATE communities. > >> We seem to have talked our way into doing nothing. > > Option 3 is probably not the correct choice. :-) :) There's a sliding scale between those 2 options. And people may have their own evaluation of where this instance falls. Summarizing the issues: There's an existing Commons Validator component. However, it's been mostly dormant. Commons provides the necessary oversight of the project, but there is small community of Commons committers working on the Validator component. AFAICT, there is not enough interest in the Commons community to implement the latest Bean Validation specification, on their own. There's a partial (85%) implementation of the new JSR 303 Bean Validation Specification that Agimatec would like to donate to the ASF. Using the initial committers list as a guide to the "community" that would be formed around this codebase: there is one Commons PMC member/committer, 6 ASF committers (but not Commons committers), and 2 non-ASF committers. I think we'd agree that a fair amount of community building will be required for this new codebase and group of committers. A motivated TLP might be able to provide the necessary oversight to build this new community. However, given the small makeup of the Commons Validator community, I don't think it's reasonable to expect the Commons community to do this community building. IMO, Incubator should support the creation of a new Validation project at incubator and let's start the community building... > >> The Geronimo project is going to need a Bean Validation implementation for > EE6 >> compliance. So, I'm confident that there is enough interest to create an >> implementation at Apache. I'd prefer that it end up in Commons (since this >> is really an SE technology). However, I can start discussions in the > Geronimo >> community, if that's what it takes. > > That would be great, but given the criteria above, which direction do you > feel that this promotes? It only provides an alternative TLP which might have the necessary interest in building a community around this new codebase. If we are stuck in a stand-off between Commons and Incubator, this might be an alternative. However, I certainly hope it doesn't come to this... --kevan
Re: [Discuss] Apache Cassandra as a TLP
Yeah, the dicussion started on private as Eric mentioned and that's what triggered the vote on d...@. We should really have re-voted the dev thread to avoid confusion. Anyhow, my strong opinion is that Cassandra is ready. Great community, great contributors, dynamic and fast moving without compromising stability. I personally have no hesitation. By the way if you have a few minutes, some feedback about the resolution that Eric attached would be cool. Thanks, Matthieu On Mon, Jan 18, 2010 at 7:37 AM, Bertrand Delacretaz wrote: > On Mon, Jan 18, 2010 at 4:34 PM, Eric Evans wrote: > > ...There was another thread started on cassandra-private (by a > > mentor), where the mentors voted. I don't know if that is archived, or > > who would have access, but I'm sure that either way they'll sound off > > here > > Cool - let's hear what they have to say then! > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Missing reports due NOW
On Jan 18, 2010, at 2:20 PM, Justin Erenkrantz wrote:
> On Mon, Jan 18, 2010 at 5:28 AM, Noel J. Bergman wrote:
>> Missing:
>>
>>Subversion
>
> Hmm. Something went wrong with the automated notifier as this ball
> got dropped, I guess. Subversion should have something submitted by
> this evening. -- justin
The automated notifier ("Marvin"?) sent it's notification on Jan. 1, and it was
promptly missed in all the post-holiday revelry.
-Hyrum
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Handling of Traffic Server Trademark
Leif Hedstrom wrote: > Traffic Server would like to resolve the TradeMark issues. > Who would be able to make this call? The relevant content is: > Y! holds several TMs for the name "Traffic Server", most of which > expires soon. Our legal team has proposed two possible solutions, > the first being the easiest for us. >1. Yahoo! provides ASF with a letter of assurance stating that we > own all right, title and interest in and to the TRAFFIC SERVER > mark and the four active registrations and that we will not take > any action against ASF or any of its licensees during the life of > these registrations (and we'd express our intention of letting > them lapse and expire in this letter). >2. Yahoo! will assign all right, title and interest in and to the > TRAFFIC SERVER mark including the four active registrations to > ASF [though we'd probably want to make this contingent on getting > through the incubator stage]. We can run this through Apache Legal, but my take is that we'd prefer option #2, which is the same route that I believe was previously used for SpamAssassin. One issue, as I understand it, is that the ASF probably should not be letting marks lapse, and should be maintaining them. But those aspects ought to be ASF-wide, and would come from Apache Legal. Does anyone else have an opinion? Please do offer it. :-) --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Kevan Miller wrote: > I think we'd agree that a fair amount of community building will be > required for this new codebase and group of committers. [However,] > given the small makeup of the Commons Validator community, I don't > think it's reasonable to expect the Commons community to do this > community building. That seems a cogent enough explanation to warrant Incubation. Thank you. I also believe that when you talk about multiple projects collaborating actively on a shared, but separately useable, codebase, a TLP is often justified. As an aside, any issues that might relate to the Commons TLP, itself, are outside the scope of the Incubator, and should be addressed elswhere. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Handling of Traffic Server Trademark
> -Original Message- > From: Noel J. Bergman [mailto:n...@devtech.com] > Sent: Tuesday, 19 January 2010 12:51 PM > To: general@incubator.apache.org > Subject: Handling of Traffic Server Trademark > > Leif Hedstrom wrote: > > > Traffic Server would like to resolve the TradeMark issues. > > Who would be able to make this call? > > The relevant content is: > > > Y! holds several TMs for the name "Traffic Server", most of which > > expires soon. Our legal team has proposed two possible solutions, > > the first being the easiest for us. > > >1. Yahoo! provides ASF with a letter of assurance stating that we > > own all right, title and interest in and to the TRAFFIC SERVER > > mark and the four active registrations and that we will not > take > > any action against ASF or any of its licensees during the life > of > > these registrations (and we'd express our intention of letting > > them lapse and expire in this letter). > > >2. Yahoo! will assign all right, title and interest in and to the > > TRAFFIC SERVER mark including the four active registrations to > > ASF [though we'd probably want to make this contingent on > getting > > through the incubator stage]. > > We can run this through Apache Legal, but my take is that we'd prefer > option > #2, which is the same route that I believe was previously used for > SpamAssassin. > > One issue, as I understand it, is that the ASF probably should not be > letting marks lapse, and should be maintaining them. But those aspects > ought to be ASF-wide, and would come from Apache Legal. > > Does anyone else have an opinion? Please do offer it. :-) Can I suggest this question gets asked on tradema...@apache.org list. I believe all trademark issues should go there, if needed they would refer to legal as and when. I haven't followed the history of this thread, so don't know if http://apache.org/foundation/marks/ has been pointed to yet. Gav... > > --- 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: [VOTE] Accept OODT for Incubation
On Tue, Jan 19, 2010 at 4:17 AM, Justin Erenkrantz wrote: > Per the previous proposal that was sent to gene...@incubator, I'd like > to now call a vote for accepting OODT into the Incubator. [x] +1 - Accept OODT into the Incubator [ ] -1 - Do not accept OODT into the Incubator (rationale strongly desired!) Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Incubator Board Report January 2010
Amended with Subversion. It is entirely up to the Board if they wish to accept this after-deadline addition. --- Noel -Original Message- From: Noel J. Bergman [mailto:n...@devtech.com] Sent: Monday, January 18, 2010 11:36 To: bo...@apache.org Cc: general@incubator.apache.org Subject: Incubator Board Report January 2010 The Incubator appears to be running smoothly, with nothing regarding Board level attention. Shindig, Cassandra and UIMA are all talking about graduating. Shindig was voted on last week, with the vote closed this morning in time to try to make the Board meeting. Cassandra, which is not reporting this period, is discussing graduation to TLP status. As noted separately, below, UIMA is preparing to graduate in the very near future. Proposed or newly entered: OODT --- a grid middleware framework for science data processing, information integration, and retrieval Lucene Connector Framework JPPF : a parallel processing framework for Java There is a 4th proposal, which resulted in some discussion regarding (code) clearance vs (community) incubation. It should be resolved shortly so that the project can move forward. Subversion, rather ironically, given the membership of the project, failed to provide a monthly report for January. Thrift also failed to report. Notes on each are below. - = Ace = Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community * Toni Menzel accepted our invitation to become a committer, after considerable contributions since the start of ACE which include support for launching using Pax Runner, various patches and the migration to Maven. * Brian Topping accepted our invitation to become a committer, after learning about ACE at ApacheCon US 2009. Brian is helping out with the migration to Maven. * Jean-Baptiste Onofre accepted our invitation to become a committer, after approaching us to work together on integrating ACE with AutoDeploy/Kalumet. He has since also helped out with the migration to Maven. * Marcel Offermans presented ACE at the ApacheCon US 2009 as part of the OSGi track Software * Migrating from an Ant based build to Maven. Current trunk holds both builds. * Currently its about aligning the Maven output with their Ant originals. After that, the ant project will be moved out/removed. (Overview: ACE-62) * CI build is going to be moved to the Hudson grid. (see ACE-71). Awaiting account creation in INFRA-2419. * Agreed on new terminology for some of the core concepts in ACE after Carsten started a broad discussion about them. Licensing and other issues * None at the moment. Things to resolve prior to graduation * Make a release * Grow the community some more = Bluesky = BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. Last month we tried to pack the release candidate package and place it at http://people.apache.org/~mabowen/. However, we made some mistakes when producing the package, first, a improper version number, second, forget to start a release audit before making the release candidate package. These faults are the things we'd restore the nxet step as soon as possible. top 2 or 3 to resolve prior to graduation: * Complete the release audit and clarify the last legal issues; * Revise the release version number and repack the release candidate; * Start a new round of release vote at bluesky dev-mailing list; = Chemistry = Apache Chemistry is an effort to provide a Java (and possibly others, like !JavaScript) implementation of the upcoming CMIS specification. Chemistry entered incubation on April 30th, 2009. There are currently no issues requiring board or Incubator PMC attention. Community * Another project (OpenCMIS) targetting a Java implementation of CMIS, like Chemistry, has been proposed to the Incubator. Discussions between OpenCMIS and Chemistry developers have identified areas of possible collaboration but the OpenCMIS incubation status has not moved forward. * Chemistry is now being used by companies or individuals outside the initial developers. Development * Development continues at a steady pace, mostly driven by Florent Guillaume. * Chemistry now targets CMIS 1.0 CD 05 draft, soon to be 06. * Nuxeo will contribute a command-line shell for CMIS in a few days. * SOAP bindings are planned in the coming days as well. Issues before graduation * Stabilize the general interest into a sustainable development community. * Set up Hudson builds. * Create an Apache release of
Re: Missing reports due NOW
As far as I know we (empire-db) also did not receive a notification.
Cheers,
Francis
On Tue, Jan 19, 2010 at 3:00 AM, Hyrum K. Wright
wrote:
>
> On Jan 18, 2010, at 2:20 PM, Justin Erenkrantz wrote:
>
>> On Mon, Jan 18, 2010 at 5:28 AM, Noel J. Bergman wrote:
>>> Missing:
>>>
>>> Subversion
>>
>> Hmm. Something went wrong with the automated notifier as this ball
>> got dropped, I guess. Subversion should have something submitted by
>> this evening. -- justin
>
> The automated notifier ("Marvin"?) sent it's notification on Jan. 1, and it
> was promptly missed in all the post-holiday revelry.
>
> -Hyrum
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OODT for Incubation
On Mon, Jan 18, 2010 at 9:17 PM, Justin Erenkrantz wrote: > Per the previous proposal that was sent to gene...@incubator, I'd like > to now call a vote for accepting OODT into the Incubator. > > [X] +1 - Accept OODT into the Incubator > [ ] -1 - Do not accept OODT into the Incubator (rationale strongly desired!) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Handling of Traffic Server Trademark
On 01/19/2010 03:50 AM, Noel J. Bergman wrote: > Leif Hedstrom wrote: > >> Traffic Server would like to resolve the TradeMark issues. >> Who would be able to make this call? > > The relevant content is: > >> Y! holds several TMs for the name "Traffic Server", most of which >> expires soon. Our legal team has proposed two possible solutions, >> the first being the easiest for us. > >>1. Yahoo! provides ASF with a letter of assurance stating that we >> own all right, title and interest in and to the TRAFFIC SERVER >> mark and the four active registrations and that we will not take >> any action against ASF or any of its licensees during the life of >> these registrations (and we'd express our intention of letting >> them lapse and expire in this letter). > >>2. Yahoo! will assign all right, title and interest in and to the >> TRAFFIC SERVER mark including the four active registrations to >> ASF [though we'd probably want to make this contingent on getting >> through the incubator stage]. > > We can run this through Apache Legal, but my take is that we'd prefer option > #2, which is the same route that I believe was previously used for > SpamAssassin. +1 > > One issue, as I understand it, is that the ASF probably should not be > letting marks lapse, and should be maintaining them. But those aspects > ought to be ASF-wide, and would come from Apache Legal. Sure. Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OODT for Incubation
On 01/18/2010 09:17 PM, Justin Erenkrantz wrote: > Per the previous proposal that was sent to gene...@incubator, I'd like > to now call a vote for accepting OODT into the Incubator. > > [X] +1 - Accept OODT into the Incubator Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
