Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
+1 of course from me, with a commitment to doing work to help out and making sure this doesn't fail; instead that it succeeds which I'm sure it will. I'll also sign up for a round of beers at the next ApacheCon. For sure! :) 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 7:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project So here's a thought... There have been many discussions about different ways to incubate projects. One of the most radical ideas is to dismantle the incubator and replace the podling concept with probationary TLPs reporting to the board. As readers of this list will know I do not support the idea of dismantling the IPMC. I believe it does a great job that is not easily replaced by a board of nine directors. However, I have always acknowledged that the idea has merit under a certain set of circumstances. For me those circumstances are present in the Apache Stratos proposal. That is there are sufficient mentors and initial committers who are ASF Members that we can be reasonably certain that this project will succeed here at the ASF. I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. For my part my intention is to get the project set-up and then dissolve into the background. I do not intend to monitor the project on a day-to-day basis. However, I do promise to help pick up the pieces if the experiment should go horribly wrong. Of course running a single experiment will only allow us to define the incubation process for probationary TLPs, It is not going to solve all the problems Chris sees in the IPMC. However it will give us an opportunity to define the process, ask the board to approve this process and thus lay the foundations for other projects wishing to follow this path. So, what do you think? Ross On 11 June 2013 10:10, 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/|Ia aS]]-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
Re: [VOTE] Graduation of Apache Mesos
Looks good! +1 On Wed, Jun 12, 2013 at 10:03 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi All, The Apache Mesos community is ready to graduate. They have added committers and PPMC members while in the Incubator; have made a few releases; are discussing their issues on list and in the Apache way, and are inclusive and representative of Apache's goals as a Foundation. I'm extremely happy to put them up for Incubator graduation. We've VOTEd as a community to move forward with this: DISCUSS thread here: http://s.apache.org/XAu VOTE thread here: http://s.apache.org/K8C VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov Project Incubator status page here: http://incubator.apache.org/projects/mesos.html Board resolution pasted at bottom of email. Existing tallies from the community VOTE: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik * - indicates IPMC Please VOTE to graduate Apache Mesos from the Incubator. Though only Incubator PMC member VOTEs are binding, all are welcome to voice your opinion. I'll leave the VOTE open for at least 72 hours, and hopefully can get enough VOTEs in time to close it by Saturday or Sunday in time for the board meeting on 6/19. [ ] +1 Graduate Apache Mesos from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Mesos from the Incubator because.. Thanks everyone! Cheers, Chris ---board resolution WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to efficient cluster management, resource isolation and sharing across distributed applications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Mesos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mesos Project be and hereby is responsible for the creation and maintenance of software related to efficient cluster management, resource isolation and sharing across distributed applications; and be it further RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mesos 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 Mesos Project: * Ali Ghodsi a...@apache.org * Andy Konwinski and...@apache.org * Benjamin Hindhman b...@apache.org * Benjamin Mahler bmah...@apache.org * Brian McCalister bri...@apache.org * Ian Holsman i...@apache.org * Matei Alexandru Zahari ma...@apache.org * Chris Mattmann mattm...@apache.org * Tom White tomwh...@apache.org * Vinod Kone vinodk...@apache.org * Brenden Matthews bren...@apache.org * Thomas Marshall tmarsh...@apache.org * Charles Reiss wog...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be appointed to the office of Vice President, Apache Mesos, 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 Apache Mesos Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Mesos podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Mesos podling encumbered upon the Apache Incubator Project are hereafter discharged. ++ 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 -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail:
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 04:56, Alan Cabrera l...@toolazydogs.com wrote: On Jun 12, 2013, at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote: So here's a thought... ... I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. ... So, what do you think? I don't see the need to force Stratos through the Incubator given the current proposed membership. Some points: Who's responsible for monitoring the probation, the IPMC or the board? I think it should be the IPMC. I think we should come up with a concrete plan then go to the board. If the board is OK with taking it on then it should be board as this will be closer to Chris' defined end goal. In either case I undertake, as I noted in my original mail, to be the one that steps up to fix things if it all goes wrong. That's true whether it is IPMC or Board. What bits must absolutely be done before probation begins? That needs to be defined. Given the fact the next board meeting is only a week away I suggest we first make this a podling to allow us to start the project here at the ASF. We can then work with the various committees to work out what the right set-up process is (i.e. don't set up as a podling, set up as a pTLP). We can then shoot for submitting a board resolution next month. I have already made it clear to the proposers of the project that taking this route will result in a slightly longer set-up period (because of the need to define new policies along the way). They are comfortable trading slower set-up for potentially faster graduation. What minimum criteria does a probationary TLP have to meet to stay in good graces? Exactly the same as any other TLP. What happens if the probationary TLP is not in good graces? Exactly the same as any other TLP. The board says fix it. If it isn't fixed the board kicks out the problem element(s) and invites remaining PMC to fix it. If that failes the pTLP is sent packing. What bits must absolutely be done before probation completes? Same as graduation from the Incubator (a release, demonstration of a healthy community, approval of the board) Fleshing out these and, I'm sure, others' concerns on a wiki, as Joe pointed out, would be a great idea. Yes, but please note my proposal to do this as a standard podling rather than in this discussion phase. I don't think we need everything in a row before the team can get to work. If it should prove impossible to find a sensible process then we can simply leave the project as a standard podling. So to recap the proposed timeline: - IPMC votes on accepting the podling with the intention of moving it to a pTLP - mentors (with Chris' assistance) guide project committers in working with the various committees to define incubation/probation process - submit a board resolution in July to create the pTLP - if project is not ready to do so this can be delayed until August - If the board are unhappy with the project then I am called in to clear up the mess I made - If the board are happy with progress submit a resolution to become a TLP in 12 months (target 6 months) Ross Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 04:04, Sanjiva Weerawarana sanj...@wso2.com wrote: On Thu, Jun 13, 2013 at 8:27 AM, David Nalley da...@gnsa.us wrote: ccing trademarks@ Note the mix of public and private lists. Yeah we also thought about that .. if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. Better to get an answer to the question up front IMO. +1. Better yes - required before we can vote - no. My reasoning is that WSO2 have already agreed they will use a different name if VP Branding requires it. In fact they won't have any choice since the proposal clearly indicates the Stratos trademark will be assigned to the ASF. That said I encourage someone on the project commit list to mail trademarks@ to understand what would be acceptable. Ross Ross The thinking is to not give that a specific name but rather call it the WSO2 distribution of Apache Stratos (or something like that). I don't think that's one of the 'sanctioned' uses of marks from: In fact, per the below page, it's explicitly forbidden. http://www.apache.org/foundation/marks/faq/#products Hmm that idea was based on how Cloudera is distributing Hadoop: http://www.cloudera.com/content/cloudera/en/products/cdh.html Is that also incorrect then? IIRC they've been doing that for years and presumably ASF is aware of it? Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
Ross, thanks for bringing this up! I'm happy to be a part of this experiment. On 13 June 2013 09:13, Ross Gardler rgard...@opendirective.com wrote: Better yes - required before we can vote - no. My reasoning is that WSO2 have already agreed they will use a different name if VP Branding requires it. In fact they won't have any choice since the proposal clearly indicates the Stratos trademark will be assigned to the ASF. While owning the Stratos trademark would certainly put us in a position of being able to ask WSO2 to stop using StratosLive. But there's no guarantee that we would be successful. Case in point: Apache CouchDB and Couchbase. We are very uncomfortable with the name Couchbase, but there's not much we can do about it. Certainly, asking them to rebrand is not going to work. (Full disclosure: I am on the PMC and have been dealing with this mess for over a year.) Couchbase causes us problems because CouchDB's progenitor left CouchDB and founded Couchbase, and made a public statement to the effect that Couchbase was the future of CouchDB. This caused a lot of market confusion, with many people (understandably) thinking that Couchbase replaced CouchDB. You still see the effects of that today. Our support channels are littered with confused Couchbase customers. And I am sure many people who would have been CouchDB users end up downloading and installing Couchbase products. So my concern with StratosLive is: would there be consumer confusion between Apache Stratos and WSO2 StratosLive? My gut tells me: yes. In many people's minds, there will already be some uncertainty about provenance, and so the name will only compound that confusion. I learnt two lessons from the Couchbase fiasco: 1. You need to be mindful of third-parties using your trademark in a compound name. Many people use couch as a sort of adjective. Couch-this and Couch-that. And in one sense, this is great, because couch is this term that is bigger than Apache CouchDB. But at the same time, the meaning is diffuse. And in many ways, the CouchDB community has little control over it. We have plans to remedy that situation, but they are not relevant here. 2. You need to apply branding rules consistently. We allowed Couchbase (and others) to share our brand because they were seen as friendly to the community. (And indeed, for many years, they were hugely beneficial for the project.) Unfortunately, that sets precedent. And it's hard to rewind precedent. It also leaves you vulnerable to the possibility that they won't always be friendly. At which point, you're gonna be SOL. On 13 June 2013 04:04, Sanjiva Weerawarana sanj...@wso2.com wrote: The thinking is to not give that a specific name but rather call it the WSO2 distribution of Apache Stratos (or something like that). I don't think that's one of the 'sanctioned' uses of marks from: In fact, per the below page, it's explicitly forbidden. http://www.apache.org/foundation/marks/faq/#products Hmm that idea was based on how Cloudera is distributing Hadoop: http://www.cloudera.com/content/cloudera/en/products/cdh.html Is that also incorrect then? IIRC they've been doing that for years and presumably ASF is aware of it? The ASF is aware of it, but I don't think we're happy with it. Shane will have more thoughts on this. -- NS
Re: [RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator
Woo hoo! \o/ On 13 June 2013 02:34, Henry Saputra henry.sapu...@gmail.com wrote: Hi All, Thank you for everyone for participating and warm welcome for the MetaModel project proposal. The VOTE is now officially closed with the result (* means IPMC): +1s: Henry Saputra* Matt Franklin* Chris Mattmann* Noah Slater* Rahul Sharma Ankit Kumar Christian Grobmeier* Arvind Prabhakar* Kasper Sorensen Noah Slater* Manuel Van den Berg Joe Brockmeier* Suresh Marru* Ted Dunning* Rich Bowen Alan Cabrera* Marcel Offermans* Alex Karasulu* 0s: None -1s: None This means with 18 +1s (13 binding) and no 0 and -1 the proposal is accepted. I will continue with the bootstrap process to bring MetaModel into Apache incubator. Thank you again for those participated in the VOTE. Thanks, Henry On Thu, Jun 6, 2013 at 3:30 PM, Henry Saputra henry.sapu...@gmail.com wrote: Hi All, I'd like to call a VOTE for acceptance of MetaModel into the Apache incubator. The vote will close on June 12, 2013 at 6:00 PM (PST). [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is: http://wiki.apache.org/incubator/MetaModelProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Henry Saputra Champion for Apache MetaModel P.S. Here's my +1 (binding) - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a
RE: [RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator
I also want to shout out a big woo hoo! :-) Sincerely, this is cool news - I am very happy about it. And colleagues here at Human Inference are also cheering. So we really hope to make it a good apache project! From: Noah Slater [nsla...@apache.org] Sent: 13 June 2013 12:08 To: general@incubator.apache.org Subject: Re: [RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator Woo hoo! \o/ On 13 June 2013 02:34, Henry Saputra henry.sapu...@gmail.com wrote: Hi All, Thank you for everyone for participating and warm welcome for the MetaModel project proposal. The VOTE is now officially closed with the result (* means IPMC): +1s: Henry Saputra* Matt Franklin* Chris Mattmann* Noah Slater* Rahul Sharma Ankit Kumar Christian Grobmeier* Arvind Prabhakar* Kasper Sorensen Noah Slater* Manuel Van den Berg Joe Brockmeier* Suresh Marru* Ted Dunning* Rich Bowen Alan Cabrera* Marcel Offermans* Alex Karasulu* 0s: None -1s: None This means with 18 +1s (13 binding) and no 0 and -1 the proposal is accepted. I will continue with the bootstrap process to bring MetaModel into Apache incubator. Thank you again for those participated in the VOTE. Thanks, Henry On Thu, Jun 6, 2013 at 3:30 PM, Henry Saputra henry.sapu...@gmail.com wrote: Hi All, I'd like to call a VOTE for acceptance of MetaModel into the Apache incubator. The vote will close on June 12, 2013 at 6:00 PM (PST). [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is: http://wiki.apache.org/incubator/MetaModelProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Henry Saputra Champion for Apache MetaModel P.S. Here's my +1 (binding) - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules
Re: [VOTE] Graduation of Apache Mesos
+1 (binding) On Thu, Jun 13, 2013 at 10:39 AM, Christian Grobmeier grobme...@gmail.comwrote: Looks good! +1 On Wed, Jun 12, 2013 at 10:03 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi All, The Apache Mesos community is ready to graduate. They have added committers and PPMC members while in the Incubator; have made a few releases; are discussing their issues on list and in the Apache way, and are inclusive and representative of Apache's goals as a Foundation. I'm extremely happy to put them up for Incubator graduation. We've VOTEd as a community to move forward with this: DISCUSS thread here: http://s.apache.org/XAu VOTE thread here: http://s.apache.org/K8C VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov Project Incubator status page here: http://incubator.apache.org/projects/mesos.html Board resolution pasted at bottom of email. Existing tallies from the community VOTE: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik * - indicates IPMC Please VOTE to graduate Apache Mesos from the Incubator. Though only Incubator PMC member VOTEs are binding, all are welcome to voice your opinion. I'll leave the VOTE open for at least 72 hours, and hopefully can get enough VOTEs in time to close it by Saturday or Sunday in time for the board meeting on 6/19. [ ] +1 Graduate Apache Mesos from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Mesos from the Incubator because.. Thanks everyone! Cheers, Chris ---board resolution WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to efficient cluster management, resource isolation and sharing across distributed applications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Mesos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mesos Project be and hereby is responsible for the creation and maintenance of software related to efficient cluster management, resource isolation and sharing across distributed applications; and be it further RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mesos 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 Mesos Project: * Ali Ghodsi a...@apache.org * Andy Konwinski and...@apache.org * Benjamin Hindhman b...@apache.org * Benjamin Mahler bmah...@apache.org * Brian McCalister bri...@apache.org * Ian Holsman i...@apache.org * Matei Alexandru Zahari ma...@apache.org * Chris Mattmann mattm...@apache.org * Tom White tomwh...@apache.org * Vinod Kone vinodk...@apache.org * Brenden Matthews bren...@apache.org * Thomas Marshall tmarsh...@apache.org * Charles Reiss wog...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be appointed to the office of Vice President, Apache Mesos, 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 Apache Mesos Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Mesos podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Mesos podling encumbered upon the Apache Incubator Project are hereafter discharged. ++ 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
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 10:56, Noah Slater nsla...@apache.org wrote: Ross, thanks for bringing this up! I'm happy to be a part of this experiment. On 13 June 2013 09:13, Ross Gardler rgard...@opendirective.com wrote: Better yes - required before we can vote - no. My reasoning is that WSO2 have already agreed they will use a different name if VP Branding requires it. In fact they won't have any choice since the proposal clearly indicates the Stratos trademark will be assigned to the ASF. While owning the Stratos trademark would certainly put us in a position of being able to ask WSO2 to stop using StratosLive. But there's no guarantee that we would be successful. That's true, but there is no change in that risk even if we give WSO2 an answer before the vote. What is more important (in my non-legal opinion) is a publicly archived statement from the WSO2 CEO stating they have no intention of abusing the Stratos mark that will be donated to the ASF. We already have that. It's only about the required order, not about the end game. Note, it is normal practice for pre-existing marks to be formally donated to the ASF during incubation, usually just before graduation. The former owner does not (usually) want to assign a mark that may become useless if the project does not graduate. Such graduation is not wholly under the control of the trademark owner. 1. You need to be mindful of third-parties using your trademark in a compound name. This is already encoded in the ASF trademarks policies - WSO2 have agreed to conform to those policies. 2. You need to apply branding rules consistently. WSO2 have agreed to do so. Sanjiva - perhaps you can edit the proposal to this effect in order to help allay any fears. That is to include the statement you made earlier: if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. I don't want to hold up the vote for entry into the incubator on this issue. At the same time I don't want VP Branding to be in a position of having to come to a quick decision. We will have plenty of time during incubation to resolve everything to our satisfaction. Ultimately VP Branding will be able to object to graduation if the issue has not been adequately addressed during incubation. We allowed Couchbase (and others) to share our brand because they were seen as friendly to the community. This is the root of why CouchDB has a problem today. I believe you a projecting that problem and its cause onto a different issue here. This is not about allowing WSO2 an exception to the existing policy. It is about giving WSO2, the Stratos project community (which includes you) and VP Branding time to work on a satisfactory solution *during* incubation rather than prior to a vote. In my opinion WSO2 have demonstrated they are willing to play by the rules. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Thu, Jun 13, 2013 at 3:26 PM, Noah Slater nsla...@apache.org wrote: Ross, thanks for bringing this up! I'm happy to be a part of this experiment. Cool. While owning the Stratos trademark would certainly put us in a position of being able to ask WSO2 to stop using StratosLive. But there's no guarantee that we would be successful. Case in point: Apache CouchDB and As long as I'm running WSO2 that would be successful. However my job is not tenured :-). I learnt two lessons from the Couchbase fiasco: Thanks for your well-reasoned explanation. We will go ahead and change StratosLive as well .. it will take a bit of time but we will do it. (BTW the current StratosLive is not Stratos 2.0 (what we're donating) based.) Hmm that idea was based on how Cloudera is distributing Hadoop: http://www.cloudera.com/content/cloudera/en/products/cdh.html Is that also incorrect then? IIRC they've been doing that for years and presumably ASF is aware of it? The ASF is aware of it, but I don't think we're happy with it. Shane will have more thoughts on this. I understand that but, using your own metric (would there be consumer confusion between Apache Stratos and WSO2 XXX), I would argue that there will be no consumer confusion as to whether what they're downloading is an Apache product or a WSO2 one. Anyway, we are not going to play games with ASF brands; that's not the way WSO2 does stuff. Lets see what Shane says as well. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
I'm just happy to have PaaS as a part of Apache. Thanks to all who are doing this. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jun 13, 2013 at 2:21 PM, Ross Gardler rgard...@opendirective.com wrote: On 13 June 2013 10:56, Noah Slater nsla...@apache.org wrote: Ross, thanks for bringing this up! I'm happy to be a part of this experiment. On 13 June 2013 09:13, Ross Gardler rgard...@opendirective.com wrote: Better yes - required before we can vote - no. My reasoning is that WSO2 have already agreed they will use a different name if VP Branding requires it. In fact they won't have any choice since the proposal clearly indicates the Stratos trademark will be assigned to the ASF. While owning the Stratos trademark would certainly put us in a position of being able to ask WSO2 to stop using StratosLive. But there's no guarantee that we would be successful. That's true, but there is no change in that risk even if we give WSO2 an answer before the vote. What is more important (in my non-legal opinion) is a publicly archived statement from the WSO2 CEO stating they have no intention of abusing the Stratos mark that will be donated to the ASF. We already have that. It's only about the required order, not about the end game. Note, it is normal practice for pre-existing marks to be formally donated to the ASF during incubation, usually just before graduation. The former owner does not (usually) want to assign a mark that may become useless if the project does not graduate. Such graduation is not wholly under the control of the trademark owner. 1. You need to be mindful of third-parties using your trademark in a compound name. This is already encoded in the ASF trademarks policies - WSO2 have agreed to conform to those policies. 2. You need to apply branding rules consistently. WSO2 have agreed to do so. Sanjiva - perhaps you can edit the proposal to this effect in order to help allay any fears. That is to include the statement you made earlier: if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. I don't want to hold up the vote for entry into the incubator on this issue. At the same time I don't want VP Branding to be in a position of having to come to a quick decision. We will have plenty of time during incubation to resolve everything to our satisfaction. Ultimately VP Branding will be able to object to graduation if the issue has not been adequately addressed during incubation. We allowed Couchbase (and others) to share our brand because they were seen as friendly to the community. This is the root of why CouchDB has a problem today. I believe you a projecting that problem and its cause onto a different issue here. This is not about allowing WSO2 an exception to the existing policy. It is about giving WSO2, the Stratos project community (which includes you) and VP Branding time to work on a satisfactory solution *during* incubation rather than prior to a vote. In my opinion WSO2 have demonstrated they are willing to play by the rules. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Thu, Jun 13, 2013 at 3:51 PM, Ross Gardler rgard...@opendirective.comwrote: 2. You need to apply branding rules consistently. WSO2 have agreed to do so. Sanjiva - perhaps you can edit the proposal to this effect in order to help allay any fears. That is to include the statement you made earlier: if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. Will do - I will go further and state that by the time the project graduates we will deprecate WSO2 StratosLive. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 11:26, Sanjiva Weerawarana sanj...@wso2.com wrote: On Thu, Jun 13, 2013 at 3:51 PM, Ross Gardler rgard...@opendirective.comwrote: 2. You need to apply branding rules consistently. WSO2 have agreed to do so. Sanjiva - perhaps you can edit the proposal to this effect in order to help allay any fears. That is to include the statement you made earlier: if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. Will do - I will go further and state that by the time the project graduates we will deprecate WSO2 StratosLive. :-D This is perfect thank you. Ross Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 11:21, Ross Gardler rgard...@opendirective.com wrote: This is the root of why CouchDB has a problem today. I believe you a projecting that problem and its cause onto a different issue here. This is not about allowing WSO2 an exception to the existing policy. It is about giving WSO2, the Stratos project community (which includes you) and VP Branding time to work on a satisfactory solution *during* incubation rather than prior to a vote. In my opinion WSO2 have demonstrated they are willing to play by the rules. Quite possibly. Once bitten... ;) In any case, we are in agreement. To clarify my intent: I only meant to share my experience so that we're mindful of the territory we're venturing into. I don't think the proposal needs to be delayed. We will have plenty of time to work on these things. Also. Thanks for your follow-up emails, Sanjiva's! That's good news. -- NS
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Jun 12, 2013, at 7:32 PM, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Jun 11, 2013 at 2: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. It is certainly a large group and a thoroughly prepared proposal with a lot of resources behind it. == Known Risks == Stratos has largely been developed by sponsored developers employed at a single organization - WSO2. Seeking a broader community of contributors is a top goal of contributing Stratos to Apache. WSO2 plans to continue to offer services and commercial support packages for Stratos, so there is a financial incentive to broaden Stratos’ appeal. This may provide the misinterpretation that Stratos remains merely a WSO2 technology. However, WSO2’s main business strategy is to build and support higher level PaaS offerings (including the WSO2 middleware stack) on top of a common PaaS framework, as provided by Stratos. This includes a WSO2 StratosLive option which is a public PaaS based on WSO2 Stratos. Kudos for the honest self-analysis. I wonder whether Apache Brand Management would cry foul on a trademark like StratosLive if such a product were to appear later because of the confusingly similar name guideline. We've seen project founders leave and compete with ASF products while using confusingly similar names before, e.g. CouchBase. I agree. I would assume that Stratos would become a trademark of the ASF and, as such, WSO2's use of StratosLive as a product name would not be allowed. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
(Please note that this conversation is happening on general@, a publicly archived list, so there is a limit to what level of details of brand strategy I will engage in on this thread.) To be brief: - This issue should not gate a [VOTE] to begin incubation. - Given both WSO2's history and the many Apache members involved in the project, I'm confident the right thing will end up happening. - The requirement is that the branding for a podling must be formally donated to the ASF before it can graduate. We are happy to sign agreements earlier or later; if we sign earlier we're happy to include language such that any trademark assignment will revert to the original owner if graduation fails for some reason. - Unofficially (meaning: I've only spent 5 minutes reading this all so far) I do *not* believe it would be tenable to have a future Apache Stratos and a future WSO2 StratosLive. Many thanks in advance to Sanjiva and company for being willing to change this! - Shane On 6/13/2013 6:21 AM, Ross Gardler wrote: On 13 June 2013 10:56, Noah Slater nsla...@apache.org wrote: Ross, thanks for bringing this up! I'm happy to be a part of this experiment. On 13 June 2013 09:13, Ross Gardler rgard...@opendirective.com wrote: Better yes - required before we can vote - no. My reasoning is that WSO2 have already agreed they will use a different name if VP Branding requires it. In fact they won't have any choice since the proposal clearly indicates the Stratos trademark will be assigned to the ASF. While owning the Stratos trademark would certainly put us in a position of being able to ask WSO2 to stop using StratosLive. But there's no guarantee that we would be successful. That's true, but there is no change in that risk even if we give WSO2 an answer before the vote. What is more important (in my non-legal opinion) is a publicly archived statement from the WSO2 CEO stating they have no intention of abusing the Stratos mark that will be donated to the ASF. We already have that. It's only about the required order, not about the end game. Note, it is normal practice for pre-existing marks to be formally donated to the ASF during incubation, usually just before graduation. The former owner does not (usually) want to assign a mark that may become useless if the project does not graduate. Such graduation is not wholly under the control of the trademark owner. 1. You need to be mindful of third-parties using your trademark in a compound name. This is already encoded in the ASF trademarks policies - WSO2 have agreed to conform to those policies. 2. You need to apply branding rules consistently. WSO2 have agreed to do so. Sanjiva - perhaps you can edit the proposal to this effect in order to help allay any fears. That is to include the statement you made earlier: if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. I don't want to hold up the vote for entry into the incubator on this issue. At the same time I don't want VP Branding to be in a position of having to come to a quick decision. We will have plenty of time during incubation to resolve everything to our satisfaction. Ultimately VP Branding will be able to object to graduation if the issue has not been adequately addressed during incubation. We allowed Couchbase (and others) to share our brand because they were seen as friendly to the community. This is the root of why CouchDB has a problem today. I believe you a projecting that problem and its cause onto a different issue here. This is not about allowing WSO2 an exception to the existing policy. It is about giving WSO2, the Stratos project community (which includes you) and VP Branding time to work on a satisfactory solution *during* incubation rather than prior to a vote. In my opinion WSO2 have demonstrated they are willing to play by the rules. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Jun 13, 2013, at 1:10 AM, Ross Gardler rgard...@opendirective.com wrote: On 13 June 2013 04:56, Alan Cabrera l...@toolazydogs.com wrote: On Jun 12, 2013, at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote: So here's a thought... ... I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. ... So, what do you think? I don't see the need to force Stratos through the Incubator given the current proposed membership. Some points: Who's responsible for monitoring the probation, the IPMC or the board? I think it should be the IPMC. I think we should come up with a concrete plan then go to the board. If the board is OK with taking it on then it should be board as this will be closer to Chris' defined end goal. In either case I undertake, as I noted in my original mail, to be the one that steps up to fix things if it all goes wrong. That's true whether it is IPMC or Board. I guess the details of how this governance will work, what are the roles, and who will fill them, will need to be ironed out. What bits must absolutely be done before probation begins? That needs to be defined. Given the fact the next board meeting is only a week away I suggest we first make this a podling to allow us to start the project here at the ASF. We can then work with the various committees to work out what the right set-up process is (i.e. don't set up as a podling, set up as a pTLP). We can then shoot for submitting a board resolution next month. I have already made it clear to the proposers of the project that taking this route will result in a slightly longer set-up period (because of the need to define new policies along the way). They are comfortable trading slower set-up for potentially faster graduation. It would probably be good to be clear on what are the exact characteristics that make this podling pTLP worthy for the future. For example, the number of ASF veterans in its ranks. What minimum criteria does a probationary TLP have to meet to stay in good graces? Exactly the same as any other TLP. What happens if the probationary TLP is not in good graces? Exactly the same as any other TLP. The board says fix it. If it isn't fixed the board kicks out the problem element(s) and invites remaining PMC to fix it. If that failes the pTLP is sent packing. What bits must absolutely be done before probation completes? Same as graduation from the Incubator (a release, demonstration of a healthy community, approval of the board) Nice and simple. Fleshing out these and, I'm sure, others' concerns on a wiki, as Joe pointed out, would be a great idea. Yes, but please note my proposal to do this as a standard podling rather than in this discussion phase. I don't think we need everything in a row before the team can get to work. If it should prove impossible to find a sensible process then we can simply leave the project as a standard podling. Makes sense. So to recap the proposed timeline: - IPMC votes on accepting the podling with the intention of moving it to a pTLP - mentors (with Chris' assistance) guide project committers in working with the various committees to define incubation/probation process - submit a board resolution in July to create the pTLP - if project is not ready to do so this can be delayed until August - If the board are unhappy with the project then I am called in to clear up the mess I made - If the board are happy with progress submit a resolution to become a TLP in 12 months (target 6 months) +1 Though I wouldn't put a date on TLP; keep things simple. We don't for podlings and since the pTLP will be filled with trustworthy ASF members we can trust they will do the right thing. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 13 June 2013 14:12, Alan Cabrera l...@toolazydogs.com wrote: On Jun 13, 2013, at 1:10 AM, Ross Gardler rgard...@opendirective.com wrote: On 13 June 2013 04:56, Alan Cabrera l...@toolazydogs.com wrote: On Jun 12, 2013, at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote: So here's a thought... ... I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. ... So, what do you think? I don't see the need to force Stratos through the Incubator given the current proposed membership. Some points: Who's responsible for monitoring the probation, the IPMC or the board? I think it should be the IPMC. I think we should come up with a concrete plan then go to the board. If the board is OK with taking it on then it should be board as this will be closer to Chris' defined end goal. In either case I undertake, as I noted in my original mail, to be the one that steps up to fix things if it all goes wrong. That's true whether it is IPMC or Board. I guess the details of how this governance will work, what are the roles, and who will fill them, will need to be ironed out. Yes. Of course in this case I'm proposing a period as a podling to give us time to iron those details out. However, here's my starting suggestion: This is just a TLP so we need to identify is committers, PMC, PMC chair. My starting suggestion is: - commiters (see proposal) - PMC members (I suggest initial membership is the mentors, the mentors seek to vote initial committers into the PMC as quickly as possible) - PMC chair (I would suggest the chair is the Champion until the PMC is confident enough to elect one from their own ranks - should be done ASAP, but certainly before graduation) What bits must absolutely be done before probation begins? That needs to be defined. Given the fact the next board meeting is only a week away I suggest we first make this a podling to allow us to start the project here at the ASF. We can then work with the various committees to work out what the right set-up process is (i.e. don't set up as a podling, set up as a pTLP). We can then shoot for submitting a board resolution next month. I have already made it clear to the proposers of the project that taking this route will result in a slightly longer set-up period (because of the need to define new policies along the way). They are comfortable trading slower set-up for potentially faster graduation. It would probably be good to be clear on what are the exact characteristics that make this podling pTLP worthy for the future. For example, the number of ASF veterans in its ranks. The board expects a TLP to be able to make releases. That requires 3 +1 votes. That implies 3 initial PMC members. According to my starting proposal above this means 3 mentors minimum. This in turn matches what has come to be common practice in the IPMC. So to recap the proposed timeline: - IPMC votes on accepting the podling with the intention of moving it to a pTLP - mentors (with Chris' assistance) guide project committers in working with the various committees to define incubation/probation process - submit a board resolution in July to create the pTLP - if project is not ready to do so this can be delayed until August - If the board are unhappy with the project then I am called in to clear up the mess I made - If the board are happy with progress submit a resolution to become a TLP in 12 months (target 6 months) +1 Though I wouldn't put a date on TLP; keep things simple. We don't for podlings and since the pTLP will be filled with trustworthy ASF members we can trust they will do the right thing. Yes, I did wonder about that when I was writing this. I kept adding and removing it. I would like a date in there as targets are always something to aim for. The fact we don't have such a target for podlings is one of the items that some people suggest needs fixing. That said, the board is sensible enough to give a pTLP longer than the target if it is clear things are moving in the right direction. I would suggest we keep the date but make sure it is only a guideline. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Thu, Jun 13, 2013 at 05:39:24AM +0530, Sanjiva Weerawarana wrote: On Thu, Jun 13, 2013 at 5:02 AM, Marvin Humphrey mar...@rectangular.comwrote: == Known Risks == Stratos has largely been developed by sponsored developers employed at a single organization - WSO2. Seeking a broader community of contributors is a top goal of contributing Stratos to Apache. WSO2 plans to continue to offer services and commercial support packages for Stratos, so there is a financial incentive to broaden Stratos’ appeal. This may provide the misinterpretation that Stratos remains merely a WSO2 technology. However, WSO2’s main business strategy is to build and support higher level PaaS offerings (including the WSO2 middleware stack) on top of a common PaaS framework, as provided by Stratos. This includes a WSO2 StratosLive option which is a public PaaS based on WSO2 Stratos. Kudos for the honest self-analysis. Thanks :-). I wonder whether Apache Brand Management would cry foul on a trademark like StratosLive if such a product were to appear later because of the confusingly similar name guideline. We've seen project founders leave and compete with ASF products while using confusingly similar names before, e.g. CouchBase. Yeah we also thought about that .. if StratosLive is too close to home we can certainly change it. Bit painful but not impossible. Alternatively, if WS02 wanted to keep using the Stratos term, the podling (to be) could re-brand the project itself to something other than Stratos. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Thu, Jun 13, 2013, at 08:58 AM, Chip Childers wrote: Alternatively, if WS02 wanted to keep using the Stratos term, the podling (to be) could re-brand the project itself to something other than Stratos. I think this would be a better way to go, honestly. If there was one thing I could do over again about CloudStack, it would have been to have let Citrix keep the name for their commercial offering and choose a different name for the Apache project. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCEL] [VOTE] Accept Apache HotdoG into the Incubator
All, First of all, big thanks to everyone for their support of this proposal but at this time it is best to put this on hold. The HDF Group, who were envisioned to provide the initial code drop and some of the primary developers, have existing efforts they would first like to get aligned before creating another thrust. Additionally, there are some collaborators with HDF Group that we would like to be involved so that we can create synergy for them and Apache. Although the vote would have passed, I feel its not the right time to spin this up and use Apache resources unnecessarily. We will be meeting with the HDF Group and their collaborators over the summer and look to see if there is a viable path forward and how best we can proceed together. Once again, thanks for everyone's interest and we look forward to making this happen. Thanks, Paul Ramirez
Change of Chair
Incubator community, 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. --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
72 hours has passed and we have the following +1's: Binding (2 more needed): Alex Karasulu Non-Binding: Vinod Kone Deepal jayasinghe Brenden Matthews Yan Xu Could some IPMC members please take a look? It would be greatly appreciated! Ben On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Will do tonight, Ben :) ++ 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 13, 2013 5:56 PM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) 72 hours has passed and we have the following +1's: Binding (2 more needed): Alex Karasulu Non-Binding: Vinod Kone Deepal jayasinghe Brenden Matthews Yan Xu Could some IPMC members please take a look? It would be greatly appreciated! Ben On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12. 0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d 7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12. 0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12. 0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Change of Chair
On Jun 13, 2013, at 2:03 PM, Benson Margulies bimargul...@gmail.com wrote: Incubator community, 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. Thanks, Benson, for all your hard work! Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Change of Chair
Benson, Thanks for your excellent service. Marvin, All the best for you in your new role. Regards, Craig On Jun 13, 2013, at 2:03 PM, Benson Margulies wrote: Incubator community, 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. --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On Wed, Jun 12, 2013 at 7:12 PM, Ross Gardler rgard...@opendirective.com wrote: I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. If the Stratos folks are amenable, +1. It's an incremental, reversible step forward. With so many experienced Members and Mentors involved, Stratos is assured of getting everything they would get out of an ordinary incubation and more, even if there are some bumps. And I hope there will be a payoff for Stratos by sidestepping what is IMO the Incubator's flawed approach to meritocracy[1], where true responsibility arrives all at once on graduation. On general@, we'll probably get the usual storms of email. But we would have gotten those anyway, and at least we'll be talking about real data rather than hypotheticals. Marvin Humphrey [1] http://s.apache.org/nzm - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Hi Ben, +1 from me (binding) SIGS pass (minor nit: your GPG key should probably be made available at id.apache.org, which will in turn make it available here http://people.apache.org/keys/group/mesos.asc) I was able to import Ben's key: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% gpg --keyserver pgpkeys.mit.edu --recv-key D141A5B6 gpg: requesting key D141A5B6 from hkp server pgpkeys.mit.edu gpg: key D141A5B6: public key Benjamin Mahler benjamin.mah...@gmail.com imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Good signature from Benjamin Mahler benjamin.mah...@gmail.com gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E3A6 E5EF 7B67 C142 5B53 F072 D0BE BB95 D141 A5B6 [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% CHECKSUMS pass: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.12.0-incubating.tar.gz: OK [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% BUILD OK: [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% ./configure --disable-java checking build system type... x86_64-apple-darwin12.4.0 checking host system type... x86_64-apple-darwin12.4.0 checking target system type... x86_64-apple-darwin12.4.0 ..long time byte-compiling build/bdist.macosx-10.8-intel/egg/_mesos.py to _mesos.pyc creating build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/PKG-INFO - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/SOURCES.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/dependency_links.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/requires.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO writing build/bdist.macosx-10.8-intel/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.12.0-py2.7-macosx-10.8-intel.egg' and adding 'build/bdist.macosx-10.8-intel/egg' to it removing 'build/bdist.macosx-10.8-intel/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, June 10, 2013 5:05 PM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0 -incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7 b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0 -incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0 -incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
+1 for the probationary TLP idea. Azeez On Thu, Jun 13, 2013 at 7:42 AM, Ross Gardler rgard...@opendirective.comwrote: So here's a thought... There have been many discussions about different ways to incubate projects. One of the most radical ideas is to dismantle the incubator and replace the podling concept with probationary TLPs reporting to the board. As readers of this list will know I do not support the idea of dismantling the IPMC. I believe it does a great job that is not easily replaced by a board of nine directors. However, I have always acknowledged that the idea has merit under a certain set of circumstances. For me those circumstances are present in the Apache Stratos proposal. That is there are sufficient mentors and initial committers who are ASF Members that we can be reasonably certain that this project will succeed here at the ASF. I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. For my part my intention is to get the project set-up and then dissolve into the background. I do not intend to monitor the project on a day-to-day basis. However, I do promise to help pick up the pieces if the experiment should go horribly wrong. Of course running a single experiment will only allow us to define the incubation process for probationary TLPs, It is not going to solve all the problems Chris sees in the IPMC. However it will give us an opportunity to define the process, ask the board to approve this process and thus lay the foundations for other projects wishing to follow this path. So, what do you think? Ross On 11 June 2013 10:10, 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
