Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Board meeting on 19 October 2016; report to be submitted by 12 October

A cloud agnostic library that enables developers to access a variety of
supported cloud providers using one API.

== Project Status
--------------==

We are in the final stages of preparation for the jclouds 2.0 release. This is
long-awaited and much needed by many users, and we are close to completing the
feature set that we want to ship. The last details of the Azure ARM provider
are being wrapped up; with that, we will have support for all of today's major
cloud providers.

We have also completed integration with the new ProfitBricks REST API, and
have been able to move the jclouds Docker provider to a very stable state.

== Community
---------==

We have continued to receive substantial contributions from the community,
especially to the ProfitBricks and OneAndOne providers. This is very pleasing,
but we are still looking for additional ways to encourage participation.

We've tried lowering the barrier to becoming a committer; however, this has
not resulted in a noticeable increase in sustained activity. We are currently
discussing changes to our release cadence, with a view to releasing more
frequently, driven by user demand (e.g. for a set of required fixes to a
particular provider) rather than release dates or feature-based milestones.
This will hopefully allow users to keep up to date with the project more
easily, and encourage contributions by reducing the turnaround time from PR to
officially released code.

Our GSoC student completed their project successfully, which is in trunk and
will be part of the jclouds 2.0 release.

There are currently 11 PMC members and 23 committers.
Last committer: 2016-02-05 (Reijhanniel Jearl Campos)
Last PMC member: 2015-09-20 (Zack Shoylev)

We are currently voting have voted on adding a new PMC member , to and the NOTICE has just been sent to the
board. We hope to have him added after the 72 hours if there are no
objections. This will help with the intended accelerated release cadence and
to bring new energy to our community involvement efforts.

== Community Objectives
--------------------==

Our immediate aim is to complete the Azure ARM provider and release jclouds
2.0 as soon as possible. Beyond that, we will be focusing on implementing the
new release criteria to improve the engagement with the community and
encourage participation.

Releases


== Releases ==--------

The last jclouds release, 1.9.2, took place on 2016on 2016-01-16.
As discussed above, we are aiming to release jclouds 2.0 shortly.