Re: [VOTE] Zipkin leave incubator, return back to OpenZipkin
[+1] Agree And best of luck in the future. On Tue, Jun 18, 2019 at 3:22 AM Sheng Wu wrote: > Hi > > This is a call for official vote of Zipkin leave from incubator, and > return back to OpenZipkin. > > PPMC have voted.[1], carried two IPMC +1 vote from Sheng Wu and Willem > Jiang > > There is no trademark, logo transfer, so, Zipkin community is OK to still > use the name(io.zipkin or zipkin + xxx) and logo. > `org.apache.zipkin` is not allowed or going to be used. > All 9 repositories(GitHub repo) will be transferred back to OpenZipkin > org(GitHub). > incubator-zipkin --> https://github.com/openzipkin/zipkin > ncubator-zipkin-dependencies --> > https://github.com/openzipkin/zipkin-dependencies > incubator-zipkin-api --> https://github.com/openzipkin/zipkin-api > incubator-zipkin-b3-propagation --> > https://github.com/openzipkin/b3-propagation > incubator-zipkin-reporter-java --> > https://github.com/openzipkin/zipkin-reporter-java > incubator-zipkin-brave --> https://github.com/openzipkin/brave > incubator-zipkin-brave-cassandra --> > https://github.com/openzipkin/brave-cassandra > incubator-zipkin-brave-karaf --> https://github.com/openzipkin/brave-karaf > incubator-zipkin-layout-factory --> > https://github.com/openzipkin/zipkin-layout-factory > > Voting will start now (2019-6-18 9:20 UTC+8) and will remain open 72 hours > only for consensus, Request all IPMC members to give their vote. > [ ] +1 Agree > [ ] +0 No opinion. > [ ] -1 Do not agree because > > [1] > https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E > < > https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E > > > > > > Sheng Wu > Apache Skywalking, ShardingSphere, Zipkin > > > >
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
It's great to see many cool and exciting new projects joining Apache Incubator. +1 from my side On Fri, Sep 20, 2013 at 3:54 PM, Sanjiva Weerawarana sanj...@wso2.comwrote: +1 - there's a lot of overlap / commonality of objective between BaaS and the set of services provided by Apache Stratos (incubating) to developers of apps. I'm very happy to see this come to ASF and will be happy to mentor if you guys need another one. Cheers, Sanjiva. On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent
Re: [VOTE]: Graduate Apache jclouds as an Apache Top Level Project
This is slightly off topic and it will also be non-relevant if the graduation vote passes, but since you've mentioned branding conformance in your email. I've noticed that there is an incubator logo, but the website is missing a standard incubator disclaimer ( http://incubator.apache.org/guides/branding.html#disclaimers).
Re: [VOTE] Accept Storm into the Incubator
+1 (binding) On Thu, Sep 12, 2013 at 9:19 PM, Doug Cutting cutt...@apache.org wrote: Discussion about the Storm proposal has subsided, issues raised now seemingly resolved. I'd like to call a vote to accept Storm as a new Incubator podling. The proposal is included below and is also at: https://wiki.apache.org/incubator/StormProposal Let's keep the vote open for four working days, until 18 September. [ ] +1 Accept Storm into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Storm because... Doug = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm’s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com, which will seed the Apache git repository. === 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 need for a low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as Zookeeper, Thrift, Mesos). We could include additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near future. == Known Risks == === Orphaned Products === The risk of the Storm project being abandoned is minimal. There are at least 50 organizations (Twitter, Yahoo!, Microsoft, Groupon, Baidu, Alibaba, Alipay, Taobao, PARC, RocketFuel etc) are
Re: [PROPOSAL] Storm for Apache Incubator
Agreed. I think Storm would be a great addition to ASF. On Wed, Sep 4, 2013 at 10:12 AM, Debo Dutta (dedutta) dedu...@cisco.comwrote: +1 This would be great. On 9/4/13 1:07 AM, Nathan Marz nat...@nathanmarz.com wrote: Hi everyone, I'd like to propose Storm to be an Apache Incubator project. After much thought I believe this is the right next step for the project, and I look forward to hearing everyone's thoughts and feedback! Here's a link to the proposal: https://wiki.apache.org/incubator/StormProposal The proposal is also pasted below. -Nathan = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm¹s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com, which will seed the Apache git repository. === 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 need for a low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as Zookeeper, Thrift, Mesos). We could include additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near future. == Known Risks == === Orphaned Products === The risk of the Storm project being abandoned is minimal. There are at least 50 organizations (Twitter, Yahoo!,
Re: [VOTE] Accept jclouds into the Apache Incubator
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 Software Foundation * Olivier Lamy, Apache Software Foundation * Tomaz Muraus, Apache Software Foundation * Suresh Marru, Apache Software Foundation * Carlos Sanchez, Apache Software Foundation === Sponsoring Entity === The jclouds contributors and community request sponsorship from the Incubator.
Re: [PROPOSAL] jclouds Proposal for Incubator
Agreed and best of luck from the Apache Libcloud PMC :) If you are looking for additional mentors I'm also more than happy to help. (I would add myself under volunteer section on the wiki, but it looks like I don't have the necessary permissions). On Tue, Apr 16, 2013 at 12:19 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. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Reports Due -- and missing
Sorry for the delay. I have just added a Libcloud report. Will also ping our mentors to check sign it off. On Mon, May 16, 2011 at 9:56 PM, Noel J. Bergman n...@devtech.com wrote: I will be doing it tonight for Thursday's meeting. Missing: Bluesky, Celix, Delta Cloud, HCatalog, HISE, LibCloud (up for a TLP vote, but we still need a report), and SIS. --- Noel
Re: [Proposal]: Libcloud to become a TLP
Yes, sorry I wanted to follow the documentation so I have posted a proposal first. But everyone is OK with it, lets call this a vote thread. Thanks! Tomaz On Sun, May 15, 2011 at 7:53 PM, Mark Struberg strub...@yahoo.de wrote: hmmm [VOTE] or not? anyway +1 (binding) LieGrue, strub --- On Sun, 5/15/11, Alan D. Cabrera l...@toolazydogs.com wrote: From: Alan D. Cabrera l...@toolazydogs.com Subject: Re: [Proposal]: Libcloud to become a TLP To: general@incubator.apache.org Date: Sunday, May 15, 2011, 4:15 PM +1 since this seems to be a vote and not a proposal. Regards, Alan On May 14, 2011, at 9:35 AM, Tomaz Muraus wrote: Hello all, Apache Libcloud developers and community thinks we are ready to graduate and become a top level project. Libcloud (http://incubator.apache.org/libcloud/) has entered the incubator in late 2009 and so far we have had multiple releases. The last version (0.4.2) was released in January. We are currently working towards 0.5.0 which is planned to be released in the upcoming week. This release is considered as a big one since it will include multiple new features (storage load balancer API), new provider drivers and a lot of improvements. We have also built a healthy and a diverse community around our project. So far we have received (and continue to receive) multiple contributions from them. Community voting has passed with ten (10) +1's, zero (0) 0's and zero (0) -1's. Thread with the results can be found at http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Our status file can be found at http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/libcloud.xmland the resolution is included bellow. http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Thanks, Tomaz Establish the Apache Libcloud 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 abstracting differences between cloud providers 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 Libcloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is responsible for the creation and maintenance of software related to software providing a standard interface to the cloud provider APIs; and be it further RESOLVED, that the office of Vice President, Apache Libcloud 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 Libcloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Libcloud 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 Libcloud Project: * Eric Woods (wood...@apache.org) * Jed Smith (j...@apache.org) * Jeremiah Orem(or...@apache.org) * Jerry Chen (je...@apache.org) * Roman Bogorodskiy (rbogorods...@apache.org) * Tom Davis (t...@apache.org) * Tomaz Muraus (to...@apache.org) * Paul Querna (pque...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tomaz Muraus be appointed to the office of Vice President, Apache Libcloud, 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 Libcloud 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 Libcloud Project; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Libcloud podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Libcloud 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 - To unsubscribe, e-mail
[Vote]: Libcloud to become a TLP
OK, sorry for the confusion, but apparently I need to open a separate voting thread so here it is. Here is also a list of people who have already voted +1 in the proposal thread which can be found at http://mail-archives.apache.org/mod_mbox/incubator-general/201105.mbox/%3cbanlktikhycoedn3r9o41ohmgj1hs41d...@mail.gmail.com%3E : - Paul Querna - Chris Mattmann - Joe Schaefer (binding) - Davanum Srinivas (binding) - Mohammad Nour El-Din - Alan D. Cabrera - Tommaso Teofili (binding) - Mark Struberg (binding) - Luciano Resende (binding) Hello all, Apache Libcloud developers and community thinks we are ready to graduate and become a top level project. Libcloud (http://incubator.apache.org/libcloud/) has entered the incubator in late 2009 and so far we have had multiple releases. The last version (0.4.2) was released in January. We are currently working towards 0.5.0 which is planned to be released in the upcoming week. This release is considered as a big one since it will include multiple new features (storage load balancer API), new provider drivers and a lot of improvements. We have also built a healthy and a diverse community around our project. So far we have received (and continue to receive) multiple contributions from them. Community voting has passed with ten (10) +1's, zero (0) 0's and zero (0) -1's. Thread with the results can be found at http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Our status file can be found at http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/libcloud.xmland the resolution is included bellow. http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Thanks, Tomaz Establish the Apache Libcloud 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 abstracting differences between cloud providers 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 Libcloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is responsible for the creation and maintenance of software related to software providing a standard interface to the cloud provider APIs; and be it further RESOLVED, that the office of Vice President, Apache Libcloud 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 Libcloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Libcloud 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 Libcloud Project: * Eric Woods (wood...@apache.org) * Jed Smith (j...@apache.org) * Jeremiah Orem(or...@apache.org) * Jerry Chen (je...@apache.org) * Roman Bogorodskiy (rbogorods...@apache.org) * Tom Davis (t...@apache.org) * Tomaz Muraus (to...@apache.org) * Paul Querna (pque...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tomaz Muraus be appointed to the office of Vice President, Apache Libcloud, 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 Libcloud 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 Libcloud Project; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Libcloud podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Libcloud podling encumbered upon the Apache Incubator Project are hereafter discharged.
[Proposal]: Libcloud to become a TLP
Hello all, Apache Libcloud developers and community thinks we are ready to graduate and become a top level project. Libcloud (http://incubator.apache.org/libcloud/) has entered the incubator in late 2009 and so far we have had multiple releases. The last version (0.4.2) was released in January. We are currently working towards 0.5.0 which is planned to be released in the upcoming week. This release is considered as a big one since it will include multiple new features (storage load balancer API), new provider drivers and a lot of improvements. We have also built a healthy and a diverse community around our project. So far we have received (and continue to receive) multiple contributions from them. Community voting has passed with ten (10) +1's, zero (0) 0's and zero (0) -1's. Thread with the results can be found at http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Our status file can be found at http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/libcloud.xmland the resolution is included bellow. http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser Thanks, Tomaz Establish the Apache Libcloud 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 abstracting differences between cloud providers 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 Libcloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is responsible for the creation and maintenance of software related to software providing a standard interface to the cloud provider APIs; and be it further RESOLVED, that the office of Vice President, Apache Libcloud 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 Libcloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Libcloud 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 Libcloud Project: * Eric Woods (wood...@apache.org) * Jed Smith (j...@apache.org) * Jeremiah Orem(or...@apache.org) * Jerry Chen (je...@apache.org) * Roman Bogorodskiy (rbogorods...@apache.org) * Tom Davis (t...@apache.org) * Tomaz Muraus (to...@apache.org) * Paul Querna (pque...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tomaz Muraus be appointed to the office of Vice President, Apache Libcloud, 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 Libcloud 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 Libcloud Project; and be it further RESOLVED, that the Apache Libcloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Libcloud podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Libcloud podling encumbered upon the Apache Incubator Project are hereafter discharged.
