Board meeting on 17 April 2024; report to be submitted by 10 April
There are no issues requiring board attention
A cloud-agnostic library that enables developers to access a variety of cloud
providers using one API.
== Project Status ==
During the last months, we initiated discussions to move the project to the
Attic, given the low activity and the concerns shared in previous reports.
The discussion started in October 2022 (https://s.apache.org/jclouds-attic)
and the Brooklyn and Karaf communities expressed interest in keeping the
project alive and helping the project. Despite the very welcomed good
intentions, however, nothing actually happened in the form of actual
contributions, further engagement with the project, etc, and for months we
have been just waiting for something to happen beyond the will to keep the
project alive.
The Attic discussion is a perfect example of the current status of the jclouds
community: there are people interested in keeping the project alive, but no
one has the time and/or energy to actually do it, and in this scenario, it has
been discussed that we would probably better serve the community by moving the
project to the Attic and set clear expectations for our users, instead of
keeping it in the current limbo of inactivity.
Revisiting this thread in March 2024 shows no new interest:
https://lists.apache.org/thread/ql50d2v7s3ccywm2frkmqsqwdzj402fb
== Community ==
Last committer: 2018-07-23 (Daniel Estevez)
Last PMC member: 2021-03-14 (Jean-Baptiste Onofré)
== Community Objectives ==
- Evaluate 2.6.0 release feedback and evaluate a possible 2.6.1 release in April
- Initiate attic process in May and write post-mortem
== Releases ==
The last major jclouds release, 2.6.0, took place on 2024-03-09.
The last bugfix release, 2.2.1, took place on 2020-05-14.