This page tracks the project status, incubator-wise. For more general project status, look on the project website.
The CloudStack project graduated on 2013-03-20
This page tracks the project status, incubator-wise. For more general project status, look on the project website.
The CloudStack project graduated on 2013-03-20
CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration platform.
If the project website and code repository are not yet setup, use the following table:
item | type | reference |
---|---|---|
Website | www | http://incubator.apache.org/cloudstack |
. | wiki | https://cwiki.apache.org/confluence/display/CLOUDSTACK/Index |
Mailing list | dev | cloudstack-dev @ incubator.apache.org |
. | commits | cloudstack-commits @ incubator.apache.org |
. | users | cloudstack-users @ incubator.apache.org |
. | issues | cloudstack-issues @ incubator.apache.org |
. | marketing | cloudstack-marketing @ incubator.apache.org |
Bug tracking | . | https://issues.apache.org/jira/browse/CLOUDSTACK |
Source code | Git | https://gitbox.apache.org/repos/asf/incubator-cloudstack.git |
. | SVN (project site and PPMC admin docs only) | https://svn.apache.org/repos/asf/incubator/cloudstack/ |
Mentors | jim | Jim Jagielski |
. | dkulp | J. Daniel Kulp |
. | akarasulu | Alex Karasulu |
. | olamy | Olivier Lamy |
. | brett | Brett Porter |
. | hogstrom | Matt Richard Hogstrom |
. | mnour | Mohammad Nour El-Din |
. | nslater | Noah Slater (2012-08-07) |
Podling PMC | willchan | Will Chan |
. | widodh | Wido den Hollander (2012-08-07) |
. | kluge | Kevin Kluge |
. | ke4qqq | David Nalley |
. | chipchilders | Chip Childers (2012-08-14) |
. | jlk | John Kinsella (2012-07-11) |
. | edison | Edison Su |
. | ahuang | Alex Huang |
. | hugo | Hugo Trippaers (2012-07-11) |
. | chiradeep | Chiradeep Vittal |
. | jzb | Joe Brockmeier (2012-08-23) |
. | mlsorensen | Marcus Sorensen (2012-10-10) |
. | sebgoa | Sebastien Goasguen (2013-01-03) |
Committers | aprateek | Abhinandan Prateek |
. | alena1108 | Alena Prokharchyk |
. | anthonyxu | Anthony Xu |
. | bfederle | Brian Federle |
. | frankzhang | Frank Zhang |
. | gavinlee | Gavin Lee (2012-10-18) |
. | jbausewein | Jason Bausewein (2012-08-06) |
. | jtomechak | Jessica Tomechak |
. | jessicawang | Jessica Wang |
. | jburwell | John Burwell (2013-01-24) |
. | kdamage | Kelcey Damage (2013-01-02) |
. | kelveny | Kelven Yang |
. | kishan | Kishan Kavala |
. | koushik | Koushik Das (2013-01-31) |
. | likithas | Likitha Shetty (2013-02-13) |
. | mchen | Minh Chen (2012-12-11) |
. | mice | Mice Xia (2012-08-06) |
. | muralireddy | Murali Reddy |
. | nitin | Nitin Mehta |
. | noa | Noa Resare (2013-02-27) |
. | olgasmola | Olga Smola (2012-06-19) |
. | prachidamle | Prachi Damle |
. | pranavs | Pranav Saxena (2012-07-11) |
. | tsp | Prasanna Santhanam (2012-07-11) |
. | radhika | Radhika Puthiyetath (2013-02-26) |
. | bhaisaab | Rohit Yadav (2012-10-05) |
. | slriv | Sam Robertson |
. | sateesh | Sateesh Chodapuneedi (2013-02-26) |
. | yasker | Sheng Yang |
. | schhen | Sonny Chhen |
. | sudhap | Sudha Ponnaganti (2012-11-12) |
Extra | . | . |
CloudStack
CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration platform.
CloudStack has been incubating since 2012-04-16.
A list of the three most important issues to address in the move towards graduation
1. Continuing to build the community and increase diversity, while effectively managing the overall scale of the project.
2. Ensuring all deliberation, decision-making, and development is happening openly and collaboratively.
3. Transfer trademark, etc. to Apache
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
The project has continuted to grow and has added several new PPMC members and committers since October:
- Edison Su, Alex Huang, Hugo Trippaers, and Chiradeep Vittal, have joined the PPMC since October.
- Rohit Yadav, Marcus Sorensen, Gavin Lee, Sudha Ponnaganti, Kelcey Damage, and Min Chen have become committers.
Members of the CloudStack community have been active in promoting the project since the last report, with members giving talks about Apache CloudStack at USENIX LISA, CPOSC, ApacheCon EU, LinuxCon EU, and other events.
The CloudStack Collaboration Conference (sponsored primarily by Citrix) was a fairly successful first conference. More than 300 people attended the event, held November 30 - December 2 in Las Vegas at The Venetian.
How has the project developed since the last report?
The first release, 4.0.0-incubating, was announced on November 6th.
The CloudStack.org domain now points to Apache infrastructure.
4.0.1 and 4.1.0 are currently in development. The community has decided to work on a time-based release cycle for feature releases, with 4.1.0 expected at the beginning of April. Feature releases will follow a four-month cycle thereafter.
CloudStack
CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration
platform. CloudStack has been in incubation since 2012-04-16
A list of the three most important issues to address in the move towards
graduation
1. Continuing to build the community and increase diversity
2. Shipping a release
3. Transfer trademark, etc. to Apache
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
The project has continued to improve its diversity, adding
Chip Childers, John Kinsella, and Wido den Hollander to the PPMC
and 3 new committers since the month of August. (Mice Xia, Jason
Bausewein, and Joe Brockmeier.) We have also taken on a new mentor,
Noah Slater.
Contributors and committers have been active in promoting CloudStack
at events, such as LinuxCon, Ohio LinuxFest, PuppetConf, a get-together
at Schuberg Philis, and a number of other events.
The community is participation at LinuxCon EU and ApacheCon EU and
a number of other events through the remainder of 2012.
Citrix is acting as primary sponsor of a CloudStack Collaboration
Conference for November 30 through December 2 in Las Vegas. The
conference is open to the community, and programming for the event
will be chosen by a committee that includes members of the CloudStack
community outside Citrix.
How has the project developed since the last report?
The pending 4.0 release has been branched. The project has made a great
deal of progress towards the 4.0 release, handling a number of technical
issues (such as a move to Maven) and resolving almost all known legal
issues that would pose an obstacle to a release. The sole remaining
blocker is under discussion and should be resolved shortly.
The Jira instance for CloudStack was stood up in early September. License
checks have been automated to ensure that we remain compliant with Apache
guidelines going forward.
Signed-off-by: nslater, mfranklin
CloudStack
A list of the three most important issues to address in the move towards graduation
1. Licensing work
2. Finishing up the move of CloudStack infrastructure resources to the ASF.
3. Shipping a release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
CloudStack has added 6 new committers in the month of July.
We had BOF and hackathon time at OSCON, which was a positive benefit for
those committers who attended, particularly in being able to delve into
issues around incubation, branding, and licensing. Additionally two
committers presented tutorials at OSCON one focused on end users deploying
CloudStack and the other focused on developers hacking on CloudStack, both
had great attendance.
We have also had some offers of contribution from people at Bitergia who are
interested in contributing the work that they have done around metrics. which
was a very encouraging start to growing the community.
How has the project developed since the last report?
Lots of modularization has been injected into CloudStack, which makes some
of our licensing issues far less of a problem as we can merely turn the
affected code off by default.
The wiki has begun migration to an ASF hosted wiki instance.
One of the CloudStack committers provided a dramatically easier way to be
able to test and develop for CloudStack in the form a completely contained
CloudStack environment that can be run as a VirtualBox VM. Much additional
enhancement has been contributed to this making the process easier and
easier to update.
We also saw the movement of documentation from binary .docx files to
DocBook XML; while this effort isn't complete it does permit folks to far
more easily collaborate, as well as providing a far better interface
for l10n.
Signed-off-by: brett, jukka, jim
CloudStack
CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration
platform. CloudStack has been in incubation since 2012-04-16
The top 3 issues to address to move towards graduation:
- CloudStack's source still contains works that are prohibited for release
under ASF guidelines
- Performing a release
- Migration of infrastructure (bug tracker, CI, websites, etc)
How has the community developed since the last report:
As of the time of this report at least one new committer has been added.
Additionally, a number of previously unknown developers have begun making
substantial quantities of bugfixes and even working on new functionality.
How has the project developed since the last report:
The project itself continues to deal with process questions as well as
learning how to operate in the new environment. A good deal of work has
been happening on resolving the problems in the code base around licensing,
though not currently close to finishing.
Signed off by mentor:
CloudStack
CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration
platform. CloudStack has been in incubation since 2012-04-16
CloudStack has been in the incubator for approximately 1.5 months. Mailing
lists have migrated, accounts for the initial committers have been set up,
and the initial code drop/git repo has been setup. Many new names are now
participating in conversations on the mailing lists, with several of them
volunteering to help move things along. The number of submitted patches from
'new names' in the month of May is in the double digits, and range from
trivial one line fixes to two major patches with over 1,000 changed lines
each. The community is beginning to exercise some of its decision making
power by deciding about release tempo, future version schemes and numbers,
and a number of other internal plumbing issues. Much remains to be done in
preparation for the initial release, and those tasks are being identified.
We also have a number of external resources (bug tracker, wiki, CI) that
are still awaiting migration.
Top 3 Issues to address in move towards graduation
- The project is using source and binaries with a number of
non-ASF-approved licenses. This needs remediation.
- Diversity of the contributor base still needs to be expanded.
- While we are making progress, there still remains a number of large
pieces (bug tracker, wiki, test infra) that still need to be migrated
to ASF infrastructure.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues that we are aware of at this point.
How has the community developed since the last report?
See the above narration, but generally speaking the community is beginning
to exercise its decision making powers, largely around internal plumbing
issues at the moment. We are also seeing a number of new developers
submitting patches.
How has the project developed since the last report?
The project continues to have many issues to tackle for its first release
and is identifying and moving forward on those issues. Work continues on
solutions to remove the need to massive (or any) amount of additional
hardware to test/develop with in an effort to lower the barrier to
participate.
Signed off by mentor:
Overview:
Cloudstack just entered the incubator a couple of weeks ago. Since then,
the mailing list has been setup and discussions have started to migrate
from the existing list to the ASF-hosted list, with several 'new names'
participating including one of those 'new names' submitting a patch.
Currently, the code repository and bulk of existing infrastructure is still
hosted by Citrix, but the community is looking forward to getting that
moved to Apache as soon as possible.
A list of the most important issues to address in the move towards graduation:
1. The base level of infrastructure migration has begun but still has far
to be finished. At present the mailing lists exist, but wiki, project
website, source repository, bug tracker, etc still need to be brought
up and migrated. In many ways we are blocked on further progress by
lack of account creation for initial committers.
2. Diversity of the contributor base still needs to be expanded - this was
identified as an issue in the proposal, and remains one, though we are
encouraged by a seeming uptick (we've been in incubation for less than
a week, so trends are indeed difficult to identify at this point) in
interest on the mailing lists from previously uninvolved individuals.
3. The project needs a working process definition. What is the review
process for contributions, recommendations for engaging before writing
large amounts of code, etc.
4. The project is using source and binaries with a number of
non-ASF-approved licenses. This needs remediation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues that we are aware of at this point.
How has the community developed since the last report?
There has been no previous report - so nothing to report here.
How has the project developed since the last report?
There has been no previous report - so nothing to report here.
CloudStack has been in the incubator for approximately 1.5 months. Mailing
lists have migrated, accounts for the initial committers have been set up,
and the initial code drop/git repo has been setup. Many new names are now
participating in conversations on the mailing lists, with several of them
volunteering to help move things along. The number of submitted patches from
'new names' in the month of May is in the double digits, and range from
trivial one line fixes to two major patches with over 1,000 changed lines
each. The community is beginning to exercise some of its decision making
power by deciding about release tempo, future version schemes and numbers,
and a number of other internal plumbing issues. Much remains to be done in
preparation for the initial release, and those tasks are being identified.
We also have a number of external resources (bug tracker, wiki, CI) that
are still awaiting migration.
Top 3 Issues to address in move towards graduation
- The project is using source and binaries with a number of
non-ASF-approved licenses. This needs remediation.
- Diversity of the contributor base still needs to be expanded.
- While we are making progress, there still remains a number of large
pieces (bug tracker, wiki, test infra) that still need to be migrated
to ASF infrastructure.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues that we are aware of at this point.
How has the community developed since the last report?
See the above narration, but generally speaking the community is beginning
to exercise its decision making powers, largely around internal plumbing
issues at the moment. We are also seeing a number of new developers
submitting patches.
How has the project developed since the last report?
The project continues to have many issues to tackle for its first release
and is identifying and moving forward on those issues. Work continues on
solutions to remove the need to massive (or any) amount of additional
hardware to test/develop with in an effort to lower the barrier to
participate.
The top 3 issues to address to move towards graduation:
- CloudStack's source still contains works that are prohibited for release
under ASF guidelines
- Performing a release
- Migration of infrastructure (bug tracker, CI, websites, etc)
How has the community developed since the last report:
As of the time of this report at least one new committer has been added.
Additionally, a number of previously unknown developers have begun making
substantial quantities of bugfixes and even working on new functionality.
How has the project developed since the last report:
The project itself continues to deal with process questions as well as
learning how to operate in the new environment. A good deal of work has
been happening on resolving the problems in the code base around licensing,
though not currently close to finishing.
A list of the three most important issues to address in the move towards graduation
1. Licensing work
2. Finishing up the move of CloudStack infrastructure resources to the ASF.
3. Shipping a release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
CloudStack has added 6 new committers in the month of July.
We had BOF and hackathon time at OSCON, which was a positive benefit for
those committers who attended, particularly in being able to delve into
issues around incubation, branding, and licensing. Additionally two
committers presented tutorials at OSCON one focused on end users deploying
CloudStack and the other focused on developers hacking on CloudStack, both
had great attendance.
We have also had some offers of contribution from people at Bitergia who are
interested in contributing the work that they have done around metrics. which
was a very encouraging start to growing the community.
How has the project developed since the last report?
Lots of modularization has been injected into CloudStack, which makes some
of our licensing issues far less of a problem as we can merely turn the
affected code off by default.
The wiki has begun migration to an ASF hosted wiki instance.
One of the CloudStack committers provided a dramatically easier way to be
able to test and develop for CloudStack in the form a completely contained
CloudStack environment that can be run as a VirtualBox VM. Much additional
enhancement has been contributed to this making the process easier and
easier to update.
We also saw the movement of documentation from binary .docx files to
DocBook XML; while this effort isn't complete it does permit folks to far
more easily collaborate, as well as providing a far better interface
for l10n.
Signed-off-by: brett, jukka, jim
A list of the three most important issues to address in the move towards
graduation
1. Continuing to build the community and increase diversity
2. Shipping a release
3. Transfer trademark, etc. to Apache
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No issues at this time
How has the community developed since the last report?
The project has continued to improve its diversity, adding
Chip Childers, John Kinsella, and Wido den Hollander to the PPMC
and 3 new committers since the month of August. (Mice Xia, Jason
Bausewein, and Joe Brockmeier.) We have also taken on a new mentor,
Noah Slater.
Contributors and committers have been active in promoting CloudStack
at events, such as LinuxCon, Ohio LinuxFest, PuppetConf, a get-together
at Schuberg Philis, and a number of other events.
The community is participation at LinuxCon EU and ApacheCon EU and
a number of other events through the remainder of 2012.
Citrix is acting as primary sponsor of a CloudStack Collaboration
Conference for November 30 through December 2 in Las Vegas. The
conference is open to the community, and programming for the event
will be chosen by a committee that includes members of the CloudStack
community outside Citrix.
How has the project developed since the last report?
The pending 4.0 release has been branched. The project has made a great
deal of progress towards the 4.0 release, handling a number of technical
issues (such as a move to Maven) and resolving almost all known legal
issues that would pose an obstacle to a release. The sole remaining
blocker is under discussion and should be resolved shortly.
The Jira instance for CloudStack was stood up in early September. License
checks have been automated to ensure that we remain compliant with Apache
guidelines going forward.
Signed-off-by: nslater, mfranklin
This is the first phase on incubation, needed to start the project at Apache.
Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).
date | item |
---|---|
2013-02-25 | Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. Completed via PODLINGNAMESEARCH-23 |
N/A | If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names. |
N/A | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. |
2012-05-27 | If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted. |
date | item |
---|---|
2012-05-27 | Ask infrastructure to create source repository modules and grant the committers karma. |
2012-04-19 | Ask infrastructure to set up and archive mailing lists. |
2012-04-17 | Ask infrastructure to set up issue tracker (JIRA, Bugzilla). |
2012-07-14 | Ask infrastructure to set up wiki (Confluence, Moin). |
2012-11-01 | Migrate the end-user site |
date | item |
---|---|
2012-09-10 | Identify all the Mentors for the incubation, by asking all that can be Mentors. |
2012-09-10 | Subscribe all Mentors on the pmc and general lists. |
2012-09-10 | Give all Mentors access to the incubator SVN and git repositories. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file) |
2012-10-10 | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html' |
date | item |
---|---|
2012-09-12 | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. |
2012-09-14 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. |
date | item |
---|---|
2012-09-14 | Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. |
2012-09-14 | Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. |
date | item |
---|---|
2012-10-05 | Check that all active committers have submitted a contributors agreement. |
2012-10-05 | Add all active committers in the STATUS file. |
2012-10-05 | Ask root for the creation of committers' accounts on people.apache.org. |
date | item |
---|---|
2012-09-14 | Remove all binaries from source repo |
2012-10-09 | Fix artifact naming so that they comply with ASF guidelines |
2012-10-10 | Comply with ASF Cryptography requirements for Export compliance |
2012-10-08 | Write release process documentation |
These action items have to be checked for during the whole incubation process.
These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.
N/A
Things to check for before voting the project out.