Re: [ANNOUNCE] Christian Müller joins the IPMC
Congrats! :) On Thu, Oct 3, 2013 at 11:49 AM, Christian Müller christian.muel...@gmail.com wrote: Thanks for the warm welcome. Because I'm a newbie here, be aware of stupid questions... ;-) Best, Christian Am 03.10.2013 08:02 schrieb Romain Manni-Bucau rmannibu...@gmail.com: Congrats! *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/3 Jean-Louis MONTEIRO jeano...@gmail.com Congrats Christian. Jean Louis Le 3 oct. 2013 01:20, Marvin Humphrey mar...@rectangular.com a écrit : Apache Member and Apache Camel PMC Chair Christian Müller has joined the Incubator PMC. Welcome! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [ANNOUNCE] Jake Farrell joins the Incubator PMC
Welcome aboard On Sep 6, 2013 2:55 AM, David Nalley da...@gnsa.us wrote: Hi Folks, The IPMC has VOTEd to add Jake Farrell as an Apache Incubator PMC. Welcome Jake! --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Change of Chair
Thanks Benson for all what you have done for the IPMC On Fri, Jun 14, 2013 at 7:41 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Welcome, Marvin! :) Cheers, Chris ++ 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 ++ -Original Message- From: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 13, 2013 7:31 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Change of Chair On Thu, Jun 13, 2013 at 2:03 PM, Benson Margulies bimargul...@gmail.com wrote: I have tendered my resignation as VP, Incubator. The PMC has recommend Marvin Humphrey as my successor in a motion submitted to the Foundation board for consideration at the meeting next week. Thank you for serving as Chair, Benson. I have very much enjoyed participating in the Incubator during your time in office. Thanks as well to everyone who has contributed to the Incubator over the years for having taught me so much, collectively; and thanks to the current members of the IPMC for honoring me with the Chair's responsibilities. I love my career as an open-source developer and I'm glad for the chances the Incubator provides to foster successful projects and make it easier for others to take the same path. For those reading this list who are not yet familiar with the role that a PMC Chair plays in the governance of a typical Apache project, the most visible task is to deliver a report to the Apache Software Foundation's Board of Directors every three months. Aside from that, the Chair generally participates in project development as an ordinary member of the PMC. Under normal circumstances, it is not a demanding job. http://www.apache.org/dev/pmc.html#chair The Incubator is different because it reports monthly and aggregates the reports of many podlings. Our report is the closest thing the Incubator has to a product, and when done well, it offers substantial value by keeping us coordinated and focused. However, well-done Incubator reports have historically required substantial individual effort by the Chair. My primary goal as Chair will be to streamline the report procedure. I hope to build institutions and increase automation in order that the Incubator may deliver consistently high-quality reports month after month regardless of any one person's availability as the board meeting approaches. Some ASF projects elect their PMC Chair annually; for others, the Chair may serve for an indefinite period. I have proposed to serve for six months and then make way for someone else -- both because I have other projects I am putting on hold and will want to return to, and because experience has taught me that rotating multiple people through a leadership role enriches the community and deepens involvement. If all goes well, perhaps my successor will not have to work as hard as I will to live up to the standards set by my predecessors. Marvin Humphrey - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
Hi The proposal is well detailed and very informative, the purpose of the projects fits ASF's Cloud Ecosystem and the community is very promising already reminds me with the one of ACS. Very looking forward to start rolling the podling tasks On Tue, Jun 11, 2013 at 11:46 AM, Christian Grobmeier grobme...@gmail.comwrote: Impressive proposal. Reminds me on RH OpenShift actually. Please note the first two links are broken in gmail. They are: * http://www.gartner.com/it-glossary/platform-as-a-service-paas * http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas Anyway, proposal looks really good for me. On Tue, Jun 11, 2013 at 11:10 AM, Ross Gardler rgard...@opendirective.com wrote: It's with great pleasure that I invite the IPMC to review a new proposal [1] for the Apache Incubator. Please let us know if you have any questions or comments - as you will see there are plenty of people on the initial commit list ready and willing to answer your questions. I copy the full text of the proposal for your convenience: = Stratos - A PaaS Framework = == Abstract == Stratos will be a polyglot [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]] framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform-wide insight including monitoring and billing. == Proposal == The Stratos PaaS framework will encompass four layers: 1. An [[ http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic layer that can interface with a wide variety of IaaS systems to provide elastic resources, and for multiple IaaS infrastructures to be automated at one time (hybrid clouds.) 2. A PaaS Controller with a cloud controller that automates and monitors IaaS runtime interactions, distributes artifacts to the underlying runtimes, deploys workloads, directs runtime traffic to the right runtimes using a tenant-aware elastic load balancer, and provides a portal for monitoring and provisioning of tenants on the system. 3. Foundational Services including security, logging, messaging, registry, storage (relational, file, and noSQL), task management, and billing. Foundational services will be loosely-coupled to allow swapping in alternate foundational services. 4. A Cartridge Architecture allowing frameworks, servers, and other runtimes to participate in the advantages of the system. The Cartridge Architecture must support multi-tenant workloads, and provide for various levels of tenant isolation and policy-based control over provisioning. Together these layers offer a foundational layer upon which applications and middleware frameworks can be deployed to speed time-to-market and simplify the development of scalable applications, as well as provide a high level of resource sharing and centralized management that can deliver lowest resource, infrastructure, and management costs. == Background == The Stratos Project has been under development[a] at http://wso2.org under the Apache 2.0 license and the Apache Way governance model since 2010. It initially was focussed on providing PaaS benefits to the users of WSO2 Carbon middleware platform. In version 2.0, to be released in summer 2013, extensive work has been done to clearly separate out the PaaS framework from the products (cartridges) that run on top of it. Stratos now has the ability to run arbitrary workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more. == Rationale == PaaS is in demand by enterprises and organizations of all sizes. The drive towards instance provisioning, high resource utilization and thus low cost, combined with a wide platform of general-purpose services to build on, PaaS has the opportunity to accelerate the development cycle and innovation index of a new class of applications, services, and business models. PaaS offerings are widely diversified but largely associated with powerful corporate interests. With the commencement of the Stratos project at Apache, vendors and users will have a neutral community free from corporate governance restrictions, with which to collaborate and accelerate the development of a platform that provides wide benefits across the industry. As a flexible framework, we expect a wide variety of platforms to leverage the technology to fill specific niches and needs. == Current Status == Stratos has been in development since 2010 at WSO2, under the Apache License and under the Apache Way. Contribution to Apache, from which many of the core components are sourced, should be very straightforward. == Meritocracy == The contributors have a longstanding commitment and practice of meritocracy in their personal and professional capacities. Many of the committers on the
Re: [PROPOSAL] Apache Spark for the Incubator
Hi Marvin On Sun, Jun 9, 2013 at 5:15 AM, Marvin Humphrey mar...@rectangular.comwrote: On Sat, Jun 8, 2013 at 4:55 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Note: we discussed adding Roman before the VOTE and it was fine with the incoming Spark community, so Roman is now on the wiki for the proposal. In case this changes anyone's VOTE on the VOTE thread, feel free to speak up or change your VOTE. Otherwise, nothing else to see here folks. +1 for the original proposal. +0.9 for the new proposal. Yes, I expect you to tally my vote that way. :) Next time, please be more careful when starting a VOTE and please don't change the proposal text in the middle of a vote. Personnel issues in proposals have caused significant problems in the past. That's unlikely to happen in this case, but I want to register my protest now because it might save us hundreds or thousands of emails in the future. This is *not* a [VOTE] yet, this is a [PROPOSAL] in which case the proposal can be updated and enhanced if required. So allow me to disagree about what you replied regarding *not to make changes to the proposal in such phase* Good luck, Spark! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Looking for a Champion
+1 @Marcel Any links for the draft proposal so people can assess if they can help or not ? On Wed, Jun 5, 2013 at 4:07 PM, Marcel Offermans marcel.offerm...@luminis.nl wrote: I would never search for a generic job scheduling application in the Wicket project. I still don't know exactly what this new project is about, but the fact that it happens to use Wicket in itself is not enough to make it a Wicket subproject if you ask me. Greetings, Marcel On Jun 5, 2013, at 16:01 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Could it be a part of Apache Wicket? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 5:33 PM, Andy Van Den Heuvel andy.vandenheu...@gmail.com wrote: Hey Alexei, Yes, it does. On Wed, Jun 5, 2013 at 3:20 PM, Alexei Fedotov alexei.fedo...@gmail.comwrote: Andy, It uses Apache Wicket, doesn't it? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 4:42 PM, Andy Van Den Heuvel andy.vandenheu...@gmail.com wrote: Jenkins is a continuous integration server, it provides integration with SCM, Build Automation, Testing... This proposal is for a multi-purpose tool, providing support for Monitoring, Backup's,Process Automation, (also Continuous Integration though) The architecture is very different. The idea behind this has come up of using Hudson/Jenkins for several years. On Wed, Jun 5, 2013 at 2:25 PM, Simon Lucy simon.l...@bbc.co.uk wrote: Andy Van Den Heuvel wrote: I'm looking for a Champion to help me setup a proposal. The project is a pluggable all-round job scheduling application. Not to be a killjoy but how is it different to Hudson/Jenkins? S Can somebody help me? Thanks for your consideration. --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache. **org 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Looking for a Champion
@Ate Yes I noticed but not enough information here in the thread to make anyone think to help or not and I would suggest for Andy just to prepare an abstract and brief description and share it here to see if someone is interested rather than keep coming and going with question just to know what the project is about rather than discussing whom will help and how @Andy: Would you please paste (or link) here an abstract and a brief description what the project is about ? I would say have a look at [1] make a similar one fill it in with as much as you can share that here to see if someone is interested to be a Champion and take it from there [1] https://wiki.apache.org/incubator/StratosProposal On Wed, Jun 5, 2013 at 4:29 PM, Ate Douma a...@douma.nu wrote: On 06/05/2013 04:12 PM, Mohammad Nour El-Din wrote: +1 @Marcel Any links for the draft proposal so people can assess if they can help or not ? He is asking for help (Champion) to create such a draft :) On Wed, Jun 5, 2013 at 4:07 PM, Marcel Offermans marcel.offerm...@luminis.nl wrote: I would never search for a generic job scheduling application in the Wicket project. I still don't know exactly what this new project is about, but the fact that it happens to use Wicket in itself is not enough to make it a Wicket subproject if you ask me. Greetings, Marcel On Jun 5, 2013, at 16:01 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Could it be a part of Apache Wicket? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 5:33 PM, Andy Van Den Heuvel andy.vandenheu...@gmail.com wrote: Hey Alexei, Yes, it does. On Wed, Jun 5, 2013 at 3:20 PM, Alexei Fedotov alexei.fedo...@gmail.com**wrote: Andy, It uses Apache Wicket, doesn't it? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 4:42 PM, Andy Van Den Heuvel andy.vandenheu...@gmail.com wrote: Jenkins is a continuous integration server, it provides integration with SCM, Build Automation, Testing... This proposal is for a multi-purpose tool, providing support for Monitoring, Backup's,Process Automation, (also Continuous Integration though) The architecture is very different. The idea behind this has come up of using Hudson/Jenkins for several years. On Wed, Jun 5, 2013 at 2:25 PM, Simon Lucy simon.l...@bbc.co.uk wrote: Andy Van Den Heuvel wrote: I'm looking for a Champion to help me setup a proposal. The project is a pluggable all-round job scheduling application. Not to be a killjoy but how is it different to Hudson/Jenkins? S Can somebody help me? Thanks for your consideration. --** --**- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache. **org general-help@incubator.apache.**org general-h...@incubator.apache.org --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Looking for a Champion
Hi Tom The proposal looks pretty interesting on the technical level indeed, but when it comes to ASF it is more about building (or trying to guarantee) of community around a project so it can continue and evolve and does not die, in terms of the code being maintained and used Yes Incubator is about being an intermediate step for a project to come into the ASF, but it is more about helping an already existing community, which IMHO and from what I have seen from projects in the Incubator that initial community should be big enough (I would say at least three real active committers) to start proposing the project into the Incubator I have mentored a project before which was more than appealing technical wise and they already had big enough community (three committers) but by the time after just coming into the Incubator their availability severely changed and the project could not make it I would suggest to wait a bit and build more awareness about the project and get more enough people around and then continue with the proposal to ASF Incubator, if you would like and allow me I can help in that On Tue, May 7, 2013 at 4:01 AM, Tom Everett t...@khubla.com wrote: Thank-you. I am looking for both champion and mentors, for this project: http://blog.khubla.com/wp-content/uploads/2013/05/pragmatach-incubator-proposal.pdf I hope that a pdf document is acceptable. The web site is here http://www.pragmatach.com If you're interested, there is a web-based presentation here: http://pragmatach.com/slideshow/index.html If there is any more information I can supply that might be of interest please let me know. On Mon, May 6, 2013 at 7:29 PM, Suresh Marru sma...@apache.org wrote: Yes this is the right list for soliciting champion and mentors. Suresh On May 6, 2013, at 7:04 PM, Tom Everett t...@khubla.com wrote: Good afternoon. I have a project which I am hoping to submit to the incubator, and I understand from the documentation that it is recommended to identify a champion prior to the incubator application. Is this mailing list an appropriate place to solicit for such a person? -- A better world shall emerge based on faith and understanding - Douglas MacArthur - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- A better world shall emerge based on faith and understanding - Douglas MacArthur -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Looking for a Champion
Hi Tom On Tue, May 7, 2013 at 9:43 PM, Tom Everett t...@khubla.com wrote: Hi Mohammad I'd be quite happy for your assistance. I haven't made a significant effort to build a community around Pragmatach, mainly because I'm not familiar with how to announce it, where, and to whom. Is there any assistance you can offer with that? Sure I would like to do that, but I suggest to take that off this list as this is more for discussing new projects coming into Incubator hoping to get back to it when the project is ready for that On Tue, May 7, 2013 at 2:25 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Tom The proposal looks pretty interesting on the technical level indeed, but when it comes to ASF it is more about building (or trying to guarantee) of community around a project so it can continue and evolve and does not die, in terms of the code being maintained and used Yes Incubator is about being an intermediate step for a project to come into the ASF, but it is more about helping an already existing community, which IMHO and from what I have seen from projects in the Incubator that initial community should be big enough (I would say at least three real active committers) to start proposing the project into the Incubator I have mentored a project before which was more than appealing technical wise and they already had big enough community (three committers) but by the time after just coming into the Incubator their availability severely changed and the project could not make it I would suggest to wait a bit and build more awareness about the project and get more enough people around and then continue with the proposal to ASF Incubator, if you would like and allow me I can help in that On Tue, May 7, 2013 at 4:01 AM, Tom Everett t...@khubla.com wrote: Thank-you. I am looking for both champion and mentors, for this project: http://blog.khubla.com/wp-content/uploads/2013/05/pragmatach-incubator-proposal.pdf I hope that a pdf document is acceptable. The web site is here http://www.pragmatach.com If you're interested, there is a web-based presentation here: http://pragmatach.com/slideshow/index.html If there is any more information I can supply that might be of interest please let me know. On Mon, May 6, 2013 at 7:29 PM, Suresh Marru sma...@apache.org wrote: Yes this is the right list for soliciting champion and mentors. Suresh On May 6, 2013, at 7:04 PM, Tom Everett t...@khubla.com wrote: Good afternoon. I have a project which I am hoping to submit to the incubator, and I understand from the documentation that it is recommended to identify a champion prior to the incubator application. Is this mailing list an appropriate place to solicit for such a person? -- A better world shall emerge based on faith and understanding - Douglas MacArthur - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- A better world shall emerge based on faith and understanding - Douglas MacArthur -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- A better world shall emerge based on faith and understanding - Douglas MacArthur -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept jclouds into the Apache Incubator
ecosystem. While jclouds does not directly rely upon any Apache project, it does support several Apache projects and has options to collaborate with several others. More specifically, jclouds currently supports Apache Whirr, Apache ACE, Apache Karaf, and Apache Camel, and options exist to use Apache Maven as a build tool with the jclouds API. jclouds includes support for the Apache CloudStack API and is used as a compatibility test tool for its EC2 interface. jclouds can also be used to test Apache Deltacloud EC2 portability. === An Excessive Fascination with the Apache Brand === jclouds recognizes the fortitude of the Apache brand, but the motivation for becoming an Apache project is to strengthen and expand the jclouds community and its user base. While the jclouds community has seen steady growth over the past several years, association with the ASF is expected to expedite this pattern of growth. Development is expected to continue on jclouds under the Apache license whether or not it is supported by the ASF. == Documentation == The [[http://www.jclouds.org/|jclouds]] project documentation is publicly available at the following sites: * http://jclouds.org: installation guide, user guides, development resources, news, resources to get started * https://github.com/jclouds/jclouds: current source, source code issues log * https://github.com/jclouds/jclouds.github.com: static content for jclouds.org, documentation issues log * https://twitter.com/jclouds: jclouds on Twitter * https://groups.google.com/forum/?fromgroups#!forum/jclouds-dev: the jclouds development forum on Google Groups * https://groups.google.com/forum/?fromgroups#!forum/jclouds: the jclouds community forum on Google Groups == Initial Source == The initial source is located on GitHub in the following repositories: * git://github.com/jclouds/jclouds.git * git://github.com/jclouds/jclouds-labs.git * git://github.com/jclouds/jclouds.github.com.git * git://github.com/jclouds/jclouds-chef.git * git://github.com/jclouds/jclouds-cli.git * git://github.com/jclouds/jclouds-karaf.git * git://github.com/jclouds/jclouds-examples.git == Source and Intellectual Property Submission Plan == jclouds's initial source is licensed under the Apache License, Version 2.0. https://github.com/jclouds/jclouds/blob/master/resources/LICENSE.txt == External Dependencies == This is a listing of Maven coordinates for all of the external dependencies jclouds uses. All of the dependencies are in Sonatype and their licenses should be accessible. * aopalliance:aopalliance:jar:1.0:compile * com.google.code.gson:gson:jar:2.2.2:compile * com.google.guava:guava:jar:14.0.1:compile * com.google.inject.extensions:guice-assistedinject:jar:3.0:compile * com.google.inject:guice:jar:3.0:compile * javax.annotation:jsr250-api:jar:1.0:compile * javax.inject:javax.inject:jar:1:compile * javax.ws.rs:jsr311-api:jar:1.1.1:compile * org.99soft.guice:rocoto:jar:6.2:compile == Cryptography == jclouds contains no cryptographic algorithms, but it does provide the ability for people to plug in various cryptographic libraries. == Required Resources == === Mailing lists === * jclouds-dev: for development discussions * jclouds-user: for community discussions * jclouds-private: for PPMC discussions * jclouds-commits: for code changes === Apache git repository === The jclouds team is experienced in git and requests the following allocation on the Apache git server: git://git.apache.org/incubator-jclouds.git === Issue Tracking === jclouds currently uses GitHub for issue tracking. The intent is to request an allocation for Jira upon acceptance into the Incubator. Proposed project name: jclouds == Initial Committers == * Ignasi Barrera, ignasi dot barrera at gmail dot com * Andrew Bayer, abayer at apache dot org * Ioannis Canellos, iocanel at gmail dot com * Adrian Cole, adrianc at netflix dot com * Andrew Gaul, gaul at maginatics dot com * Andrew Phillips, aphillips at qrmedia dot com * Matt Stephenson, mattstep at mattstep dot net * Everett Toews, everett dot toews at rackspace dot com * Becca Wood, silkysun at silkysun dot net == Affiliations == * Ignasi Barrera, Abiquo * Andrew Bayer, Cloudera * Ioannis Canellos, Red Hat * Adrian Cole, Netflix * Andrew Gaul, Maginatics * Matt Stephenson, Google * Everett Toews, Rackspace == Sponsors == === Champion === * Brian McCallister, Apache Software Foundation === Mentors === * Brian McCallister, Apache Software Foundation * Tom White, Apache Software Foundation * Henning Schmiedehausen, Apache Software Foundation * David Nalley, Apache Software Foundation * Jean-Baptiste Onofré, Apache Software Foundation * Mohammad Nour El-Din, Apache
Re: [PROPOSAL] jclouds Proposal for Incubator
Hi Sent from my Samsung Galaxy S3 Apologies for any typos On Apr 16, 2013 9:20 PM, David Nalley da...@gnsa.us wrote: On Tue, Apr 16, 2013 at 2:34 PM, Rebecca Wood silky...@gmail.com wrote: Dear ASF members, We would like to propose the jclouds project to the Incubator. The jclouds Proposal is available at: http://wiki.apache.org/incubator/jcloudsProposal We welcome your feedback and suggestions. Excited to see jclouds proposal. If you are looking for additional mentors, I'd be happy to step up. Indeed, jclouds is a perfect fit to Apache Cloud ecosystem I add my enthusiasm to David's about additional mentors --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Onami as TLD
+1 (binding) On Tue, Mar 26, 2013 at 8:04 AM, Christian Grobmeier grobme...@gmail.comwrote: Hi all, Apache Onami entered incubation before more than 3 months. Since then the community has proven to be pretty active and healthy. A few releases were made and the status page has been completed: http://incubator.apache.org/projects/onami.html Three new committers were added in the past weeks. SVNSearch shows, there is clearly one guy who is outstanding in his motivation, but others do commit as well: http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fonami Mailinglist Archives show the Community is discussing in public: http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/ The community consists of new Apache-people and some more experienced Apache-people. I do not see any problem regarding developing the Apache-way. I agree on that regard as additionally to the experienced people in the project also the mentors are moving on with the project which will help in the future in case of any issues if any. Way to go Onami, good work :) A [DISCUSS] thread on general@ showed no concerns. Simone Tripodi has been elected as the new Chair: http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/201303.mbox/%3CCAPFNckisQo29Ssy6Q-WkKgAZLRa3VW%2B7afLCEbbVy6HsWX_rAg%40mail.gmail.com%3E A resolution has been created and voted on: http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/201303.mbox/%3CCAPFNckjDujef_G6t1%3DjuTdOvuXsgxWq-%2BGntiOMdFpE%3DgwReDg%40mail.gmail.com%3E The community vote for becoming a TLD was successful too: http://onami-dev.markmail.org/thread/6w2dvrs3bj755kdm We now kindly ask the IPMC to review our findings and vote on the Onami graduation. [ ] +1, yes propose the graduation of Apache Onami to the board [ ] -1, no, don't let Apache Onami graduate, because... Thanks, Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Apache Onami to become an ASF TLD
Hi Last time I checked the rules it state that, for such votes, the IPMC should be *notified* through general@ On Mon, Mar 18, 2013 at 11:32 AM, Branko Čibej br...@apache.org wrote: On 18.03.2013 11:25, Bertrand Delacretaz wrote: Hi, On Mon, Mar 18, 2013 at 8:01 AM, Christian Grobmeier grobme...@gmail.com wrote: ...in the previous discussions were no objections against the graduation of Apache Onami... Was there a community vote indicating a desire to graduate? This is the community vote. It's a bit confusing that it's also cc:'d to general@. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Apache Onami to become an ASF TLD
Hi AS you can read I used the word *should* and in the rules say ...It is wise to copy the incubator general list when the vote is proposed. So Christian did the *wise* thing :D If you don't like that, and I see your point BTW, you can propose to change that part *not* to copy the general@ when such vote(s) are proposed On Mon, Mar 18, 2013 at 11:47 AM, Branko Čibej br...@apache.org wrote: On 18.03.2013 11:35, Mohammad Nour El-Din wrote: Hi Last time I checked the rules it state that, for such votes, the IPMC should be *notified* through general@ This VOTE is not a requirement but is recommended. It is unlikely that IPMC members will vote to approve graduation unless the Mentors and community positively express their readiness for graduation. It is wise to copy the incubator general list when the vote is proposed. I see no requirement to notify. And I still maintain it's confusing, as evidenced by this very case. It would make more sense if general@ were notified after the fact of the vote result, e.g., as an addendum to the graduation vote proposal. There's absolutely no call for the IPMC to poke our fingers into what are obviously optional, internal podling procedures. That's almost as bad as doing code reviews for them. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Apache Onami to become an ASF TLD
Hi I totally agree that it can be a source of confusion, but I used to either FWD or send a different copy to general@ for notification and I thought others do the same On Mon, Mar 18, 2013 at 5:01 PM, Craig L Russell craig.russ...@oracle.comwrote: On Mar 18, 2013, at 6:16 AM, Christian Grobmeier wrote: On Mon, Mar 18, 2013 at 2:12 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Mar 18, 2013 at 2:02 PM, Christian Grobmeier grobme...@gmail.com wrote: ...I followed this: http://incubator.apache.org/**guides/graduation.html#tlp-** community-votehttp://incubator.apache.org/guides/graduation.html#tlp-community-vote It is wise to copy the incubator general list when the vote is proposed Ok - I have now changed that to it is wise to notify the incubator general list that the community vote is starting - but do not Cc the vote to the general list as that creates confusion. Great, thanks! I was just starting to do the same, now I safe the time and grab a cup of coffee instead. I started to do the same. But I decided to read to the end of this thread to be sure what the issue was. As a note, there was recently a very similar discussion about whether to copy or forward podling votes for new committers. Regards, Craig P.S. I found nothing misleading about the original vote which states pretty clearly This is the community graduation vote for the Apache Onami project. The only thing confusing is that you actually have to *read* the message to know that it's a community vote. [meow] ;-) Cheers -Bertrand --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:Craig.Russell@oracle.**com craig.russ...@oracle.com P.S. A good JDO? O, Gasp! --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Apache Onami to become an ASF TLD
Hi On Mon, Mar 18, 2013 at 2:12 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Mar 18, 2013 at 2:02 PM, Christian Grobmeier grobme...@gmail.com wrote: ...I followed this: http://incubator.apache.org/guides/graduation.html#tlp-community-vote It is wise to copy the incubator general list when the vote is proposed Ok - I have now changed that to it is wise to notify the incubator general list that the community vote is starting - but do not Cc the vote to the general list as that creates confusion. I was encouraged by your change and changed a bit: It is wise to notify the incubator general listhttp://incubator.apache.org/guides/lists.html#general+at+incubator.apache.org that the community vote is starting. Please do not Cc the vote to the general list as that creates confusion, instead you can either: - FWD the [VOTE] e-mail to the general list, or - Send a different copy to the general list indicating that a graduation community [VOTE] is in progress This way we also can have a kind of unified behavior (or at least hints) about what to do when notifying the IPMC about such votes -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate CloudStack from Incubator
+1 (binding) On Sun, Mar 17, 2013 at 3:38 PM, Suresh Marru sma...@apache.org wrote: + 1 (binding) Great going in a short time (given the size of the project), All the best as a TLP, Suresh On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote: Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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, for distribution at no charge to the public, related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org * Sebastien Goasguen seb...@apache.org * Matt Richard Hogstrom hogst...@apache.org * Wido den Hollander wid...@apache.org * Alex Huang ahu...@apache.org * Jim Jagielski j...@apache.org * Alex Karasulu akaras
Re: [RESULT][VOTE] Accept MRQL into the Incubator
Hi On Sun, Mar 17, 2013 at 11:49 AM, Alex Karasulu akaras...@apache.orgwrote: We're also missing Ant Elder from the Nominated Mentors list no? Fixed On Sun, Mar 17, 2013 at 9:45 AM, ant elder ant.el...@gmail.com wrote: On Sat, Mar 16, 2013 at 11:07 PM, Edward J. Yoon edwardy...@apache.org wrote: The required action has been taken, so let me close this thread again. I apologize again for my mistake. The Sponsors are changed as following: == Champion == * Alex Karasulu akarasulu AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org * Mohammad Nour mnour AT apache DOT org * Alan Cabrera adc AT apache DOT org The following IPMCers voted in favor: * Mohammed Nour El-Din * Alex Karasulu * Tommaso Teofili * Chris Mattmann * Christian Grobmeier * Niall Pemberton Thanks. Actually Edward we've discussed this within the Incubator PMC and the plan is to respect the original vote and leave you on as champion and mentor, the only change being the additional mentors. You're an Officer of the ASF which is close enough and there are now a lot of mentors who can provide any additional help should it be needed. Sorry from the Incubator that this got into such a mess. ...ant -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Hi On Fri, Mar 15, 2013 at 2:06 AM, Marvin Humphrey mar...@rectangular.comwrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. No I didn't Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept MRQL into the Incubator
+1 On Wed, Mar 6, 2013 at 6:04 PM, Leonidas Fegaras fega...@cse.uta.eduwrote: Dear ASF members, I would like to call for a VOTE for acceptance of MRQL into the Incubator. The vote will close on Monday March 11, 2013. [ ] +1 Accept MRQL into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept MRQL into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/**incubator/MRQLProposalhttp://wiki.apache.org/incubator/MRQLProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Leonidas Fegaras = Abstract = MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop and Hama. = Proposal = MRQL (pronounced ''miracle'') is a query processing and optimization system for large-scale, distributed data analysis. MRQL (the MapReduce Query Language) is an SQL-like query language for large-scale data analysis on a cluster of computers. The MRQL query processing system can evaluate MRQL queries in two modes: in MapReduce mode on top of Apache Hadoop or in Bulk Synchronous Parallel (BSP) mode on top of Apache Hama. The MRQL query language is powerful enough to express most common data analysis tasks over many forms of raw ''in-situ'' data, such as XML and JSON documents, binary files, and CSV documents. MRQL is more powerful than other current high-level MapReduce languages, such as Hive and PigLatin, since it can operate on more complex data and supports more powerful query constructs, thus eliminating the need for using explicit MapReduce code. With MRQL, users will be able to express complex data analysis tasks, such as PageRank, k-means clustering, matrix factorization, etc, using SQL-like queries exclusively, while the MRQL query processing system will be able to compile these queries to efficient Java code. = Background = The initial code was developed at the University of Texas of Arlington (UTA) by a research team, led by Leonidas Fegaras. The software was first released in May 2011. The original goal of this project was to build a query processing system that translates SQL-like data analysis queries to efficient workflows of MapReduce jobs. A design goal was to use HDFS as the physical storage layer, without any indexing, data partitioning, or data normalization, and to use Hadoop (without extensions) as the run-time engine. The motivation behind this work was to build a platform to test new ideas on query processing and optimization techniques applicable to the MapReduce framework. A year ago, MRQL was extended to run on Hama. The motivation for this extension was that Hadoop MapReduce jobs were required to read their input and write their output on HDFS. This simplifies reliability and fault tolerance but it imposes a high overhead to complex MapReduce workflows and graph algorithms, such as PageRank, which require repetitive jobs. In addition, Hadoop does not preserve data in memory across consecutive MapReduce jobs. This restriction requires to read data at every step, even when the data is constant. BSP, on the other hand, does not suffer from this restriction, and, under certain circumstances, allows complex repetitive algorithms to run entirely in the collective memory of a cluster. Thus, the goal was to be able to run the same MRQL queries in both modes, MapReduce and BSP, without modifying the queries: If there are enough resources available, and low latency and speed are more important than resilience, queries may run in BSP mode; otherwise, the same queries may run in MapReduce mode. BSP evaluation was found to be a good choice when fault tolerance is not critical, data (both input and intermediate) can fit in the cluster memory, and data processing requires complex/repetitive steps. The research results of this ongoing work have already been published in conferences (WebDB'11, EDBT'12, and DataCloud'12) and the authors have already received positive feedback from researchers in academia and industry who were attending these conferences. = Rationale = * MRQL will be the first general-purpose, SQL-like query language for data analysis based on BSP. Currently, many programmers prefer to code their MapReduce applications in a higher-level query language, rather than an algorithmic language. For instance, Pig is used for 60% of Yahoo MapReduce jobs, while Hive is used for 90% of Facebook MapReduce jobs. This, we believe, will also be the trend for BSP applications, because, even though, in principle, the BSP model is very simple to understand, it is hard to develop, optimize, and maintain non-trivial BSP applications coded in a general-purpose programming language. Currently, there is no widely acceptable declarative BSP query language, although there are a few special-purpose BSP systems for graph analysis, such as Google
Re: [PROPOSAL] MRQL for the Apache Incubator
I added myself as a mentor. Welcome aboard. On Wed, Mar 6, 2013 at 9:02 AM, Edward J. Yoon edwardy...@apache.orgwrote: I think it's time to call for vote. On Mon, Mar 4, 2013 at 9:25 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: Nice proposal indeed, I'd say having 3 mentors is usually better to avoid release headaches. Regards, Tommaso 2013/3/4 Edward J. Yoon edwardy...@apache.org Sure I can. :) Of course, we'll welcome more mentors from incubator IPMC if there're volunteers. On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org wrote: On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 (binding) Sent from my Samsung Galaxy S3 Apologies for any typos On Mar 4, 2013 8:07 AM, kishore g g.kish...@gmail.com wrote: +1 (non-binding) Good luck On Sun, Mar 3, 2013 at 11:05 PM, Ashish paliwalash...@gmail.com wrote: +1 (non-binding) On Sun, Mar 3, 2013 at 5:05 AM, Andrei Savu as...@apache.org wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority
Re: Patches from contributors: missing ASF license inclusion?
Hi On Mon, Mar 4, 2013 at 12:19 PM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? I believe that should be the way. The positive side is that it will be one step less when they are recommended as committers in the future :) Thanks for any clarification! Matthieu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Patches from contributors: missing ASF license inclusion?
Sorry about my false answer then, I take it back On Mon, Mar 4, 2013 at 3:01 PM, Matthieu Morel mmo...@apache.org wrote: This is clear now, there is no room for doubt. Thanks ! Matthieu On Mar 4, 2013, at 14:42 , Benson Margulies wrote: You DO NOT NEED AN ICLA from these people. Under the terms of the AL, any contribution made back to the ASF on ASF infrastructure, such as via a mailing list, JIRA, or Bugzilla, is licensed to the foundation. The JIRA checkbox existed to give people an easy way to _avoid_ contributing something. There is no need to ask casual patchers for ICLAs. On Mon, Mar 4, 2013 at 3:19 AM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? Thanks for any clarification! Matthieu - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi I would like to help and hence added myself as a mentor. Thanks for bringing the project to Apache. On Fri, Mar 1, 2013 at 7:02 AM, Andrei Savu savu.and...@gmail.com wrote: Hi David - On Thu, Feb 28, 2013 at 11:19 AM, David Nalley da...@gnsa.us wrote: I am interested in this. I know one or two things about puppet and cloud APIs. Not sure how many cycles I can expend. It would be great to have you part of the team. Feel free to edit the wiki. CloudStack support is very important for me and I'm going to spend a fair amount of time on that over the next cloud of weeks / months. -- Andrei Savu -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL] BeanShell join the Apache Incubator
The proposal looks interesting. I also added my self as a mentor. Good luck. On Sun, Feb 17, 2013 at 5:59 PM, Simone Tripodi simonetrip...@apache.orgwrote: Hi there, the BeanShell project, the long living JSR-274 reference implementation, would like to join the Apache Incubator - I started preparing a proposal on Wiki[1] and we are looking for Mentors and committers. The project has already been donated to the ASF with the SG for BeanShell and original authors are onboard, we also have people who started maintaining their own fork, so the community is really promising! Please guys feel free to signup in the proposal if interested - help us on keep living the JSR-274 RI!!! Have a nice day, all the best! -Simo [1] http://wiki.apache.org/incubator/BeanShellProposal http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Release Apache Onami-Logging 3.4.0-incubating
+1 (binding) On Wed, Jan 23, 2013 at 2:48 PM, Simone Tripodi simonetrip...@apache.orgwrote: Good morning IPMC, The Apache Onami community has voted[1] the release of Apache Onami-Logging 3.4.0-incubating, collecting two IPMC votes from members Olivier Lamy and Christian Grobmeier. This is the changelist: Bug [ONAMI-28] - Do not use code from com.google.inject.internal Dependency upgrade [ONAMI-61] - Update SLF4J to v1.7.2 New Feature [ONAMI-1] - Add the Apache Log4j 2 integration module Task [ONAMI-7] - Import Logging donated codebase to ASF SVN [ONAMI-16] - Update Logging docs [ONAMI-26] - Make all artifactId OSGi name compliant [ONAMI-31] - Update parent pom reference to released 1-incubating version SVN source tag https://svn.apache.org/repos/asf/incubator/onami/tags/org.apache.onami.logging.parent-3.4.0-incubating/ Staging repo: https://repository.apache.org/content/repositories/orgapacheonami-150/ Vote will be open for at least 72 hours and closes approximatively on 26th Jan 2013, at 1:40pm. [ ] +1, let's get it rmblee!!! [ ] +/-0, fine, but consider to fix few issues before... [ ] -1, nope, because... (and please explain why) So IPMCs please cast your votes! [1] http://markmail.org/message/pe5lzynixtpk2er5 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Release Apache Onami-Logging 3.4.0-incubating
Hi Branko... On Sun, Feb 3, 2013 at 10:31 PM, Branko Čibej br...@apache.org wrote: On 03.02.2013 21:26, Christian Grobmeier wrote: Just to be clear, in the case of Onami Logging, reviewers are asked to find the right package amongst 8 different source packages in 8 different directories. What do you mean with right? They all are right, because they contain different sources and we want to release them all. In the end I realized that only the -parent.zip contained all the sources and was comparable to the contents of the release tag in SVN. This should, IMO, be better communicated in the vote announcement. I agree this might be a helpful detail but not a mandatory or necessary one as it can be deduced from the structure of the project The fact that the NOTICE files in the other source .jars are not identical to the one in the source .zip, or in the release tag, is (putting it mildly) confusing. Impossible? I have to disagree. One can: wget -r -l 1 -np -nH -nd -nv -e robots=off --wait 10 --no-check-certificate https://repository.apache.org/content/repositories/orgapacheonami-150/ and easily gets all files. Yes. I'm not interested in checking a lot of binaries. They're not part of the release, right? Well yes and no, what we release is the source code itself, but optionally and for the convenience of users (developers) who do not want to build the artifacts from source code on their machines, which can be for what ever reason, we publish maven artifacts and if they are published they have to comply to the rules in [1] I know sometimes checking a release is a PITA process, but someone needs to do it to get the effort of other Apache Commiters and Members out and to progress with other stuff, it is a *voluntary team work* effort. For sure your comments and ideas to enhance, improve and ease the process of release check, for Onami or any other project in general are more than welcome, but allow me to say that IMHO it is not helpful to ask an ASF project team to provide the release in a way that suits every an each IPMC member to make it easy for them to check [1] http://www.apache.org/dev/publishing-maven-artifacts.html -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Please help us release 2 Onami artifacts
Hi... On Fri, Feb 1, 2013 at 12:12 PM, Gary Martin gary.mar...@wandisco.comwrote: On 01/02/13 04:42, Christian Grobmeier wrote: Hello all, we need one more binding vote for the two running votings on Onami: http://people.apache.org/~**brane/incubator-votes.htmlhttp://people.apache.org/~brane/incubator-votes.html They are 9 days open so far... hopefully somebody else from the IPMC can flesh out a few minutes and check them. Thank you! Christian -- http://www.grobmeier.de https://www.timeandbill.de --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org I find it interesting that Christian has once again had to ask for attention for Onami votes. Why the lack of interest here? It looks like there have been 6 votes that have been resolved or cancelled since the Onami votes started. Is there anything intrinsically harder about evaluating these releases? I don't think so, I think it is just bad timing as I notice that traffic on different mailing list is low these days, maybe some people still have holidays/vacations, busy at work after a holiday/vacation But above all most of this problem is on my shoulder as I am mentor of Onami and didn't contribute to any of the votes so far neither on the dev@on in here. I apologize about that as I have some stress at work I will try to have a look at them during this weekend Cheers, Gary --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Cloudstack report signoffs
Hi Re-reviewed the report and re-signed it On Thu, Jan 10, 2013 at 10:31 PM, David Nalley da...@gnsa.us wrote: On Thu, Jan 10, 2013 at 3:58 PM, Benson Margulies bimargul...@gmail.com wrote: If I read the diffs correctly, Joe just posted an update to the report which removed all the mentor signoffs. Was this on purpose? This was on purpose. See: http://markmail.org/message/w5mjdw3yfuxgrv3v --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Do all releases need to go to /dist?
Hi I agree about how policy should change. But when it comes to apply on this case I believe we have to read the release rules carefully and we will see that we don't need policy change we just need to add more details and hence make it more clear The release rules assume you are release source code not just a pom file (s) which for sure people will not use it by downloading a dist from anywhere. They either will svn co the tag and build it locally or use the one deployed in Nexus It is just a different situation not an exception Christian and I already discussed that offline and kindly took the effort to bring it to the list :) Sent from my Samsung Galaxy S3 Apologies for any typos On Dec 21, 2012 5:12 PM, Benson Margulies bimargul...@gmail.com wrote: My belief is that the policy changed a long time ago but was not properly edited into the document. If I didn't believe that, I'd be taking a different approach here. My secondary belief is that the existing document is an ambiguous writing job, and I'm as entitled to my opinion as to the actual intention as anyone else with rights to edit it. And, as such, I think that the right thing to do is to put up the edits and see who complains. I am perfectly happy to set the example of boldly editing documents to state the policy as I understand it, and then inviting people to comment. I am in part inspired by the other thread about the uselessness of DRAFT and suchlike markings. If you are so convinced that I am entirely changing, as opposed to clarifying, a Foundation invariant, then you should say as much on the thread over on infra. If you feel strongly enough, you should revert my commit. On Fri, Dec 21, 2012 at 10:16 AM, Daniel Shahaf d...@daniel.shahaf.name wrote: Benson Margulies wrote on Fri, Dec 21, 2012 at 07:01:03 -0500: On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Give me a URL where this policy is and I'll edit it. The way to change a policy is to obtain consensus on the new policy, not to edit the web page that documents the existing policy --- particularly when someone just expressed an opinion in favour of the documented policy. You're setting a good counter-example to podlings. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Onami parent 1-incubating
+1 (binding) On Sun, Dec 16, 2012 at 11:31 PM, Christian Grobmeier grobme...@gmail.comwrote: I voted on the dev list, but here is my +1 as IPMC On Sun, Dec 16, 2012 at 8:58 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all, This is a call for a vote on releasing the following candidate as Apache Onami parent 1-incubating. This will be our first release. the Apache Onami PPMC has voted[1] the release of the parent-1, collecting 2 IPMC binding votes. We need an additional IPMC vote. Artifacts are on Nexus: https://repository.apache.org/content/repositories/orgapacheonami-006/ SVN Tag: http://svn.apache.org/repos/asf/incubator/onami/tags/parent-1-incubating/ The vote is open for 72 at least hours and is closing ~ on December 19th, 8:00pm GMT Please cast your votes: [ ] +1 release it [ ] +0 go ahead, but ... [ ] -0 uhm... [ ] -1 don't release it, because... Many thanks in advance for reviewing, all the best! -Simo [1] http://s.apache.org/pVu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept Apache Streams as an Incubator Project
+1 (binding) Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 14, 2012 6:36 PM, Ryan Baxter rbaxte...@apache.org wrote: +1 (non-binding) On Wed, Nov 14, 2012 at 11:16 AM, James M Snell jasn...@gmail.com wrote: +1 On Wed, Nov 14, 2012 at 7:24 AM, Ross Gardler rgard...@opendirective.com wrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Onami proposal in the Incubator
Hi Bertrand... On Mon, Nov 12, 2012 at 9:56 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sun, Nov 11, 2012 at 8:44 PM, Simone Tripodi simonetrip...@apache.org wrote: ...I am submitting a proposal that has been open for discussion for some days (with the former name of Mayhem), so now submitting for a vote for this project to be accepted into the incubator +1 (and as someone noted the mayhem name still appears twice in the proposal, should be fixed) It is already fixed in the wiki page of the proposal -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept Onami proposal in the Incubator
Hi On Mon, Nov 12, 2012 at 7:32 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) NOTE: I still see some mayhem in confluence and jira. I don't have access to my laptop now would u please update the proposal ? Checked again at [1] and all was OK. Thanks [1] http://wiki.apache.org/incubator/OnamiProposal Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 12, 2012 5:06 PM, Alan Cabrera l...@toolazydogs.com wrote: +1 - binding Regards, Alan On Nov 11, 2012, at 11:44 AM, Simone Tripodi wrote: Hi all guys, I am submitting a proposal that has been open for discussion for some days (with the former name of Mayhem), so now submitting for a vote for this project to be accepted into the incubator. Vote will be open for at least 72 hours and closes approximately on Nov 14th, 2012 at 7:45pm GMT Many thanks in advance, have a nice day! -Simo Adam Berry ~ = Onami = == Abstract == The following proposal is about Onami, a project focused on all aspects of Google Guice[1] extensions. The name takes inspiration from Great Waves (O-nami, in Japanese) Zen Story[2]. == Proposal == Apache Onami aims to create a community focused on the development and maintenance of a set of Google Guice extensions not provided out of the box by the library itself nor the Google developers team, such as integration with 3rd part frameworks or extra functionalities. == Background == Google Guice is a modern, lightweight and fast Dependency Injection Open Source Java library developed by Google, released for the first time on 2006, which is developed under the Google governance. A small group of people, specifically ASF committers Davide Palmisano, Marco Spearanza and Simone Tripodi, that define themselves The 99 Software Foundation[3] (also 99soft for brevity), with the help of some contributors, has developed and maintained a good number of Open Source Google Guice extensions[4], that have been adopted in some (Open Source) projects. Since the community clearly demonstrated the sign of growing participation, they thought times were mature enough to move the components to a real community-driven environment such as the Apache Software Foundation. == Rationale == Actually, there are no projects hosted by the ASF focused on providing Google Guice extensions and even if Google provides some extensions and allows people participating by submitting issues/patches/... there is no real community involvement, so moving the existing 99soft components under the Apache umbrella would mean create a real community-driven project around Guice where people can become active part of the development. = Current Status = == Meritocracy == The historical 99soft team believes in meritocracy and always acted as a community. Mailing list, open issue tracker and other communication channels have always been adopted since its first releases. The adoption in a larger community, such as Apache, is the natural evolution for 99soft components. Moreover, the Apache standards will enforce the existing 99soft community practices and will be a foundation for future committers involvement. == Core Developers == In alphabetical order: * Christian Grobmeier grobmeier at apache dot org * Daniel Manzke daniel dot manzke at googlemail dot com * Davide Palmisano dpalmisano at apache dot org * Marco Speranza marcosperanza at apache dot org * Nino Martinez Wael nino dot martinez dot wael at gmail dot com * Simone Tripodi simonetripodi at apache dot org === Regular Contributors === In alphabetical order: * Cody Ray cray at brighttag dot com * Ghislain Picpoc Touratier ghislain dot touratier at gmail dot com * Ioannis Canellos iocanel at apache dot org * Jordi Gerona jordi at donky dot org * Marzia Forli marzia dot forli at yahoo.com * Pawel Poltorak pawel dot poltorak at gmail.com * Thilo-Alexander Ginkel thilo at ginkel dot com == Alignment == The Apache Onami project is intended to be portable and be fully compatible with Google Guice. To promote the adoption of this project, we believe that it is important that it remains free from corporate association and is perceived by the community to be vendor neutral. To this end, the Apache Software Foundation with its values of transparency and community makes it an excellent fit for this project, not to mention that project creators are already Apache Members/Committers. = Known Risks = == Orphaned Products == The increasing number of Google Guice adopters and the raising interest for its extensions let us believe that there is a minimal risk for this work to being abandoned from the community. == Inexperience with Open Source == All
Re: [DISCUSS] Apache Mayhem proposal
in my ex-company we used two different approaches, we were using mercurial but the same concepts apply here 1- use one repo and have branches for each component in which u make changes and then we merge that back into the main/default branch from which we make releases 2- have different repo for each component which is easier but includes maintaining more reps well in either case some effort needs to be done. for me u really don't mind using either. svn is a very powerful scm and if users are looking for git access we have git mirrors so for me I would be neutral and I will help in both cases Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 6, 2012 8:13 AM, Eric Charles e...@apache.org wrote: On 04/11/2012 09:14, Simone Tripodi wrote: Salut Olivier! AFAIK not possible (git is poor for supporting such sparse checkout mode). So we (infra folks) will have to maintain one git repo per component and create a new git repo for each new component (IMHO a pain ..). In some case git is probably nice but not here ! indeed, for what I can see, not all apache-commons components are supported in git - adding an extra step, every time a new component has to be created, would be not a benefit for the project. We have very similar situation in maven projects (with some components which have their own lifecycle) and we decided to not move those parts to git. nice to see that another ASF community chan share a past similar experience! But hey what is most important build a community around cool code/projects or being able to use the last à la mode scm tool ? as I wrote in a previous message, I personally just need a SCM that allows me continue developing software in a comfortable way :) Mohammad, Eric, maybe SVN fits better for Mayhem? A git repo has to be seen like a monolithic piece of code with its full history. If Mayhem components are aiming to have completely different lifecycle with their own release independent, then many git repos would be needed. I tend to think that 'Less is more', that 'git is now a defacto standard', and that releasing all Mayhem components at the same time, with the same version number (even if there is no change for some of them) is easier for the user. But I am perfectly fine with SVN, except that we would create a structure more difficult to migrate to git later on. Thx, Eric Thanks for the feedbacks! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Mayhem proposal
Hi Christian... Isn't that a step that should be done before graduation, in other words this should not stop going with the Incubator acceptance [VOTE] ? On Tue, Nov 6, 2012 at 3:23 PM, Christian Grobmeier grobme...@gmail.comwrote: Putting trademarks into the loop. Trademark people, any comments to Simones mail? I am not sure if a commonly used word like Mayhem can be a matter of an trademark Thanks in advance, Christian On Tue, Nov 6, 2012 at 2:27 PM, Simone Tripodi simonetrip...@apache.org wrote: Good morning President :) Gianugo pointed me to the homepage of Make Mayem[1] and I found a trademarked software[2] which is called Mayhem as well. Trademarkia shows that more than 10 pages of results of products are registered with the name Mayhem, which I suspect is a daily used word in English language, especially in the US. Giving an overview: * _Make Mayhem_ is an application that lets you connect trigger events to reactions. Unlike writing a program, you simply select an event and a reaction, and then turn on the connection. Voila! No code or app required. * _Mayhem_ is a computer software for use in the encryption and decryption of digital files, including audio, video, text, binary, still images, graphics and multimedia files * _Apache Mayhem_ aims to create a community focused on the development and maintenance of a set of Google Guice extensions My question - IANAL and don't aim to be :P - is: where the legal issues comes out? We don't aim to invade someone else's domain... If the Mayhem is a trademark by Grey Heron Technologies, LLC for a software, aren't Outercurve's guys violating a TM? Sorry if asking silly questions, many thanks in advance! best, -Simo [1] http://www.makemayhem.com/ [2] http://www.trademarkia.com/mayhem-85483903.html [3] http://www.trademarkia.com/trademarks-search.aspx?tn=Mayhem http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Tue, Nov 6, 2012 at 2:10 PM, Jim Jagielski j...@jagunet.com wrote: Different topic: Is there a potential naming/trademark issue related to a pre-existing project? http://www.outercurve.org/Galleries/InnovatorsGallery/Mayhem Thanks! - 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 -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Apache Mayhem proposal
Hi Simone... On Thu, Nov 1, 2012 at 1:04 PM, Simone Tripodi simonetrip...@apache.orgwrote: Hi Mohammad, what about having SVN+Git mirror? I personally just need a SCM, don't have a strong preference, so recommendations are more than welcome! What do you suggest? IMO it would be easier to move into a Git repository, which I will help in setting it up. IMO, it will also be helpful for ASF Git support to have more projects using Git which will help us understand different needs and use cases of different project to provide better Git support by time, by better I mean that now it is really good IMO but for sure we can make it better :) The thing is we still need to have SVN for content related operations like website and so cause it needs to be published using SVN pub-sub. I will collect more details about that Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Thu, Nov 1, 2012 at 11:11 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi I noticed that the code is hosted on github but u r asking for an svn rep while we can have a git repo, or u don't want to continue using git ? Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 11:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Simone I like the idea pretty much and I would like to be a mentor of this project. But I can't edit the wiki page at the moment would u please add me :) Thanks for bringing the project to ASF Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org wrote: I was waiting this since a long time, especially since guiceyfruit is not officially update to guice3. It's great time to do this, as more well-known 3rd parties provide their own extensions [1]. With such a good code base coming from 99soft foundation, we will be good on track. Big +1 and thx again, Eric [1] http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html On 31/10/2012 22:16, Christian Grobmeier wrote: I like that proposal (you have guessed it as I signed up to mentor). Guice is something cool as I found out recently. And I really like the logging component in there (surprise) On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock dwhyt...@gmail.com wrote: Just giving a post-hurricane nudge. On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I prepared a new proposal[1] for the incubator, concerning the creation of a new community focused on all aspects of Google Guice extensions, starting from a rather than small codebase that I and other friends - already ASF committers/members - would like to donate to the ASF. We still need at least one mentor, is there any volunteer available on joining to provide help on bringing that new community up? Many thanks in advance, all the best!!! -Simo [1] http://wiki.apache.org/incubator/MayhemProposal http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Apache Mayhem proposal
Hi Simone... On Fri, Nov 2, 2012 at 1:56 PM, Simone Tripodi simonetrip...@apache.orgwrote: Hi Mohammed! IMO it would be easier to move into a Git repository, which I will help in setting it up. IMO, it will also be helpful for ASF Git support to have more projects using Git which will help us understand different needs and use cases of different project to provide better Git support by time, by better I mean that now it is really good IMO but for sure we can make it better :) agreed! can you update the reference in the proposal, please? TIA!!! Sure thing will do it today when I have sometime The thing is we still need to have SVN for content related operations like website and so cause it needs to be published using SVN pub-sub. I will collect more details about that thanks a lot! Can we propose the site be published on Git, like we already did on GitHub in the `gh-pages` branch? WDYT? IIRC thats not possible as rge pub-sub works with SVN, to be honest I am not aware about the details thats the only fact I know about If I am wrong would someone please correct me :) ? All the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Apache Mayhem proposal
Hi Simone I like the idea pretty much and I would like to be a mentor of this project. But I can't edit the wiki page at the moment would u please add me :) Thanks for bringing the project to ASF Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org wrote: I was waiting this since a long time, especially since guiceyfruit is not officially update to guice3. It's great time to do this, as more well-known 3rd parties provide their own extensions [1]. With such a good code base coming from 99soft foundation, we will be good on track. Big +1 and thx again, Eric [1] http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html On 31/10/2012 22:16, Christian Grobmeier wrote: I like that proposal (you have guessed it as I signed up to mentor). Guice is something cool as I found out recently. And I really like the logging component in there (surprise) On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock dwhyt...@gmail.com wrote: Just giving a post-hurricane nudge. On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I prepared a new proposal[1] for the incubator, concerning the creation of a new community focused on all aspects of Google Guice extensions, starting from a rather than small codebase that I and other friends - already ASF committers/members - would like to donate to the ASF. We still need at least one mentor, is there any volunteer available on joining to provide help on bringing that new community up? Many thanks in advance, all the best!!! -Simo [1] http://wiki.apache.org/incubator/MayhemProposal http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Mayhem proposal
Hi I noticed that the code is hosted on github but u r asking for an svn rep while we can have a git repo, or u don't want to continue using git ? Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 11:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Simone I like the idea pretty much and I would like to be a mentor of this project. But I can't edit the wiki page at the moment would u please add me :) Thanks for bringing the project to ASF Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org wrote: I was waiting this since a long time, especially since guiceyfruit is not officially update to guice3. It's great time to do this, as more well-known 3rd parties provide their own extensions [1]. With such a good code base coming from 99soft foundation, we will be good on track. Big +1 and thx again, Eric [1] http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html On 31/10/2012 22:16, Christian Grobmeier wrote: I like that proposal (you have guessed it as I signed up to mentor). Guice is something cool as I found out recently. And I really like the logging component in there (surprise) On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock dwhyt...@gmail.com wrote: Just giving a post-hurricane nudge. On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I prepared a new proposal[1] for the incubator, concerning the creation of a new community focused on all aspects of Google Guice extensions, starting from a rather than small codebase that I and other friends - already ASF committers/members - would like to donate to the ASF. We still need at least one mentor, is there any volunteer available on joining to provide help on bringing that new community up? Many thanks in advance, all the best!!! -Simo [1] http://wiki.apache.org/incubator/MayhemProposal http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Mayhem proposal
Hi Marvin It is not a login problem I only have my smart phone for now and don't have access to any computer atm that's why I couldn't Sorry for not explaining in details :) Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 1, 2012 4:15 PM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Nov 1, 2012 at 2:20 AM, Eric Charles e...@apache.org wrote: I tried to add myself to the 'Other interested people' on the wiki, but I have not the right to edit the page. On Thu, Nov 1, 2012 at 2:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But I can't edit the wiki page at the moment would u please add me What are the user ids that you use for the Incubator wiki? (Not your apache ids, and specifically the Incubator wiki, since the id can differ across different ASF wikis.) I or someone else will add you to the ContributorsGroup as per this note: http://wiki.apache.org/incubator/ This is the Apache Wiki for the Apache Incubator and is maintained by the community. To edit pages, first sign up for a user account. Then send your username to general@incubator so that we can grant you write access by adding your account to the ContributorsGroup. Once your account is set up, just login and start making changes. Notifications of all changes you make will be sent to the cvs@incubator mailing list. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: ${podling}.incubator.apache.org
+1
Good idea
On Fri, Oct 12, 2012 at 10:54 AM, Alexei Fedotov
alexei.fedo...@gmail.com wrote:
I like it -
that will simplify migrations
12.10.2012 11:31 пользователь Daniel Shahaf d...@daniel.shahaf.name
написал:
Do people mind if web sites (and maybe mailing lists) of new podlings
live at domains of the form ${podling}.incubator.apache.org?
This is in relation to infra work on streamlining TLP migrations. (Case
in point: CMS TLP migrations.) This thread is about the
externally-visible names, not about implementation details.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Thanks
- Mohammad Nour
Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: ${podling}.incubator.apache.org
Hi
On Fri, Oct 12, 2012 at 12:17 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Fri, Oct 12, 2012 at 10:31 AM, Daniel Shahaf d...@daniel.shahaf.name
wrote:
Do people mind if web sites (and maybe mailing lists) of new podlings
live at domains of the form ${podling}.incubator.apache.org?
Not at all. I'd even be fine with ${podling}.apache.org especially if
they've already completed the PODLINGNAMESEARCH process.
See http://markmail.org/message/sbpw2ifnppzd4kal for an earlier
discussion on this that so far didn't lead to much action.
Hmm, didn't notice that thread before, but still, as Joe pointed,
INFRA should give their opinion about it.
BR,
Jukka Zitting
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Thanks
- Mohammad Nour
Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Isis podling from Apache Incubator
[x] +1 Graduate Isis podling from Apache Incubator On Fri, Oct 5, 2012 at 5:44 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, Oct 4, 2012 at 2:41 PM, Dan Haywood d...@haywood-associates.co.uk wrote: This is a call for vote to graduate the Isis podling from Apache Incubator. [x] +1 Graduate Isis podling from Apache Incubator [...] Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, to enable the creation of software using domain-driven design principles, and the realization of this through the naked objects architectural pattern, [...] responsible for the creation and maintenance of software related to and inspired by the naked objects architectural pattern; and be it further It would be clearer if these two statements of scope weren't slightly different. How about simply: [...] related to the naked objects architectural pattern [...] ... for both parts? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Incubator PMC/Board report for Oct 2012 ([ppmc])
Hi Noah... This reminder is for collecting reports which is early enough as the reports are discussed at board meeting 3rd Wednesday from each month. Before reports were collected just one week before the board meeting and some of them were too late to submit there reports and hence the IPMC came up with the idea to collect it max. by the 1st Wednesday of the month. And I believe the reminders are even send more early than that I suppose this one is just a second/another reminder But thanks for being so keen to get things done on the right time :) On Thu, Oct 4, 2012 at 1:19 AM, Noah Slater nsla...@tumbolia.org wrote: I had seen the earlier reminder, but had not made a calendar event for it. So when the 24 hour reminder came in, along with a quick draft that was posted before I checked my email, I felt a little blindsided. Would be nice to have the final call reminder come in 72 hours before the deadline, as is customary in Apache. On Thu, Oct 4, 2012 at 12:15 AM, David Crossley cross...@apache.org wrote: Noah Slater wrote: Can we please adjust this system to send the notice out two days prior? As it stands, this notice gives the project a single day to prepare the board report. As it happens, I missed it, because I didn't check my mail yesterday. Which is annoying, because I had some comments on what was proposed. Can we adjust it so there is, at least, 72 hours notice? These are just reminders. The whole project should be aware of the reporting schedule, now and when TLP. Anyway here is the schedule stuff: http://incubator.apache.org/report-next-month.html http://incubator.apache.org/report-groups.txt These are generated from the main content/podlings.xml file. We should find a link in these archives about the SVN location of the tool that sends the reminders. Someone could adjust it. The code probably also needs some changes, to pick up next month's set of projects, because then firing before the new month. -David -- Forwarded message -- From: Marvin no-re...@apache.org Date: Tue, Oct 2, 2012 at 8:11 PM Subject: Incubator PMC/Board report for Oct 2012 ([ppmc]) To: cloudstack-...@incubator.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 October 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Oct 3rd). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/October2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- NS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi... From all the replies we got so far I don't see any legal concerns and hence I take my question/concern back. In either way, keep the good work OpenMeetings ;) On Mon, Sep 17, 2012 at 10:52 PM, dsh daniel.hais...@gmail.com wrote: Well I still opt to use Meta descriptors such as Maven POMs or CMake (probably only applicable for native projects) files in such cases which would allow to generate Eclipse/IDE you name it specific files once the sources has been obtained. Cheers Daniel On Mon, Sep 17, 2012 at 10:22 PM, sebb seb...@gmail.com wrote: On 14 September 2012 13:57, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. Unfortunately, Eclipse .classpath and .project files are *not* portable; the contents can depend on the individual Eclipse setup. In particular, unless all developers use the same default JDK as required by the project, the classpath files will vary. Also, the .project file will vary if some developers have added certain plugins, e.g. FindBugs or Maven. Having the files in SVN in the location where Eclipse expects to find them will cause problems for some developers, as they will need to modify the files locally in order to build. They cannot commit the files without causing problems for others, and so their workspace will always contain modifications. If you do wish to release IDE build files, I suggest you release them as separate files, e.g. under res/ide-support/eclipse res/ide-support/netbeans etc. The files can be named eclipse.classpath eclipse.profile as files without names can cause problems. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi Alexei... On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Hello Mohammad, thank you for the review. Eclipse can be considered as an alternative build system, so these files are like build.xml files. Why not to keep them in release? 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: Hi I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi Daniel... On Fri, Sep 14, 2012 at 11:11 AM, dsh daniel.hais...@gmail.com wrote: @Mohammad: And btw, in reference to that big (blue) company, I'd say your statement is hearsay and needs to be proofed. For instance why is that very big (blue) company adding their own, proprietary license header to such generated files and in one way or another even Java files are Eclipse-generated in the beginning ;) To be honest I don't remember correctly cause that was since before 2008, but I remember vaguely that I wanted to do something and I was not allowed to because of some rules related to this big (blue) company :D, so I thought it is better to bring that up again maybe someone already know more details or an answer Cheers Daniel On Fri, Sep 14, 2012 at 11:07 AM, dsh daniel.hais...@gmail.com wrote: The more practical and pragmatic question to pose is: why would you want to add license headers to generated files. You would have to take care of that they won't disappear each time the file (e.g. .classpath) is getting re-generated. Again from a practical point of view a mentoring suggestion could be to suggest moving such configuration settings over to Maven over the course of time and let Maven generate the Eclipse project-specific files. Cheers Daniel On Fri, Sep 14, 2012 at 11:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi Benson... On Fri, Sep 14, 2012 at 6:53 PM, Benson Margulies bimargul...@gmail.com wrote: Does anyone seriously believe that IP notices are required in files like these? These files cannot be copyrighted because they do not have any 'creative' content. If they can't be copyrighted, they can't be licensed. And, even it were otherwise, the notices at the top of the tree are sufficient. This isn't the first instance of a 'source' file format that has no provisions for an IP notice. Thanks for the explanation. Then my question/concern is not valid and hence I take it back. On Fri, Sep 14, 2012 at 9:42 AM, dsh daniel.hais...@gmail.com wrote: Well I think Maven allows to create both Eclipse and IDEA IntelliJ projects including metdata artifacts such as .classpath files... Cheers Daniel On Fri, Sep 14, 2012 at 2:57 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: September Reports
Hi Jukka... 1st of all congrats on the new house :) I have some time tonight is there something I can help in ? On Thu, Sep 13, 2012 at 12:49 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, Sep 13, 2012 at 12:25 PM, Benson Margulies bimargul...@gmail.com wrote: I can do it tonight, but I completely missed the assignment email! OK no worries, and thanks! BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: September Reports
Hi On Thu, Sep 13, 2012 at 5:58 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, September 13, 2012 10:54 AM To: general@incubator.apache.org Subject: Re: September Reports Hi, On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I have some time tonight is there something I can help in ? Sure, thanks! It would be great if you could take a look at some of the following reports unless the previously assigned shepherds beat you to it: Matt Franklin- Isis, NPanday, Wave I am in progress with these and will have reviewed them by end of day. Additional eyes don't hurt though. I am not looking into: Bigtop, Openmeetings Matt Hogstrom- Bigtop, Openmeetings BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Bigtop - A Shepherd's View
Hi... The Bigtop community look they doing pretty good and already in their final steps of graduating. -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: September Reports
Hi On Thu, Sep 13, 2012 at 11:10 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi On Thu, Sep 13, 2012 at 5:58 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, September 13, 2012 10:54 AM To: general@incubator.apache.org Subject: Re: September Reports Hi, On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I have some time tonight is there something I can help in ? Sure, thanks! It would be great if you could take a look at some of the following reports unless the previously assigned shepherds beat you to it: Matt Franklin- Isis, NPanday, Wave I am in progress with these and will have reviewed them by end of day. Additional eyes don't hurt though. I am not looking into: Sorry that was a typo: s/not/now Bigtop, Openmeetings Matt Hogstrom- Bigtop, Openmeetings BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Openmeetings - A Shepherd's View
Hi I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Etch, Isis, NPanday and Wave missing reports
Taking a look at it On Mon, Sep 10, 2012 at 9:31 AM, Dan Haywood d...@haywood-associates.co.uk wrote: Hi Jukka, I've just added a report for Isis this morning. Still needs signing off by one of our mentors. Thx Dan ~~~ On 8 September 2012 09:50, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, Please report ASAP so there's enough time for review. If you won't have the report ready by tomorrow, let us know so we can postpone the report to next month. NPanday, since you missed already the August report, it would be really good if we could have a status update now. From the list archive it looks like activity remains alarmingly low, with only Jenkins producing larger volumes of traffic. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Drill into the Apache Incubator
+1 (binding) On Wed, Aug 8, 2012 at 3:55 PM, Grant Ingersoll gsing...@apache.org wrote: On Aug 7, 2012, at 10:41 PM, Ted Dunning wrote: I would like to call a vote for accepting Drill for incubation in the Apache Incubator. The full proposal is available below. Discussion over the last few days has been quite positive. Please cast your vote: [ ] +1, bring Drill into Incubator +1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Incubator release task force
I like the idea, but I suggest to do it in a different way: Why not to have volunteers who are already mentoring different podlings with different sizes of both number of people and the size of code base, these mentors then volunteer: 1- Update the release process docs 2- Report their their experience Which is exactly what you said but the only change IMO is about who should volunteer On Thu, Jul 26, 2012 at 4:10 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, The Incubator ships about half a dozen releases each month on average, but our release process is notoriously lengthy, fraught with problems, and badly documented. If this was any other project, we'd have had a well-oiled release process in place already years ago. Much of our extra release overhead can of course be attributed to the high release manager turnaround (ideally nobody would make more than one or at most a few incubating releases) and the different requirements (source layout, build process, packaging style, distribution channels, etc.) of different podlings. However, there's much that we could do that so far hasn't been done or has been sidetracked. For example, our current release guide [1] is the result of quite a bit of work, but without a clear vision accompanied with a process of incremental improvements it's become a mess that few people read, let alone understand. I'd like to start fixing this by forming a release task force of a handful of volunteers who are ready to invest an hour or two per week to work on a) helping podlings get their releases out, b) migrating /dist/incubator to svnpubsub by the end of this year as requested by infra, c) improving related documentation, and d) proposing updates to the Incubator release policy if needed to streamline the process. In concrete terms I'd like the task force to 1) be the first port of call for podlings who're failing to get enough +1s from their mentors and 2) to contribute a short updates (one sentence to one paragraph) on their progress for inclusion in the monthly Incubator board reports. Anyone interested? [1] http://incubator.apache.org/guides/releasemanagement.html BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Incubator release task force
Hi Gary... On Thu, Jul 26, 2012 at 6:20 PM, Gary Martin gary.mar...@wandisco.comwrote: As someone who is currently attempting to go through their first release, I am not really in the category of someone who could be in such a taskforce. However, I am very interested in seeing an improvement in the release documentation. I would certainly consider looking back over my recent experience to potentially offer suggestions for updating the documentation. It might not be a task that other first time release managers would want to add to their workload but, if this kind of contribution is seen as valuable, I would hope that it would not hurt to ask. Actually I believe you added another aspect that might not be covered by what Jukka suggested, which is people consuming information from such documentation and their feedback how much it is comprehensible and readable, so for sure such feedback would be great. Thanks for your suggestions :) Cheers, Gary On 07/26/2012 03:10 PM, Jukka Zitting wrote: Hi, The Incubator ships about half a dozen releases each month on average, but our release process is notoriously lengthy, fraught with problems, and badly documented. If this was any other project, we'd have had a well-oiled release process in place already years ago. Much of our extra release overhead can of course be attributed to the high release manager turnaround (ideally nobody would make more than one or at most a few incubating releases) and the different requirements (source layout, build process, packaging style, distribution channels, etc.) of different podlings. However, there's much that we could do that so far hasn't been done or has been sidetracked. For example, our current release guide [1] is the result of quite a bit of work, but without a clear vision accompanied with a process of incremental improvements it's become a mess that few people read, let alone understand. I'd like to start fixing this by forming a release task force of a handful of volunteers who are ready to invest an hour or two per week to work on a) helping podlings get their releases out, b) migrating /dist/incubator to svnpubsub by the end of this year as requested by infra, c) improving related documentation, and d) proposing updates to the Incubator release policy if needed to streamline the process. In concrete terms I'd like the task force to 1) be the first port of call for podlings who're failing to get enough +1s from their mentors and 2) to contribute a short updates (one sentence to one paragraph) on their progress for inclusion in the monthly Incubator board reports. Anyone interested? [1] http://incubator.apache.org/**guides/releasemanagement.htmlhttp://incubator.apache.org/guides/releasemanagement.html BR, Jukka Zitting --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
RE: [PROPOSAL] Blur for the Apache Incubator
A pretty cool project and from what I have read in the proposal and the other links I believe the project will do prefect in the incubator phase and will be a perfect addition to ASF. Good luck. Sent from my Samdung Galaxy S3 Apologies for any typos On Jul 18, 2012 9:00 PM, Chen, Pei pei.c...@childrens.harvard.edu wrote: This seems like a very interesting project. Looking forward to see it in Apache... -Original Message- From: Aaron McCurry [mailto:amccu...@gmail.com] Sent: Friday, July 13, 2012 5:24 PM To: general@incubator.apache.org Subject: [PROPOSAL] Blur for the Apache Incubator Hello! I would like to propose Blur to be an Apache Incubator project. Blur is a distributed search platform built for low latency searches over large amounts of data. Blur is scalable and fault tolerant through the use of Hadoop and ZooKeeper. Thrift is used as the RPC library and the underlying search implementation uses Lucene and the Lucene query syntax. The proposal can be found here: http://wiki.apache.org/incubator/BlurProposal I have included the contexts of the proposal below. Thanks! Aaron = Blur Proposal = == Abstract == Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur leverages several existing Apache projects, including Apache Lucene, Apache Hadoop, Apache !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) updates are possible with Blur. Bulk updates are accomplished using Hadoop Map/Reduce and NRT are performed through direct Thrift calls. == Proposal == Blur is an open source search platform capable of querying massive amounts of data at incredible speeds. Rather than using the flat, document-like data model used by most search solutions, Blur allows you to build rich data models and search them in a semi-relational manner similar to joins while querying a relational database. Using Blur, you can get precise search results against terabytes of data at Google-like speeds. Blur leverages multiple open source projects including Hadoop, Lucene, Thrift and !ZooKeeper to create an environment where structured data can be transformed into an index that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for bulk indexing into Blur. Server failures are handled automatically by using !ZooKeeper for cluster state and HDFS for index storage. == Background == Blur was created by Aaron !McCurry in 2010. Blur was developed to solve the challenges in dealing with searching huge quantities of data that the traditional RDBMS solutions could not cope with while still providing JOIN-like capabilities to query the data. Several other open source projects have implemented aspects of this design including elasticsearch, Katta and Apache Solr. == Rationale == There is a need for a distributed search capability within the Hadoop ecosystem. Currently, there are no other search solutions that natively leverage HDFS and the failover features of Hadoop in the same manner as the Blur project. The communities we expect to be most interested in such a project are government, health care, and other industries where scalability is a concern. We have made much progress in developing this project over the past 2 years and believe both the project and the interested communities would benefit from this work being openly available and having open development. In future versions of Blur the API will more closely follow the API's provided in Lucene so that systems that already use Lucene can more easily scale with Blur. Blur can be viewed as a query execution engine that Lucene based solutions can utilize when scale becomes an issue. == Initial Goals == The initial goals of the project are: * To migrate the Blur codebase, issue tracking and wiki from github.comand integrate the project with the ASF infrastructure. * Add new committers to the project and grow the community in The Apache Way. == Current Status == === Meritocracy === Blur was initially developed by Aaron !McCurry in June 2010. Since then Blur has continued to evolve with the support of a small development team at Near Infinity. As a part of the Apache Software Foundation, the Apache Blur team intends to strongly encourage the community to help with and contribute to the project. Apache Blur will actively seek potential committers and help them become familiar with the codebase. === Community === A small community has developed around Blur and several project teams are currently using Blur for their big data search capability. The source code is currently available on GitHub and there is a dedicated website (blur.io) that provides an overview of the project. Blur has been shared with several members of the Apache community and has been presented at the Bay Area HUG (see http://www.meetup.com/hadoop/events/20109471/). === Core Developers === The current developers are employed by Near
Re: Incubation state transitions and stuck projects (Was: February report review)
Hi Sent from my Samdung Galaxy S3 Apologies for any typos On Jul 16, 2012 1:41 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Sun, Jul 15, 2012 at 11:02 AM, Ross Gardler rgard...@opendirective.com wrote: This is great stuff. It implies the ComDev PPMC ought to focus on the low diversity trap while Incubator focuses on more process driven IP, release, graduation. Sounds good. Of course this means we should figure our exactly what low diversity is. As discussed recently low diversity is not a problem if the project can demonstrate it is open to newcomers. Right. I'm even thinking that we should drop the low diversity label and simply replace it with a more generic not yet ready to graduate one until we have a better shared understanding of the things podlings falling into that category still need to do. Not ready for graduation is also too generic, for thw low diversity case we can have of lacking to attract new committers , in that case maybe the podling community can explain why to the IPMC also /w the help of Mentors and hence we are able to evaluate whether the reasons are really valid not to graduate or not For examle Isis is a very active and healthy community but it took a while till new blood comes into the community, which is changing recently but I believe it happens to other podlings as well But in general as u mentioned more investigations about categories of such cases is idd required Given I committed to find a way for ComDev to support the Incubation process do you think this is a starting point? Yes. Going through all the podlings in that category and trying to spot common patterns and areas of potential trouble or improvement would be my first step here. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][RFC] Fediz for the Apache Incubator
Hi Jean... I added myself, lets go for a [VOTE] :) On Mon, Nov 21, 2011 at 10:52 AM, Jean-Baptiste Onofré j...@nanthrax.netwrote: Hi all, To be able to start a formal vote, we need an additional mentor. Is someone interested ? Thanks, Regards JB On 11/11/2011 11:49 PM, Jean-Baptiste Onofré wrote: Thanks for the update Marcel, and sorry for the late answer. I updated the Fediz proposal with your comment. Thanks again, Regards JB On 11/03/2011 12:40 PM, Marcel Offermans wrote: On Nov 1, 2011, at 10:22 AM, Jean-Baptiste Onofré wrote: http://wiki.apache.org/**incubator/FedizProposalhttp://wiki.apache.org/incubator/FedizProposal Definitely an interesting proposal! Just a comment on the affiliations section: isn't it true that both Olivier Lamy and Colm O'hEigeartaigh are also working for Talend? Of course part of the incubation process will be to attract other developers, I just think it's fair to list affiliations for all initial committers. Greetings, Marcel --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL][RFC] Fediz for the Apache Incubator
ROFL Sorry I was checking my old e-mails and I didn't notice the date :D what a dump reply did I send :D On Tue, Jul 3, 2012 at 1:20 PM, Jean-Baptiste Onofré j...@nanthrax.netwrote: Hi Mohammad, the proposal has been retired as Fediz is now a subproject of Apache CXF. Thanks anyway for your proposal ! Regards JB On 07/03/2012 12:37 PM, Mohammad Nour El-Din wrote: Hi Jean... I added myself, lets go for a [VOTE] :) On Mon, Nov 21, 2011 at 10:52 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi all, To be able to start a formal vote, we need an additional mentor. Is someone interested ? Thanks, Regards JB On 11/11/2011 11:49 PM, Jean-Baptiste Onofré wrote: Thanks for the update Marcel, and sorry for the late answer. I updated the Fediz proposal with your comment. Thanks again, Regards JB On 11/03/2011 12:40 PM, Marcel Offermans wrote: On Nov 1, 2011, at 10:22 AM, Jean-Baptiste Onofré wrote: http://wiki.apache.org/incubator/FedizProposalhttp://wiki.apache.org/**incubator/FedizProposal http:/**/wiki.apache.org/incubator/**FedizProposalhttp://wiki.apache.org/incubator/FedizProposal Definitely an interesting proposal! Just a comment on the affiliations section: isn't it true that both Olivier Lamy and Colm O'hEigeartaigh are also working for Talend? Of course part of the incubation process will be to attract other developers, I just think it's fair to list affiliations for all initial committers. Greetings, Marcel --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org general-**unsubscribe@incubator.apache.**orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.** **orggeneral-help@incubator.**apache.orggeneral-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --** --**- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org general-**unsubscribe@incubator.apache.**orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org general-help@incubator.**apache.org general-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Board will be proposing a new TLP
+1 on the proposal itself and how it will go directly through the board I also agree /w what has been said and replied to by both Emmanuel Alex On Jun 30, 2012 3:32 PM, Alex Karasulu akaras...@apache.org wrote: On Sat, Jun 30, 2012 at 3:53 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Le 6/30/12 2:23 PM, Jim Jagielski a écrit : Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... Sure we should go through incubation, to make sure the peeps being STV code *knows* about the Apache Way... Or is this simple non-sense ? No I don't think this is non-sense. However note that as Jim pointed out, the difference here, that would favor the direct TLP route, is the fact that everyone working on the voting tool are already Apache Committers and Members. Conceivably they already know the Apache Way. Then again a quick incubation process might help get an extra sanity check from the Incubator. Your point makes sense considering outside participants to build a larger community around the tool. Incubation might be a good environment for a mass influx of new to Apache, interested parties to participate. But it does not sound like they're going to be directly involved, knocking on our doors immediately. Also there's no IP to vet. I presume this is more a matter of making the software an official Apache Product with PMC endorsed releases that other organizations like OpenStack can use immediately. +1 Setup TLP without incubation, yet I can understand arguments for a quick incubation. -- Best Regards, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Steve
Looks good to me +1 :) On Jun 30, 2012 12:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Sat, Jun 30, 2012 at 12:03 PM, Sam Ruby ru...@intertwingly.net wrote: This so far has lead us to the conclusion that there really isn't any incubating that needs to be done. I'd like to open the topic up for discussion. Here's what I wrote about this on board@: There's plenty of precedent of existing TLPs spawning off subprojects without having them first go through the Incubator, and I don't see why stuff from infra would need to be treated differently. However, there's also precedent of TLPs bringing subprojects to the Incubator to grow the community and to evaluate when critical mass for a TLP has been reached. I'd say it's up to infra and the people who're already working on the STV tools to decide which path to follow. The Incubator would of course be happy to help (in the ways it can), but I see no hard reason why the Incubator would absolutely need be involved if a good enough community already exists for a TLP. To kick things off, I'd copy the draft ASF Board resolution into the incubator wiki, but apparently SamRuby is not in the ContributorsGroup. Fixed. If somebody could rectify that and/or copy the resolution into the wiki, I would appreciate that. There's not much to see there, it simply is a routine resolution, full of words like WHEREAS, THEREFORE, and RESOLVED. https://svn.apache.org/repos/private/foundation/board/apache-steve.txt Not sure if it needs to be on the wiki, so for now I'm just including a copy of the proposed resolution below: 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, for distribution at no charge to the public, related to voting systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Steve Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Steve Project be and hereby is responsible for the creation and maintenance of software related to voting systems; and be it further RESOLVED, that the office of Vice President, Apache Steve 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 Steve Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Steve 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 Steve Project: * Jim Jagielski j...@apache.org * Chris A. Mattmann mattm...@apache.org * Sam Ruby ru...@apache.org * Greg Stein gst...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be appointed to the office of Vice President, Apache Steve, 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 Steve Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Steve Project. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Allura to enter the Incubator
+1 (binding) On Thu, Jun 21, 2012 at 10:50 PM, Olivier Lamy ol...@apache.org wrote: +1 (binding) 2012/6/21 Rich Bowen rbo...@rcbowen.com: Hi, We are proposing Allura to be admitted to the Apache Incubator, and would like to request that the IPMC votes on this issue. The requisite 72 hours has passed since the initial proposal. The proposal may be found at http://wiki.apache.org/incubator/AlluraProposal Please cast your vote. [ ] +1 I recommend that Allura becomes an Apache Incubator project [ ] 0 Abstain or don't care [ ] -1 No, I do not recommend that Allura becomes an Apache Incubator project yet (because ...) -- Rich Bowen rbo...@rcbowen.com :: @rbowen rbo...@apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Prototype ASF Mailing List Request form
Nice work Sam ;) May I suggest adding some fields to ease data entry even more: 1- A checkbox indicating whether or not the mailing list is for an incubator project or not 2- Another list of checkboxes which are enabled only when the incubator checkbox is enabled: 2.1- Dvelopment 2.2- Commits 2.3- Private 2.4- Users(*) For the first three ones they can be checked by default as they are required by all Incubator projects, the last one for users can be checked sometimes when a new podling is in need for a users list This will ease data entry a lot for new podlings instead of making a new request for each mailing list a mentor can just in one request send all data required by the tool On Sun, May 27, 2012 at 1:41 PM, Daniel Shahaf d...@daniel.shahaf.namewrote: Daniel Shahaf wrote on Sun, May 27, 2012 at 14:12:54 +0300: Nick Kew wrote on Sat, May 26, 2012 at 07:39:48 +0100: On 26 May 2012, at 03:54, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... [foo] @ [bar] .apache.org ? The form is ASF wide. You guys will enter incubator for [bar]. What about a toggle for a private list? Or is that determined on name alone? Easy to add if there's a use case. apmail hat on, I would still like sanity checking to avoid the case where someone requests a foo-private list and forgets to tick the Make it private? checkbox. There _is_ a use case: some f...@apache.org lists will need such an option. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Shepherds for podling reports
Hi Alan For sure your point may be valid, but the whole point, if you read the whole thread from the beginning, which I am sure you did, you will notice that Jukka mentioned that this is a start and will assess the effort and the whole plan after giving it sometime. And actually having other people looking into reports, from one side that will help mentors and from the other side it is as mentioned by Alex a fresh eye, who can poke around and ask questions or even provide more help. On Sat, May 5, 2012 at 8:50 PM, Alan D. Cabrera l...@toolazydogs.comwrote: On May 5, 2012, at 11:07 AM, Benson Margulies wrote: If you don't want to be a Shepherd, don't sign up. Yeah, I get that part. The board asked us to do a better job of reviewing reports and detecting mentor deficiencies. I get that too. This is a plan to accomplish that. My opinion about the plan stands. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Shepherds for podling reports
Hi Alan... On Sun, May 6, 2012 at 12:05 AM, Alan D. Cabrera l...@toolazydogs.comwrote: Thanks for replying with a thoughtful response. Jukka put forth the idea of shepherds as a proposal. I was merely replying to that proposal with my own considered ideas. I am encouraged about the enthusiasm but I feel that it blurs the responsibility of the mentor. Shepherding the shepherds of a podling, i.e. mentors, seems to me like the wrong way to go. It does add process. If one carefully re-reads posts to this thread there's all sorts of extra complexity being considered such as groupings of podlings and clearly defining the rules for cross-cutting projects, etc. Not that this is what's going to finally be adopted. Incubation is confusing enough as it is. Sprinkling more process, roles, and bureaucracy is not the solution to, my mind, mentors who need to be politely pinged. This is just my humble opinion. With that said, the shepherds have my sincere best wishes and I am happy to cooperate for those podlings where I am mentor. Thanks again for your kind reply. You still have a point, but lets give it a try and adjust the idea along the way :), maybe come up with another idea if this didn't work out Regards, Alan On May 5, 2012, at 1:04 PM, Mohammad Nour El-Din wrote: Hi Alan For sure your point may be valid, but the whole point, if you read the whole thread from the beginning, which I am sure you did, you will notice that Jukka mentioned that this is a start and will assess the effort and the whole plan after giving it sometime. And actually having other people looking into reports, from one side that will help mentors and from the other side it is as mentioned by Alex a fresh eye, who can poke around and ask questions or even provide more help. On Sat, May 5, 2012 at 8:50 PM, Alan D. Cabrera l...@toolazydogs.com wrote: On May 5, 2012, at 11:07 AM, Benson Margulies wrote: If you don't want to be a Shepherd, don't sign up. Yeah, I get that part. The board asked us to do a better job of reviewing reports and detecting mentor deficiencies. I get that too. This is a plan to accomplish that. My opinion about the plan stands. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Shepherds for podling reports
Hi Jukka... I also added myself, but as being a Mentor of CloudStack I would rather take (shepherdZ: DeltaSpike, Nuvem, Wink) while Dave Fisher takes (shepherdY: CloudStack, NPanday, VCL) Dave would you please ACK that ? On Fri, May 4, 2012 at 2:54 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, May 3, 2012 at 11:14 PM, Dave Fisher dave2w...@comcast.net wrote: This looks like a mind expanding activity. I added my name for a maximum of 2 per month. Great, thanks! Would you mind taking a look at for example Nuvem and Wink this month? Or pick some other yet unclaimed reports. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Shepherds for podling reports
On Fri, May 4, 2012 at 8:27 PM, Greg Stein gst...@gmail.com wrote: In the Board agenda, we have a line where each Director can state they have reviewed the report (before the meeting). They can also append queries and comments. Little mini-discussions kinda happen in those comments. Point here is: provide a similar location for IPMC members (including shepherds) to list their review/approval. There is no strict need to divvy the reviews. Jukka is doing that as a transitionary measure until people get into it. IOW, there is no big deal if both Mohammad and Dave review Nuvem and Wink. The real goal is at least one or more IPMC names associated with each podling report. (beyond mentor signoffs?) Another way to say it: Mohammad: go ahead and review all six. No big deal if there is overlap. (and if you believe six is a problem, then avoid becoming a Director; we review something like 40 to 50... month after month... :-P) Well, I can start rehearsing with 6 reports preparing for the 40-50 ones :P It is this early review and signoff that is behind the need for receiving reports in advance of the meeting. The hope is that all reports have been reviewed by (all) the Directors beforehand, so we don't have to discuss them in detail during the meeting. We stop and discuss when a Director leaves a flag/query/concern in the report comments. Cheers, -g On May 4, 2012 12:35 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Jukka... I also added myself, but as being a Mentor of CloudStack I would rather take (shepherdZ: DeltaSpike, Nuvem, Wink) while Dave Fisher takes (shepherdY: CloudStack, NPanday, VCL) Dave would you please ACK that ? On Fri, May 4, 2012 at 2:54 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, May 3, 2012 at 11:14 PM, Dave Fisher dave2w...@comcast.net wrote: This looks like a mind expanding activity. I added my name for a maximum of 2 per month. Great, thanks! Would you mind taking a look at for example Nuvem and Wink this month? Or pick some other yet unclaimed reports. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] CloudStack for Apache Incubator
I believe this [VOTE] is ready to be wrapped up Kevin ;) On Fri, Apr 13, 2012 at 3:46 PM, Jim Jagielski j...@jagunet.com wrote: On Apr 9, 2012, at 9:32 PM, Kevin Kluge wrote: Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. The proposal is available at [1] and I have also included it below. Please vote with: +1: accept CloudStack into Incubator +0: don't care -1: do not accept CloudStack into Incubator (please explain the objection) The vote is open for at least 72 hours from now (until at least 19:00 US-PST on April 12, 2012). Thanks for the consideration. -kevin [1] http://wiki.apache.org/incubator/CloudStackProposal +1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding) On Tue, Apr 10, 2012 at 8:55 AM, Emmanuel Lécharny elecha...@gmail.comwrote: +1: accept CloudStack into Incubator (binding) -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
Hi On Thu, Apr 5, 2012 at 8:03 AM, Kevin Kluge kevin.kl...@citrix.com wrote: I updated the proposal at http://wiki.apache.org/incubator/CloudStackProposal. I have included the embedded source dependencies, binary dependencies, and contributor e-mail addresses. There are some open questions in the dependencies (e.g., treatment of dependencies that have no discernible license), but my impression is that these issues do not need resolution before entering incubation. Please correct me if that's wrong. I didn't look into the updated version of the proposal, but in general yes such issues can be solved while being in the Incubator. I believe the proposal is now complete, pending additional feedback. Give it some more few time and if no more feedback or comments I believe you are ready to start a [VOTE] on the final proposal -kevin -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
Hi... On Wed, Apr 4, 2012 at 9:41 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Wed, Apr 4, 2012 at 7:57 AM, Kevin Kluge kevin.kl...@citrix.com wrote: Citrix is pursuing patents based on prior CloudStack work and expects to continue to do so in the future. Citrix is getting these patents to protect the CloudStack user community. Consider the case where some other entity states that the use of CloudStack is infringing on their patents. Citrix could use these patents to fight this entity and defend the community. An incremental benefit is that if Citrix (or any other CloudStack-friendly entity) has a patent then that patent cannot be acquired by an unfriendly entity. Anyone with about $15B can buy Citrix, and start wreaking havoc with the patents. See Google with its acquisition of Motorola, or Oracle with its acquisition of Sun (Java?). Or Citrix can sell its patent portfolio to a shell company, keeping a license and let the shell start suing the rest of the world (see Apple, Microsoft etc). There are many avenues to abuse the patents. I read section 3 of [1], and AFAIU and if the above scenario hold does this mean that such company X can sue ASF for example ? Sorry if it is a stupid question but I am no lawyer at all :). [1]- http://www.apache.org/licenses/LICENSE-2.0.html Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
On Wed, Apr 4, 2012 at 10:20 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Apr 4, 2012 at 8:55 PM, Matt Hogstrom m...@hogstrom.org wrote: The proposal looks good. I'm excited that the community is looking to grow at the ASF. I'm working on similar technology in my day job at IBM and am interested in getting involved. Happy to mentor if you need, although, it has quite a large list now as I look at the Wiki. The number of mentors should not be an issue. As stated before, in other threads, the number of mentors is unbounded and AOO has 8 as an example. The perspective podling should not feel that the list is too long - more mentors and interest is a good thing. We have much to do, the project is not small, and it would be nice to see the community gracefully pass thru incubation as fast as posible in accordance with incubator standards. More mentors might help in this regard. Indeed -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: CloudStack?
Quoting: ...will become the first cloud platform in the industry to be submitted to the Apache Software Foundation http://www.apache.org/,... They mentioned that it is to be submitted The title is misleading, I am not sure if that is a problem ? Is it ? On Tue, Apr 3, 2012 at 5:47 PM, Nóirín Plunkett noi...@apache.org wrote: See Jim's email (subject CloudStack) of an hour ago. N On Tue, Apr 3, 2012 at 8:46 AM, Brian McCallister bri...@skife.org wrote: I don't remember seeing anything about a CloudStack project, is there something I missed? http://www.citrix.com/English/NE/news/news.asp?newsID=2323072 -Brian - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: CloudStack?
On Tue, Apr 3, 2012 at 6:30 PM, Kevin Kluge kevin.kl...@citrix.com wrote: Hi All, thanks for the interest in CloudStack. I'm working on the wiki page at this moment. I'll send out a proposal notice later today. Then hurry up, cause we are looking forward to it ;) -kevin -Original Message- From: Nóirín Plunkett [mailto:noi...@apache.org] Sent: Tuesday, April 03, 2012 8:48 AM To: general@incubator.apache.org Subject: Re: CloudStack? See Jim's email (subject CloudStack) of an hour ago. N On Tue, Apr 3, 2012 at 8:46 AM, Brian McCallister bri...@skife.org wrote: I don't remember seeing anything about a CloudStack project, is there something I missed? http://www.citrix.com/English/NE/news/news.asp?newsID=2323072 -Brian - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
[DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)
I don't see that this getting to any clear end yet. So I suggest that we take this from a Sqoop instance to be a discussion on rules them selves. I would like to start a [VOTE] about whether it is a *must* for podlings to rename all packages before being a TLP or not over keeping the old package names for backward compatibility. What ever the consensus going to be built we definitely need to update the Incubator documents to clear this kind of issue. But before starting the vote I would like to consider others' opinions. Thoughts ? On Wed, Feb 29, 2012 at 10:33 AM, Alex Karasulu akaras...@apache.orgwrote: On Wed, Feb 29, 2012 at 2:40 AM, Patrick Hunt ph...@apache.org wrote: On Tue, Feb 28, 2012 at 4:02 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On the other hand, I totally respect that Cloudera's interest to support their customers and provide backword compatibility, but this is *not* the point at all, the point is this *should* not, and even allow me to say this is *must* not be the problem of Apache, and yes I agree with the opinion that this is a matter to be decided by Sqoop team but not to make Apache's problem. So also let not get more into this!!! Or course this is Apache's problem. You can't have your cake and eat it too. If you accept code for a project you accept the community as well. Say Apache accepts a project like Open Office, should we ignore the existing community and not concern ourselves with backward compatibility for that project as well, because the original code wasn't birthed at Apache? That's a very slippery slope. Maybe some projects get way too much leeway because of the big flashing lights. Regardless of how big the press headlines are all projects should be held to the same standard. No project should be allowed to graduate without solving all issues pertaining to marks. It's a failure of the incubator in the past for allowing other projects to do so. I'm shocked it was allowed. -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi Greg... On Wed, Feb 29, 2012 at 1:06 PM, Greg Stein gst...@gmail.com wrote: On Feb 29, 2012 4:15 AM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 4:06 AM, Daniel Kulp dk...@apache.org wrote: On Wednesday, February 29, 2012 1:13:30 AM Mohammad Nour El-Din wrote: Hi Daniel... On Wed, Feb 29, 2012 at 1:07 AM, Daniel Kulp dk...@apache.org wrote: We had a very similar discussion about the back word compatibility classes/package names when Subversion graduated and we deemed it OK for them. In fact, I believe they still of org.tigris packages in their codebase long after graduation. See: http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javah l/src/org/ I don't see why we would or should hold Sqoop to a different or higher standard at this point. I agree with Jukka that if we, as a foundation, would like to re-address this, fine, take it to trademarks@ and start a discussion. However, from an INCUBATOR standpoint, the precedent and expectations have been set. That's my $0.02 cents worth. Thanks a lot for this, but would you elaborate more on why this has been accepted ? My believe is that there is some clarification that should be added to documentation so it is more clear for all people in the future, your input on this example would help indeed. You could likely read the mail archives if you want all the details. general@incubator in Nov 2009 had a thread, dev@subversion in Jan 2010 had a thread, and I think the graduation vote in Feb 2010 had more discussions. Basically, the Subversion had binary compatibility rules and there was no real legal requirement to force a huge disruption in the community by changing the package names. The project had a plan to deprecate them/create wrappers/whatever so when it was appropriate to break compatibility they would. Did they remove those packages or did they remain? They remain. Keeping them is the right thing for our community and product. That is our determination, and is our Right. That is what we are trying to figure out here, and that is why we have this discussion :) Sqoop has determined backwards compatibility is important to their community and wants to keep this (deprecated) interface for a while. So where is the problem here, people? Really. What is the problem with the extra interfaces? No body is trying to make any problems to any other one here, we are just trying to make sure that things are done as it should be There is no legal (trademark or copyright) problem that I'm aware of. There is no technical problem that I'm aware of. So what is it? Why are people all up in Sqoop's face here? Why is there some attempt at imposing technical changes on them? What ASF-wide policy is being broken? If the policy doesn't exist, but you think it *should*, then please state as much, along with a resolution for the Board to consider, in order to make it official policy. And if/when the Board *does* make it official policy, then the graduated/TLP PMC can ensure their code base complies. Again and as I started in one of my earlier e-mails, no one is trying to impose anything on Sqoop or any other project, it is something that needs to be discussed and thats all, and the vote neither cancelled nor postponed, we still have time till next board meeting and we here trying to sort things out to see, as you also explained below, if it is a real issue which needs to be raised to the board or not, if not then there is nothing to talk about and thing will go as planned for Sqoop or any other podling will propose for being graduated in the future. So I agree with you it is not a Sqoop thing at all it is more about ASF itself. And please note: this imputed/proposed policy will affect Subversion packaging, too. Your rationale for mandates on Sqoop package names must be able to apply just as well to Subversion. Don't focus on just Sqoop, but the overall Foundation-wide issue. If you send a resolution to the Board, then it better be backed up with an explanation of why the Board should be getting involved in Java package naming for projects across the Foundation. The explanation should state the problem, and how the policy (via the resolution) will solve that problem. Totally agree, and again we are still discussing if it should be raised to the board and then stated and an ASF policy or not, and in the former case sure there must plans for already existing projects how to adapt to that and sure giving them the proper time window, but again there is no reason going into this hassle if there is no consensus on making an issue out of it. I see no reason for the Incubator to reverse a vote that has been completed, and to do so in the name of some nebulous/unstated policy. It is exactly
Re: [DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)
Yes I did, and thanks for clarification :), and please read my as well :). Thanks. On Wed, Feb 29, 2012 at 1:15 PM, Greg Stein gst...@gmail.com wrote: Has nothing to do with incubation. You're talking about Foundation-wide policy. You cannot impose different naming rules on podlings, than what is imposed on TLPs. Please see my response in the original thread. You need a Board resolution and rationale. -g On Feb 29, 2012 5:03 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I don't see that this getting to any clear end yet. So I suggest that we take this from a Sqoop instance to be a discussion on rules them selves. I would like to start a [VOTE] about whether it is a *must* for podlings to rename all packages before being a TLP or not over keeping the old package names for backward compatibility. What ever the consensus going to be built we definitely need to update the Incubator documents to clear this kind of issue. But before starting the vote I would like to consider others' opinions. Thoughts ? On Wed, Feb 29, 2012 at 10:33 AM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 2:40 AM, Patrick Hunt ph...@apache.org wrote: On Tue, Feb 28, 2012 at 4:02 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On the other hand, I totally respect that Cloudera's interest to support their customers and provide backword compatibility, but this is *not* the point at all, the point is this *should* not, and even allow me to say this is *must* not be the problem of Apache, and yes I agree with the opinion that this is a matter to be decided by Sqoop team but not to make Apache's problem. So also let not get more into this!!! Or course this is Apache's problem. You can't have your cake and eat it too. If you accept code for a project you accept the community as well. Say Apache accepts a project like Open Office, should we ignore the existing community and not concern ourselves with backward compatibility for that project as well, because the original code wasn't birthed at Apache? That's a very slippery slope. Maybe some projects get way too much leeway because of the big flashing lights. Regardless of how big the press headlines are all projects should be held to the same standard. No project should be allowed to graduate without solving all issues pertaining to marks. It's a failure of the incubator in the past for allowing other projects to do so. I'm shocked it was allowed. -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi Greg... On Wed, Feb 29, 2012 at 2:03 PM, Greg Stein gst...@gmail.com wrote: On Feb 29, 2012 7:32 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Greg... On Wed, Feb 29, 2012 at 1:06 PM, Greg Stein gst...@gmail.com wrote: ... They remain. Keeping them is the right thing for our community and product. That is our determination, and is our Right. That is what we are trying to figure out here, and that is why we have this discussion :) ... Again and as I started in one of my earlier e-mails, no one is trying to impose anything on Sqoop or any other project, What? I've seen people say the vote should be canceled, that Sqoop needs to yank the code, etc. Those are most certainly impositions. I was talking about myself actually here and, sorry for the confusion. But even everybody has freedom to express there *opinions* and *ideas* we are not gods here, so even if some people said that the vote should be cancelled that does not mean it is cancelled or it will be cancelled immediately or in the future, it is still a *discussion* after all. This is no mere discussion; it is some number of people attempting to impose some unstated policy upon Sqoop before allowing them to graduate. ... I gave it more thought and IMO, I think we should raise the issue to the Board to get to some results, Raise what issue? I have not seen a statement of the problem, other than projects sometimes deem it necessary to use package names in addition to org.apache. But I don't see the problem in that. Could you at least explain here before bringing a question to the Board? If it is legal in nature, then it should go to legal-discuss. You got this point wrong, I am not saying to raise an issue immediately, what I am saying is that we discuss that before raising it as an issue to the board *if any*. For the legal-discuss I believe it is a good idea to bring that to them as well. I believe the more input we get the clearer things are. Cheers, -g -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)
On Wed, Feb 29, 2012 at 2:32 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 2:15 PM, Greg Stein gst...@gmail.com wrote: Has nothing to do with incubation. You're talking about Foundation-wide policy. You cannot impose different naming rules on podlings, than what is imposed on TLPs. Please see my response in the original thread. You need a Board resolution and rationale. I'm glad you phrased it like this. It totally takes us out of the scope of the perceived problem. As you say you have to apply the same rules until policies change, if they change. You're amazingly cogent dude! It's a strong argument that I can't disagree with even though I am convinced the perceived problem is quite serious. I'll withdraw my veto on the other VOTE thread but I really want to evaluate this in this discussion thread. I agree with this, I believe that Sqoop deserve to be graduated for a lot of reasons and even the discussion in hand it is not all their fault it is fault of Mentors and a problem of lacking of clear information about such situation, so IMO as I explained before we proceed with the vote and bring that issue in a more general ASF wide level. -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)
Hi... On Wed, Feb 29, 2012 at 2:44 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 3:32 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 2:15 PM, Greg Stein gst...@gmail.com wrote: Has nothing to do with incubation. You're talking about Foundation-wide policy. You cannot impose different naming rules on podlings, than what is imposed on TLPs. Please see my response in the original thread. You need a Board resolution and rationale. I'm glad you phrased it like this. It totally takes us out of the scope of the perceived problem. As you say you have to apply the same rules until policies change, if they change. You're amazingly cogent dude! It's a strong argument that I can't disagree with even though I am convinced the perceived problem is quite serious. I'll withdraw my veto on the other VOTE thread but I really want to evaluate this in this discussion thread. OK to get back on track with this discussion I've taken a snippet from the original thread and pasted it here: They remain. Keeping them is the right thing for our community and product. That is our determination, and is our Right. Sorry but I don't think that's right. Sqoop has determined backwards compatibility is important to their community and wants to keep this (deprecated) interface for a while. So where is the problem here, people? It's fine but those com.cloudera packages don't need to be hosted here. They can be hosted elsewhere and the backwards compatibility issue can still be handled. Really. What is the problem with the extra interfaces? The package namespace is not ours. It's that simple G. There is no legal (trademark or copyright) problem that I'm aware of. There is no technical problem that I'm aware of. OK do we have the right to create any kind of package or class under com.cloudera (or any other companies packages)? I'd like to approach it by answering this question. Because if we look at it like this then we'll start seeing the issues this could cause. That is a good question! -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi Alex On Wed, Feb 29, 2012 at 2:39 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 3:07 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 2:06 PM, Greg Stein gst...@gmail.com wrote: On Feb 29, 2012 4:15 AM, Alex Karasulu akaras...@apache.org wrote: On Wed, Feb 29, 2012 at 4:06 AM, Daniel Kulp dk...@apache.org wrote: On Wednesday, February 29, 2012 1:13:30 AM Mohammad Nour El-Din wrote: Hi Daniel... On Wed, Feb 29, 2012 at 1:07 AM, Daniel Kulp dk...@apache.org wrote: We had a very similar discussion about the back word compatibility classes/package names when Subversion graduated and we deemed it OK for them. In fact, I believe they still of org.tigris packages in their codebase long after graduation. See: http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javah l/src/org/ I don't see why we would or should hold Sqoop to a different or higher standard at this point. I agree with Jukka that if we, as a foundation, would like to re-address this, fine, take it to trademarks@ and start a discussion. However, from an INCUBATOR standpoint, the precedent and expectations have been set. That's my $0.02 cents worth. Thanks a lot for this, but would you elaborate more on why this has been accepted ? My believe is that there is some clarification that should be added to documentation so it is more clear for all people in the future, your input on this example would help indeed. You could likely read the mail archives if you want all the details. general@incubator in Nov 2009 had a thread, dev@subversion in Jan 2010 had a thread, and I think the graduation vote in Feb 2010 had more discussions. Basically, the Subversion had binary compatibility rules and there was no real legal requirement to force a huge disruption in the community by changing the package names. The project had a plan to deprecate them/create wrappers/whatever so when it was appropriate to break compatibility they would. Did they remove those packages or did they remain? They remain. Keeping them is the right thing for our community and product. That is our determination, and is our Right. Sorry but I don't think that's right. Sqoop has determined backwards compatibility is important to their community and wants to keep this (deprecated) interface for a while. So where is the problem here, people? It's fine but those com.cloudera packages don't need to be hosted here. They can be hosted elsewhere and the backwards compatibility issue can still be handled. Really. What is the problem with the extra interfaces? The package namespace is not ours. It's that simple G. There is no legal (trademark or copyright) problem that I'm aware of. There is no technical problem that I'm aware of. OK do we have the right to create any kind of package or class under com.cloudera (or any other companies packages)? Greg's right. Jukka was as well but for some reason I did not immediately get it. We cannot hold Scoop to a standard which we don't apply to other TLPs and this needs to be a Foundation wide policy discussion. I still think the practice of bundling classes and packages which are not in our namespace is a serious issue. I'll take this up the other discussion thread. I am withdrawing my veto and I apologize for any inconvenience this may have caused the Scoop community. No need for any apologies at all, we are all one team and such discussions IMHO are important and also healthy cause it helps making things clear and more explicit which IMO makes ASF a better place to live :) -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Good catch On Mon, Feb 27, 2012 at 9:10 PM, Alan Gates ga...@hortonworks.com wrote: The source code in Sqoop still exists in both com.cloudera.sqoop and org.apache.sqoop packages and most of the code appears to include the com.cloudera packages and not the org.apache packages. While in the incubator this seems fine. Are we ok with this in a TLP? I couldn't find any policy statements on it in the Apache pages. No this is not OK with a TLP Alan. On Feb 24, 2012, at 1:34 PM, Arvind Prabhakar wrote: This is a call for vote to graduate Sqoop podling from Apache Incubator. Sqoop entered Incubator in June of 2011. Since then it has added three new committers from diverse organizations, added two new PPMC members, and made two releases following the ASF policies and guidelines. The community of Sqoop is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Sqoop community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Sqoop podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Sqoop podling [ ] -1 Reject graduation of Sqoop podling from Apache Incubator This vote will be open for 72 hours. Please find the proposed board resolution below. [1] http://markmail.org/thread/xwhjtkik7pgrmypi [2] http://s.apache.org/sqoop Thanks, Arvind Prabhakar X. Establish the Apache Sqoop 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 efficiently transferring bulk data between Apache Hadoop and structured datastores 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 Sqoop Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is responsible for the creation and maintenance of software related to efficiently transferring bulk data between Apache Hadoop and structured datastores; and be it further RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Sqoop 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 Sqoop Project: * Aaron Kimball kimba...@apache.org * Andrew Bayer aba...@apache.org * Ahmed Radwan ah...@apache.org * Arvind Prabhakar arv...@apache.org * Bilung Leeb...@apache.org * Greg Cottman gcott...@apache.org * Guy le Marguyle...@apache.org * Jaroslav Cechojar...@apache.org * Jonathan Hsiehjmhs...@apache.org * Olivier Lamy ol...@apache.org * Paul Zimdars pzimd...@apache.org * Roman Shaposhnik r...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar be appointed to the office of Vice President, Apache Sqoop, 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 Sqoop 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 Sqoop Project; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Sqoop podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Sqoop 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: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi... 1st of all, and I speaking about myself here, I believe this is partially my fault cause I am one of the mentors of Sqoop and I should have spotted such thing before moving the vote to general@ I totally agree with Alex, more specifically I believe this is easy to solve. There is no problem to support some features or API(s) for backward compatibility but as Alex stated it should not be part of Apache's code, more specifically when it comes to be part of a TLP's code. The solution can be like packaging this code and host it on Cloudera or even Apache Extras [1] and a note is added to Sqoop website that if users want to have backward compatibility they should use that code besides the code of Apache. Now the question is, and I ask this more specifically to the Sqoop people, Can you do this before the next board meeting, at least the extracting that code ? Cause if not I support Alex in that this vote should be cancelled and then we work out another one when Sqoop meets this criteria. Looking forward to your feedback! [1] - http://code.google.com/a/apache-extras.org/hosting/ On Tue, Feb 28, 2012 at 10:44 AM, Alex Karasulu akaras...@apache.orgwrote: On Tue, Feb 28, 2012 at 11:06 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasulu akaras...@apache.org wrote: Cloudera's compatibility issues are not our problem. These packages need to go. Citation needed. I did not think we needed one: nor do I have one. It's common sense to me that this causes issues. It combines the namespace of a foreign mark with our own. We should not be releasing anything in the namespace belonging to another entity. Without a written policy to that effect these things are up for each project to decide. Jarek's rationale sounds perfectly fine to me. I highly respect you opinion here but I disagree regarding this argument provided. There may be no policy to cite, and there may be examples of where this was done before for the sake of backwards compatibility. It still does not justify doing it. We have plenty of projects that provide such backwards compatibility wrappers or otherwise put stuff in non-apache namespaces for various reasons. See for example [1] or [2]. Understood. Examples are solid points supporting the argument but IMHO I think this was a mistake that opens the door to several issues. Maybe we need some clear policy regarding the matter. I'm more than ready to be proven wrong on this matter so long as it does not present problems down the line for us. [1] http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/ [2] http://svn.apache.org/repos/asf/geronimo/specs/trunk/ BR, Jukka Zitting -- Best Regards, -- Alex -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
On Tue, Feb 28, 2012 at 3:01 PM, Ate Douma a...@douma.nu wrote: On 02/28/2012 01:46 PM, Mohammad Nour El-Din wrote: Hi... 1st of all, and I speaking about myself here, I believe this is partially my fault cause I am one of the mentors of Sqoop and I should have spotted such thing before moving the vote to general@ I totally agree with Alex, more specifically I believe this is easy to solve. There is no problem to support some features or API(s) for backward compatibility but as Alex stated it should not be part of Apache's code, more specifically when it comes to be part of a TLP's code. I agree. And specifically as this seems to concern compatibility support for Cloudera own API, only needed for Cloudera customers. Keeping those com.cloudera packages in the code could imply a specific preference and affiliation with an external and commercial entity, thereby potentially jeopardizing the project independence. While I don't expect there was any intend to do so, even the impression itself can be considered harmful to the ASF and the project. The solution can be like packaging this code and host it on Cloudera or even Apache Extras [1] and a note is added to Sqoop website that if users want to have backward compatibility they should use that code besides the code of Apache. That sounds reasonable and hopefully easy to do (if not this case might even be more worrisome then). I'm not really sure though if Apache Extras is an appropriate location either. I think Apache Extras intends to convey an affiliation with the ASF and probably should value project independence high as well. If this really only concerns a thin layer to provide compatibility only for Cloudera's API, hosting and maintenance of this should be the responsibility of Cloudera itself. Good point, I agree on this Ate Now the question is, and I ask this more specifically to the Sqoop people, Can you do this before the next board meeting, at least the extracting that code ? Cause if not I support Alex in that this vote should be cancelled and then we work out another one when Sqoop meets this criteria. Looking forward to your feedback! [1] - http://code.google.com/a/**apache-extras.org/hosting/http://code.google.com/a/apache-extras.org/hosting/ On Tue, Feb 28, 2012 at 10:44 AM, Alex Karasuluakaras...@apache.org** wrote: On Tue, Feb 28, 2012 at 11:06 AM, Jukka Zittingjukka.zitting@gmail.** com jukka.zitt...@gmail.com wrote: Hi, On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasuluakaras...@apache.org wrote: Cloudera's compatibility issues are not our problem. These packages need to go. Citation needed. I did not think we needed one: nor do I have one. It's common sense to me that this causes issues. It combines the namespace of a foreign mark with our own. We should not be releasing anything in the namespace belonging to another entity. Without a written policy to that effect these things are up for each project to decide. Jarek's rationale sounds perfectly fine to me. I highly respect you opinion here but I disagree regarding this argument provided. There may be no policy to cite, and there may be examples of where this was done before for the sake of backwards compatibility. It still does not justify doing it. We have plenty of projects that provide such backwards compatibility wrappers or otherwise put stuff in non-apache namespaces for various reasons. See for example [1] or [2]. Understood. Examples are solid points supporting the argument but IMHO I think this was a mistake that opens the door to several issues. Maybe we need some clear policy regarding the matter. I'm more than ready to be proven wrong on this matter so long as it does not present problems down the line for us. [1] http://svn.apache.org/repos/**asf/subversion/trunk/** subversion/bindings/javahl/http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/ [2] http://svn.apache.org/repos/**asf/geronimo/specs/trunk/http://svn.apache.org/repos/asf/geronimo/specs/trunk/ BR, Jukka Zitting -- Best Regards, -- Alex --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi all... I don't think that anyone here is trying to underestimate or saying anything bad about Sqoop in general or about Cloudera people in particular. And I agree on the point that this vote was more about evaluating whether the Sqoop community succeeded to adapt to the Apache way of doing open source software or not, and I still believe that they did very good job. So lets not get into this by any how!!! On the other hand, I totally respect that Cloudera's interest to support their customers and provide backword compatibility, but this is *not* the point at all, the point is this *should* not, and even allow me to say this is *must* not be the problem of Apache, and yes I agree with the opinion that this is a matter to be decided by Sqoop team but not to make Apache's problem. So also let not get more into this!!! Even if there is no explicit rules about that, which is something I really have to look into, again I believe it shouldn't be Apache's problem and if thats the case the relevant documents should be updated and on behalf on others, sorry if I am speaking in name of others here, but I thank the Sqoop team to bring that issue so we know that we need to make things more clear and precise which is also the role of IPMC as part of Apache. IMHO lets be pragmatic and cut into the chase and seek answers and solutions. As I stated before, but I still didn't get any answers, how much of work this needs to get it done ? I will assume two available answers: 1- It can be done before the next board meeting and hence there is no problem at all and the vote still valid. 2- If not, we have two options: 2.1 We still make the vote valid but Mentors they *must* make sure that such issue is resolved as a checklist item of the graduation process steps, which I would prefer 2.2 Vote is cancelled and required changes are discussed by the PPMC preparing for the next vote iteration I would urge all involved to focus on these options or other options if available, the whole purpose here is to make things better, to make Apache way better and more clear which is not only the role of IPMC but it is the role of everyone involved with Apache including Sqoop community itself, which I am sure they are willing to help as much as possible. Sorry for the long e-mail :) Looking forward to your reply! On Wed, Feb 29, 2012 at 12:18 AM, Alex Karasulu akaras...@apache.orgwrote: On Wed, Feb 29, 2012 at 12:59 AM, Arvind Prabhakar arv...@apache.org wrote: On Tue, Feb 28, 2012 at 2:50 PM, Alex Karasulu akaras...@apache.org wrote: On Tue, Feb 28, 2012 at 11:39 PM, Arvind Prabhakar arv...@apache.org wrote: On Tue, Feb 28, 2012 at 1:25 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Tue, Feb 28, 2012 at 9:53 PM, Patrick Hunt ph...@apache.org wrote: On Tue, Feb 28, 2012 at 12:24 PM, Alan D. Cabrera a...@toolazydogs.com wrote: Opps, I didn't see that Arvind concluded the vote. I still stand by my opinion that there are some things that are not solely up to the people that are doing the work. Complete migration to the the org.apache.* package space is one of them. No worries. I respect your opinion and if Apache feels that this is important enough to make explicit then certainly Sqoop should make the changes. Short of that I don't see why we should hold Sqoop to a higher standard than is expected of other Apache projects. (that's _my_ opinion ;-) ) Right. Basically the graduation vote by the IPMC is about determining whether the PPMC is capable of conducting itself according to the Apache Way and Apache policies on it's own. I didn't have time to look deeper into Sqoop yet, but all the +1s in this vote suggest that the Sqoop PPMC is ready to take on that responsibility. Along with that responsibility comes the right to make value judgements on topics like this where existing policies aren't clearly spelled out. Thanks Jukka. In fact, Sqoop already has a plan in place to completely remove com.cloudera.* namespace from its contents via the next major revision of the product. The work for that has already started and currently exists under the branch sqoop2 [3], tracked by SQOOP-365 [4]. We hope that in a few months time, we will have feature parity in this branch with the trunk, which is when we will promote it to the trunk. [3] https://svn.apache.org/repos/asf/incubator/sqoop/branches/sqoop2/ [4] https://issues.apache.org/jira/browse/SQOOP-365 Personally I think we should let the vote result stand with guidance to the new Sqoop PMC to discuss the matter with the branding team at trademarks@ to seek Apache-wide consensus. I encourage anyone who feels strongly about this (the point being made clearly has some merit) make their case to trademarks@ as it's IMHO not really the task of the Incubator to be forming new
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
Hi Daniel... On Wed, Feb 29, 2012 at 1:07 AM, Daniel Kulp dk...@apache.org wrote: We had a very similar discussion about the back word compatibility classes/package names when Subversion graduated and we deemed it OK for them. In fact, I believe they still of org.tigris packages in their codebase long after graduation. See: http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/src/org/ I don't see why we would or should hold Sqoop to a different or higher standard at this point. I agree with Jukka that if we, as a foundation, would like to re-address this, fine, take it to trademarks@ and start a discussion. However, from an INCUBATOR standpoint, the precedent and expectations have been set. That's my $0.02 cents worth. Thanks a lot for this, but would you elaborate more on why this has been accepted ? My believe is that there is some clarification that should be added to documentation so it is more clear for all people in the future, your input on this example would help indeed. Dan On Tuesday, February 28, 2012 10:25:41 PM Jukka Zitting wrote: Hi, On Tue, Feb 28, 2012 at 9:53 PM, Patrick Hunt ph...@apache.org wrote: On Tue, Feb 28, 2012 at 12:24 PM, Alan D. Cabrera a...@toolazydogs.com wrote: Opps, I didn't see that Arvind concluded the vote. I still stand by my opinion that there are some things that are not solely up to the people that are doing the work. Complete migration to the the org.apache.* package space is one of them. No worries. I respect your opinion and if Apache feels that this is important enough to make explicit then certainly Sqoop should make the changes. Short of that I don't see why we should hold Sqoop to a higher standard than is expected of other Apache projects. (that's _my_ opinion ;-) ) Right. Basically the graduation vote by the IPMC is about determining whether the PPMC is capable of conducting itself according to the Apache Way and Apache policies on it's own. I didn't have time to look deeper into Sqoop yet, but all the +1s in this vote suggest that the Sqoop PPMC is ready to take on that responsibility. Along with that responsibility comes the right to make value judgements on topics like this where existing policies aren't clearly spelled out. Personally I think we should let the vote result stand with guidance to the new Sqoop PMC to discuss the matter with the branding team at trademarks@ to seek Apache-wide consensus. I encourage anyone who feels strongly about this (the point being made clearly has some merit) make their case to trademarks@ as it's IMHO not really the task of the Incubator to be forming new policy on this, especially with all the recent talk about scaling down the ambitions of the IPMC. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Graduation of Lucy to TLP
Hi... 1st of all congrats. I have only one question/comment, in the charter draft why you call it Apache Lucy Project why not just Apache Lucy ? On Sat, Feb 18, 2012 at 9:16 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1, amen to that, brother. Time to Lucy to become a TLP! Cheers, Chris On Feb 17, 2012, at 9:50 AM, Chris Hostetter wrote: : The Apache Lucy community feels ready to graduate from the Incubator. As the Lucy Champion Mentor I think the Lucy community has definitely reached self sufficience and self direction. In aggregate, the the Lucy PPMC knows as much about the Apache Way as any of the members, and they've satisfied all of the criteria for graduation, so I don't see any reason why they should continue to stay in the Incubator. There is certainly room for growth, but that's true of every Apache project -- they can continue do it as a TLP just as easily as a podling... : * five releases : * three new PPMC members : * five new committers -Hoss - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Graduation of Lucy to TLP
Yeah I am sorry thats my mistake :)
On Thu, Feb 23, 2012 at 1:30 AM, Marvin Humphrey mar...@rectangular.comwrote:
On Thu, Feb 23, 2012 at 01:27:31AM +0100, Mohammad Nour El-Din wrote:
1st of all congrats.
Thanks!
I have only one question/comment, in the charter draft why you call it
Apache Lucy Project why not just Apache Lucy ?
That language is in the template:
https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache ${PROJECT} Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
Cheers,
Marvin Humphrey
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Thanks
- Mohammad Nour
Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein
Re: [VOTE] Graduate Sqoop from Apache Incubator
Hi Matt... Allow me to disagree with you :), there is no confusion but the problem is that most of the people click on reply to all which includes general@address by mistake most probably they don notice it. On Sun, Feb 19, 2012 at 6:43 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Arvind, Okey dok, just thought if you were going to cut down on confusion, it might make sense to *not* include general@, regardless of the guidelines :) Otherwise, some IPMC person like me might think (regardless of what you put in your email) that you are intending it as a VOTE for the IPMC. That's why they are, guidelines, but I don't think they are perfect. Anyhoo, I'll just ignore the VOTE thread on general@, and assume that it's really for the Sqoop PPMC at this point. Cheers, Chris //notes to self, maybe I should go update those guidelines, as they don't //make sense to me, but who doesn't have the energy to do so at this point. I can look into that today or tomorrow :) On Feb 19, 2012, at 9:38 AM, Arvind Prabhakar wrote: Thanks Chris for your feedback. Yes, this vote is only intended to be held in the Sqoop community. However, according to the guide on graduation [2], the guidance on community graduation vote explicitly suggests copying the Incubator general list when the vote is proposed. Hence, I added the general list in the cc of the vote mail. Also, I do state explicitly in the vote mail that if this community vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. When we do draft the board resolution proposal it will have details about initial PMC. [2] http://incubator.apache.org/guides/graduation.html#tlp-community-vote Thanks, Arvind Prabhakar On Sun, Feb 19, 2012 at 9:24 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Arvind, I would encourage removing another ambiguity that I saw -- I think you meant to only hold this on sqoop-dev, right? That's because by the time it gets to the IPMC, at least one thing I'm interested in is the proposed PMC, if there are 3 ASF members or not, etc., and that would be part of the resolution that you guys haven't drafted yet. If you hold this on general@, then before VOTE'ing I would like to see the proposed graduation resolution. There's a bunch of templates, here's the one that Lucy just used: http://wiki.apache.org/lucy/LucyCharter Thanks! Cheers, Chris On Feb 19, 2012, at 9:19 AM, Arvind Prabhakar wrote: Hi, I will have to cancel this vote thread due to a typo in the vote options in my original mail below. Specifically, the option to reject the vote is mentioned as +1 when it should be -1 instead. In order to make sure that there is absolutely no ambiguity in the vote, I will send out a new vote thread in a few minutes. My sincere apologies for the inconvenience. Thanks, Arvind Prabhakar On Sun, Feb 19, 2012 at 1:00 AM, Arvind Prabhakar arv...@apache.org wrote: The Apache Sqoop project entered incubator in June of 2011. Since then we have added three new committers from diverse organizations and added two new PPMC members. The codebase of our product has steadily grown and we have made two releases following the ASF policies and guidelines. Thanks to the excellent mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Sqoop continues to attract interest from contributors and users from all across the world. Given these milestones, I strongly feel that Sqoop is ready to graduate from Incubator. The first step towards graduation is to vote as a community that Sqoop is ready to graduate. If the vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. The complete graduation process is described [1]. Please cast your votes: [ ] +1 Graduate Sqoop from Incubator [ ] +0 Indifferent to graduation status of Sqoop [ ] +1 Reject graduation of Sqoop from Incubator This vote will remain open for at least 72 hours from now. [1] http://incubator.apache.org/guides/graduation.html Thanks, Arvind Prabhakar ++ 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 ++
Re: svn commit: r1291238 - in /incubator/public/trunk/site-publish: index.html projects/awf.html projects/index.html
Thanks sebb On Tue, Feb 21, 2012 at 5:00 AM, sebb seb...@gmail.com wrote: On 20 February 2012 13:07, elecha...@apache.org wrote: Author: elecharny Date: Mon Feb 20 13:07:13 2012 New Revision: 1291238 URL: http://svn.apache.org/viewvc?rev=1291238view=rev Log: Updated the site to reflect the deft-awf renaming Added: incubator/public/trunk/site-publish/projects/awf.html Next time, please set eol-style:native on new files. Modified: incubator/public/trunk/site-publish/index.html incubator/public/trunk/site-publish/projects/index.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: svn commit: r1291363 - /incubator/public/trunk/site-author/projects/isis.xml
On Tue, Feb 21, 2012 at 9:16 AM, Dan Haywood d...@haywood-associates.co.ukwrote: Forgive my ignorance... is there any guidance on how to do that regeneration that you could point me to...? Dan On 21 February 2012 03:58, sebb seb...@gmail.com wrote: On 20 February 2012 16:52, danhayw...@apache.org wrote: Author: danhaywood Date: Mon Feb 20 16:52:18 2012 New Revision: 1291363 URL: http://svn.apache.org/viewvc?rev=1291363view=rev Log: Updating Isis project summary after 0.2.0-incubating release Modified: incubator/public/trunk/site-author/projects/isis.xml Next time please regenerate the site and commit the updated html version of the file. Good catch, thanks sebb for sending the notice! Modified: incubator/public/trunk/site-author/projects/isis.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects/isis.xml?rev=1291363r1=1291362r2=1291363view=diff == --- incubator/public/trunk/site-author/projects/isis.xml [utf-8] (original) +++ incubator/public/trunk/site-author/projects/isis.xml [utf-8] Mon Feb 20 16:52:18 2012 @@ -26,9 +26,9 @@ titleNews/title ul -li2010-09-07 Isis has been accepted to enter incubation/li - +li2012-02-20 Released version 0.2.0-incubating/li li2011-07-14 Released version 0.1.2-incubating/li +li2010-09-07 Isis has been accepted to enter incubation/li /ul /section @@ -274,20 +274,20 @@ ul li - a href=http://wiki.apache.org/incubator/October2010#Isis October - 2010/a + a + href=http://wiki.apache.org/incubator/December2011#Isis December + 2011/a /li li a - href=http://wiki.apache.org/incubator/November2010#Isis November - 2010/a + href=http://wiki.apache.org/incubator/September2011#Isis September + 2011/a /li li - a - href=http://wiki.apache.org/incubator/December2010#Isis December - 2010/a + a href=http://wiki.apache.org/incubator/June2011#Isis June + 2011/a /li li @@ -296,20 +296,20 @@ /li li - a href=http://wiki.apache.org/incubator/June2011#Isis June - 2011/a + a + href=http://wiki.apache.org/incubator/December2010#Isis December + 2010/a /li li a - href=http://wiki.apache.org/incubator/September2011#Isis September - 2011/a + href=http://wiki.apache.org/incubator/November2010#Isis November + 2010/a /li li - a - href=http://wiki.apache.org/incubator/December2011#Isis December - 2011/a + a href=http://wiki.apache.org/incubator/October2010#Isis October + 2010/a /li /ul /section - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: svn commit: r1291363 - /incubator/public/trunk/site-author/projects/isis.xml
On Tue, Feb 21, 2012 at 9:16 AM, Dan Haywood d...@haywood-associates.co.ukwrote: Forgive my ignorance... is there any guidance on how to do that regeneration that you could point me to...? Hi Dan, 1st of all it is our fault as Mentors but sure would appreciate your help in that! Take a look at [1] [1] - http://incubator.apache.org/guides/website.html#Edit+your+project+status+report Dan On 21 February 2012 03:58, sebb seb...@gmail.com wrote: On 20 February 2012 16:52, danhayw...@apache.org wrote: Author: danhaywood Date: Mon Feb 20 16:52:18 2012 New Revision: 1291363 URL: http://svn.apache.org/viewvc?rev=1291363view=rev Log: Updating Isis project summary after 0.2.0-incubating release Modified: incubator/public/trunk/site-author/projects/isis.xml Next time please regenerate the site and commit the updated html version of the file. Modified: incubator/public/trunk/site-author/projects/isis.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects/isis.xml?rev=1291363r1=1291362r2=1291363view=diff == --- incubator/public/trunk/site-author/projects/isis.xml [utf-8] (original) +++ incubator/public/trunk/site-author/projects/isis.xml [utf-8] Mon Feb 20 16:52:18 2012 @@ -26,9 +26,9 @@ titleNews/title ul -li2010-09-07 Isis has been accepted to enter incubation/li - +li2012-02-20 Released version 0.2.0-incubating/li li2011-07-14 Released version 0.1.2-incubating/li +li2010-09-07 Isis has been accepted to enter incubation/li /ul /section @@ -274,20 +274,20 @@ ul li - a href=http://wiki.apache.org/incubator/October2010#Isis October - 2010/a + a + href=http://wiki.apache.org/incubator/December2011#Isis December + 2011/a /li li a - href=http://wiki.apache.org/incubator/November2010#Isis November - 2010/a + href=http://wiki.apache.org/incubator/September2011#Isis September + 2011/a /li li - a - href=http://wiki.apache.org/incubator/December2010#Isis December - 2010/a + a href=http://wiki.apache.org/incubator/June2011#Isis June + 2011/a /li li @@ -296,20 +296,20 @@ /li li - a href=http://wiki.apache.org/incubator/June2011#Isis June - 2011/a + a + href=http://wiki.apache.org/incubator/December2010#Isis December + 2010/a /li li a - href=http://wiki.apache.org/incubator/September2011#Isis September - 2011/a + href=http://wiki.apache.org/incubator/November2010#Isis November + 2010/a /li li - a - href=http://wiki.apache.org/incubator/December2011#Isis December - 2011/a + a href=http://wiki.apache.org/incubator/October2010#Isis October + 2010/a /li /ul /section - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Graduate Sqoop from Apache Incubator
Hi :) On Tue, Feb 21, 2012 at 2:28 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Oh Mohammad, On Feb 21, 2012, at 2:06 AM, Mohammad Nour El-Din wrote: Hi Matt... s/Matt/Chris/ Allow me to disagree with you :), there is no confusion but the problem is that most of the people click on reply to all which includes general@address by mistake most probably they don notice it. Hehe, semantics, semantics. OK, fine, how's this, consider *me* confused, that better? I know that you are much smarter not to be confused, I just wanted to express my different PoV :D On Sun, Feb 19, 2012 at 6:43 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Arvind, Okey dok, just thought if you were going to cut down on confusion, it might make sense to *not* include general@, regardless of the guidelines :) Otherwise, some IPMC person like me might think (regardless of what you put in your email) that you are intending it as a VOTE for the IPMC. That's why they are, guidelines, but I don't think they are perfect. Anyhoo, I'll just ignore the VOTE thread on general@, and assume that it's really for the Sqoop PPMC at this point. Cheers, Chris //notes to self, maybe I should go update those guidelines, as they don't //make sense to me, but who doesn't have the energy to do so at this point. I can look into that today or tomorrow :) Thanks man. Cheers, Chris ++ 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: Mentors as the core of the IPMC
On Thu, Feb 9, 2012 at 7:38 PM, Mark Struberg strub...@yahoo.de wrote: Imo it's always good to have a few pair of (active!) eyes having oversight. It's just simply too easy to miss something important - even for a long-time committed mentor. True, it is also important about how they co-ordinate with each other and fill the playing the role of a mentor for each other in case on mentor was active and then he/she got busy the other picks it up from there, that is much better than they are all active or they are all not active. LieGrue, strub - Original Message - From: Jim Jagielski j...@jagunet.com To: general@incubator.apache.org Cc: Sent: Friday, February 3, 2012 2:58 PM Subject: Mentors as the core of the IPMC One thing I would like to be bantered about: Long ago, it was customary to have a single mentor for a podling. Nowadays, the feelings are the more, the merrier. Has the above been an experiment which succeeded, failed or is moot? Justify your decision. - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Apache Isis release 0.2.0-incubating (RC3)
+1 (binding) On Sat, Feb 18, 2012 at 9:26 PM, Benson Margulies bimargul...@gmail.comwrote: +1 On Fri, Feb 17, 2012 at 10:02 AM, Dan Haywood d...@haywood-associates.co.uk wrote: Isis is in the process of voting on 0.2.0-incubating (RC3). The thread below has the details, along with current votes cast. We still need one more +1 from a member before we can release. I'd like to close this vote in 72 hours from now, to ensure adequate time for oversight from the IPMC and hopefully to attract the +1 additional member vote that we need Many thanks Dan -- Forwarded message -- From: Dan Haywood d...@haywood-associates.co.uk Date: 17 February 2012 09:01 Subject: Re: [VOTE] Apache Isis release 0.2.0-incubating (RC3) To: isis-...@incubator.apache.org My +1, for the record. We currently have +2 members (Mark, Benson) and +3 others (Kevin, Robert, Matthew). I'm going to forward this thread to the Incubator IPMC because it needs approval there and also, hopefully, to pick up the additional +1 from a member. Dan On 10 February 2012 15:36, Dan Haywood d...@haywood-associates.co.uk wrote: All, I've staged a release candidate for Apache Isis, namely 0.2.0-incubating (RC3) The artifacts have been staged to staging repository on repository.apache.org: * https://repository.apache.org/content/repositories/orgapacheisis-216/org/apache/isis/isis/0.2.0-incubating/isis-0.2.0-incubating-source-release.zip(zipfile) * https://repository.apache.org/content/repositories/orgapacheisis-216/org/apache/isis/isis/0.2.0-incubating/isis-0.2.0-incubating-source-release.zip.asc(signature) In Subversion the code has been tagged as tags/isis-0.2.0-incubating/framework. I've also uploaded a new version of the site at http://incubator.apache.org/isis-0.2.0-incubating. The contributors guide on the site contains some suggestions of how to verify the release, see http://incubator.apache.org/isis-0.2.0-incubating/docbkx/html/guide/ch12.html . Please note that RAT check is now configured in the parent pom.xml and can now be performed using mvn org.apache.rat:apache-rat-plugin:check. Please verify the release and cast your vote. The vote will be open for a minimum of 72 hours. [ ] +1 [ ] 0 [ ] -1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
