This was extracted (@ 2025-01-15 22:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Report was filed, but display is awaiting the approval of the Board minutes.
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 few years, 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 * Initiate attic process in October 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.
@Willem: pursue an attic resolution
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 few years, 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 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.
here 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 postmortem == 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.
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. == Community == Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Finalize the Attic movement discussion and release 2.6.0 in Q1. This is planned to be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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. == Community == Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Finalize the Attic movement discussion and release 2.6.0 in November 2023 which is planned to be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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. == Community == Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Finalize the Attic movement discussion and release 2.6.0 in July 2023 which is planned to be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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. == Community == Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Finalize the Attic movement discussion and release 2.6.0 in 2Q2023 which may be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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 == We continue to discuss the low activity of the project and the impending lack of quorum for releases. Several individuals proposed joining the jclouds team, including members from the Brooklyn and Karaf projects, but subsequent discussion suggested insufficient bandwidth to contribute and they have not filed any issues, submitted any PRs, or otherwise participated in the project. As such, moving the project to the attic soon seems the most likely next step. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.6.0 in 2Q2023 which may be the final release. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds development has slowed from 123 commits from 26 contributors in 2018 to just 24 from 6 contributors in 2022. This is despite growing downloads over the last 12 months from 50,000 to 80,000 for jclouds-core alone. Unfortunately the number of active committers has shrunk and we will soon lack quorum for future releases. We are considering moving the project to the attic and currently soliciting feedback from the community. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.6.0 in 4Q 2022. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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 == Project successfully released 2.5.0 in Q1 2022. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.6.0 in 3Q 2022. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
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 == Project successfully released 2.5.0 in 1Q2022 and stopped publishing jclouds-labs release artifacts to streamline the release process. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.6.0 in 3Q2022. == Releases == The last major jclouds release, 2.5.0, took place on 2022-03-26. The last bugfix release, 2.2.1, took place on 2020-05-14.
== Project Status == Project successfully released 2.4.0 in Q3 2021. The team fixed some modern Java incompatibilities and resolved to streamline the release process by dropping the labs packages. There are no issues requiring board attention. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.5.0 in Q1 2022. == Releases == The last major jclouds release, 2.4.0, took place on 2021-09-10. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == Project successfully released 2.4.0 which improved compatibility with modern Java environments and merged several PRs from the community. The team is evaluating how to reduce the release overhead by simplifying the jclouds-labs repositories, possibly removing them altogether. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.5.0 in Q1 2022. == Releases == The last major jclouds release, 2.4.0, took place on 2021-09-10. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == Project continues to modernize dependencies to make it work better with modern Java environments, continuing work started in 2.3.0. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.4.0 in Q3 2021. == Releases == The last major jclouds release, 2.3.0, took place on 2021-03-06. The last bugfix release, 2.2.1, took place on 2020-05-14. == Comment == There are no issues that require Board attention.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds recently released 2.3.0, which modernized many dependencies and addressed OSGi pain points. == Community == We continue to merge fixes from the community. Apart from this the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2021-03-14 (Jean-Baptiste Onofré) == Community Objectives == Release 2.3.1 in Q3 2021. == Releases == The last major jclouds release, 2.3.0, took place on 2021-03-06. The last bugfix release, 2.2.1, took place on 2020-05-14. == Notes == There are no issues that require Board attention.
WHEREAS, the Board of Directors heretofore appointed Ignasi Barrera (nacx) to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Ignasi Barrera from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Andrew Gaul (gaul) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ignasi Barrera is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Andrew Gaul be and hereby is appointed to the office of Vice President, Apache jclouds, 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. Special Order 7A, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have upgraded our Guava and Guice dependencies, addressing several user issues. However, these changes introduced some incompatibilities in OSGi environments, and we're looking at addressing those and relaxing the constraints on the core dependencies of the project to minimize the impact on the jclouds ecosystem. We are looking forward to releasing 2.3.0 once the fixes are in place. == Community == There have been contributions from people in the community, especially around our OSGi integration. This is an ongoing effort mainly driven by a fairly new contributor that is being really helpful and unblocked several issues that prevented jclouds from upgrading to newer Java versions. Apart from this, the overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Release 2.3.0 in Q1 2021. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have upgraded our Guava and Guice dependencies, addressing several user issues, and two community members expressed interest in upgrading gson and OkHttp which would further modernize jclouds. We plan to release 2.3.0 in a few months with or without these fixes. There has been a member of the community that is contributing OSGi related improvements that hopefully would help the project better support those environments while helping us move forward without the limitations we had in the past. == Community == The project has merged a few small pull requests from 2 contributors over the last three months. The overall activity remains low. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Release 2.3.0 in 4Q2020. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == The project is modernizing several stale dependencies that have caused issues for our users and developers: Guava, gson, and OkHttp. Otherwise, the activity remains low. Modernizing gson is challenging due to our dependency on OSGi and on some gson packages that were removed from the OSGi bundle in newer versions. Keeping OSGi support has become challenging due to the lack of expertise across the active members. We are discussing different approaches and the tradeoffs of dropping support for that (and probably offloading that to Karaf or other projects) so that we can move forward the project without being blocked on this while providing a way for existing OSGi users to keep using jclouds. == Community == The project has merged several small pull requests from 7 contributors over the last three months. Notably, one user stepped forward with a solution to the gson dependency issue. There was also interest from a user in helping us modernizing the builds and improve our Jenkins setups. We voted on welcoming him as a committer to facilitate as much as possible getting involved (he was a well-known member of the community that has been maintaining jclouds-related projects for a long time), but even though communication was fluid at the beginning, just before the vote and after it, all communication attempts failed and we never heard from him again, so he was not added to the committer group in the end. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Complete dependency upgrades and release 2.3.0 in 3Q2020. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.2.1, took place on 2020-05-14.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds continues to squash bugs but little feature work. There are sporadic issues being reported and fixed, but activity overall is low. The project remains stable, but there are no plans or requirements to modernize it and upgrade it to newer Java versions. == Community == There have been small contributions from the community and bugfix reports as in previous quarters. As said in previous reports, most of the PMC and committers are now "pure" volunteers (with $dayjob no longer related to jclouds). There is also a lack of traction, requests, and general interest from the community itself. This could be an issue but it simply shows that the project is no longer that relevant in the space and that the primitives it provides are an "already fixed problem". Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Be able to keep fixing important issues, and help anyone interested in contributing to the project be successful at it. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.1.3, took place on 2019-10-21.
A cloud-agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds continues to squash bugs but little feature work. As commented in the previous report, we are still aiming to support newer Java versions. The availability of the current PMC member is low and we're looking for champions to modernize the project dependencies, but we have not seen interest beyond some few comments in the JIRA issues. At this point, it is unlikely that we'll find someone in the community willing to take this effort. == Community == There have been small contributions from the community and bugfix reports as in previous quarters. THe concern around the amount of time being dedicated to the project is still there, since most of the PMC and committers are now "pure" volunteers (with $dayjob no longer related to jclouds). Another concern keeps being the lack of traction, requests, and general interest from the community itself. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Find a champion that helps us upgrade the core dependencies that pin us to old Java versions. Keep engaging contributors on Slack, and propose them as new committers as appropriate. Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last major jclouds release, 2.2.0, took place on 2019-10-21. The last bugfix release, 2.1.3, took place on 2019-10-21.
WHEREAS, the Board of Directors heretofore appointed Andrea Turli (andreaturli) to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrea Turli from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by consensus to recommend Ignasi Barrera (nacx) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrea Turli is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Ignasi Barrera be and hereby is appointed to the office of Vice President, Apache jclouds, 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. Special Order 7A, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds continues to squash bugs but little feature work. There is a community interest in a new release that incorporates recent work on Azure. We are releasing a new major and a bugfix release this week. We are aiming to support newer Java versions, and many efforts have been put in upgrading to Java 8. There are several dependencies that still pin the project to this version of Java, and further upgrading it would require upgrading those core dependencies. We are trying to find champions in the community to lead that effort, as the energy and availability of the current Committers and PMC members are low (see the Community section below). == Community == There have been small contributions from the community and bugfix reports as in previous quarters. We have seen, however, that the issues that are being reported recently are more about the core features of the project instead of the simple features of a specific provider. This is a bit encouraging since some of those reports had a level of detail that shows that there was interest in digging down and understanding the most complex parts of the codebase. There is still a concern around the amount of time being dedicated to the project since most of the PMC and committers are now "pure" volunteers (with $dayjob no longer related to jclouds). Another concern keeps being the lack of traction, requests, and general interest from the community itself. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Find a champion that helps us upgrade the core dependencies that pin us to old Java versions. Keep engaging contributors on Slack, and propose them as new committers as appropriate. Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last jclouds release, 2.1.2, took place on 2019-02-07.
== Description== A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds continues to accumulate bug fixes but little feature work. Notably we are struggling with compatibility with Java 8 and newer Guava versions, which vexes our users. After a fruitful discussion with the Karaf community, we decided to move jclouds-karaf and jclouds-cli projects to the Karaf project. This has removed a blocker for new releases of jclouds, and we think it will help both communities going forward. == Community == We had 12 contributors this quarter - including several new ones - in addition to the existing PMC and committers, and more activity on our issue tracker. Notably, there have been very promising contributions from some new developers to help with technical debt, particularly to remove uses of an internal package that makes it impossible to use jclouds in an OSGi environment with newer versions of Gson. There is a growing concern around the amount of time being dedicated to the project, since most of the PMC and committers are now "pure" volunteers (with $dayjob no longer related to jclouds). Another concern is the lack of traction, requests, and general interest from the community itself, or from downstream projects like Apache Brooklyn. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Unblock the release of jclouds 2.2.0, which will provide Java 8 support. Keep engaging contributors on Slack, and propose them as new committers as appropriate. Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last jclouds release, 2.1.2, took place on 2019-02-07.
== Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We are still struggling to release a version that supports Java 8 and newer Guava versions. The main blocker for this has been the dependency on Karaf and the lack of expertise on it by the active community. We've been working with the Karaf community for around a year now, but results have not materialized yet. We think it is not sustainable to have such a hard dependency on jclouds, especially when the active community has no expertise on it and when that dependency is not strictly related to the direct value jclouds provides. For this reason, we are working with the Karaf community and plan to transfer the jclouds-karaf and jclouds-cli to them. Our first conversations are positive and we believe that this new home for those projects, although they will be disconnected from the official jclouds release cycle, will provide continued and better support for their existing users. This transfer also makes sense because Karaf already has some plans to integrate their recent Kloud project with jclouds. == Community == Outside the existing PMC and committers, we have had the usual contribution pace. We've had some contributions to the Azure Blobstore provider with good engagement in the issue tracker, slack and the mailing list by the contributor. We will keep an eye on upcoming contributions. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21(Andrea Turli) == Community Objectives == Unblock the release of jclouds 2.2.0, which will provide Java 8 support. Transfer jclouds-karaf and jclouds-cli to the Karaf project. Keep engaging contributors on Slack, and propose them as new committers as appropriate. Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last jclouds release, 2.1.2, took place on 2019-02-07.
== Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == jclouds continues to accumulate bug fixes but little feature work. Notably we are struggling with Java 8/newer Guava compatibility which vexes our users. We continue to work with the Karaf community on one of these issues. This blocks release of jclouds 2.2.0. We have migrated our source repositories to Gitbox, and will be deprecating and archiving the legacy jclouds GitHub org in such a way as to allow contributors to migrate easily. We've also moved our CI infrastructure from CloudBees DEV@cloud to the ASF Jenkins installation. One consequence of that is that we have been able to results of our live tests public, which will be valuable to the community. == Community == Outside the existing PMC and committers, we had 12 contributors this quarter (including several new ones) and more activity on our issue tracker. Notably, one potential contributor sent a pull request for a new Aliyun OSS provider, but this will require significant rework to merge. It is important to note that these kinds of large pull requests are difficult to review, and it may take more time than desired to guide and educate the contributors, since most of the PMC and committers are now "pure" volunteers (with $dayjob no longer related to jclouds). Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21(Andrea Turli) == Community Objectives == Unblock the release of jclouds 2.2.0, which will provide Java 8 support. Keep engaging contributors on Slack, and propose them as new committers as appropriate. Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last jclouds release, 2.1.1, took place on 2018-08-16.
== Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == Project development has slowed down. Most contributions are bug fixes and small additions, but no big features have been developed recently. We are getting continued contributions to the DimensionData provider, and we hope we can move it to a stable state and release it out of labs soon. We are also actively working with the Karaf community to move our jclouds-karaf integration to Java 8. This is taking more time than we expected, but the Karaf community is taking ownership of this and is directly working on jclouds-karaf. They also proposed to implement a Karaf compute service in jclouds to leverage jclouds provisioning features to provision applications Karaf and manage their lifecycle. We look forward to discussing this as we think it would be a great new functionality and addition to jclouds. == Community == We continue to receive contributions from several individuals. We've found that having the slack channel facilitates communication and training, as the codebase has a considerable learning curve. In particular, there is a contributor that is doing great at learning new technologies. He opened a pull request a while ago but he is still actively addressing issues, tweaking, and learning. His feedback and participation in slack are being valuable for us and we are happy to see this kind of new contributions and engagement. Mailing list activity is low, mainly because all recent contributions have been mostly bug fixes. Also, slack conversations are mostly about training and explaining some isolated codebase internals, so there are not many things that are relevant to be moved to the mailing list. Two of the most active PMC members have changed their job recently, and although their day job was not about directly contributing to jclouds, it was related to the project, so we expect their code contributions and related activities to decrease since the new jobs are not related to the project. We have not many active PMC members, so this is a situation we will have to handle carefully and plan accordingly if we see that this change affects the project. Last committer: 2018-07-23 (Daniel Estevez) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == * Release jclouds 2.2.0 with Java 8 support. * Keep engaging the slack contributors and propose them as new committers. * Monitor the PMC and ensure we have enough resources to properly manage the project. == Releases == The last jclouds release, 2.1.1, took place on 2018-08-16.
== Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have upgraded to Java 8 to a newer Guava version. It will have a significant impact on users but we believe it will simplify jclouds adoption in modern environments. We have discussed it long enough to have a clear upgrade path, and will keep the old branches JDK 7 compatible. Users already know that the next major release will require Java 8, so although the impact is significant, there should be no issues. We are working with the Karaf community to complete the migration of our jclouds-karaf integration to Java 8 too and then we'll be ready to release. == Community == The project continues to receive contributions in the form of code and issues from new developers, indicating that development is healthy and that users are feeding back their problems and feature suggestions. We have detected, though, that interactions in the mailing list have slowed down, and we are starting to have some discussions on how to improve engagement. We're kicking off the process of supporting Alibaba Cloud hoping to get contributions from users of that cloud. Currently there are 25 committers and 12 PMC members. Last committer: 2018-01-26 (Jim Spring) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == Continue to monitor our community for potential new committers and PMC members. == Releases == The last jclouds release, 2.1.0, took place on 2018-02-21.
==Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have released jclouds 2.1.0, which support for OpenStack Keystone v3, a long-standing issue that prevented jclouds from supporting modern OpenStack versions. This has been eagerly awaited by the community and we have already received (although off-list) some positive feedback from users. In this release, several providers have reached a good level of maturity and have been promoted out of "labs": Azure ARM, Packet and OpenStack neutron for compute, and Google Cloud Storage and Backblaze B2 for storage. Another discussion that is taking place is the need to move to Java 8 as our officially supported Java version. This presented some compatibility issues with the Guava library, which is widely used in the project, but we have finally been able to come to an agreement on the upgrade plan. There has been valuable feedback from the community regarding this topic and we now feel comfortable in moving forward with the Java and Guava versions. == Community == The project continues to receive contributions in the form of code and issues from new developers, indicating that development is healthy and that users are feeding back their problems and feature suggestions. We're also working to see if an Aliyun user can contribute work done on a private branch back into the open-source repository. It has been great to see a contributor-initiated effort to move the project forward to Java 8 and a newer Guava version. It is not an easy change given our codebase and we are happy to see people is not afraid of trying to change the project core, as one recurrent topic is that the learning curve to understand the jclouds core is quite high. Last committer: 2018-01-26 (Jim Spring) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == - Upgrade to Java 8 to support newer Guava version. This will have a significant impact on users but we hope it won't be an issue at this point. - Continue to monitor our community for potential new committers and PMC members == Releases == The last jclouds release, 2.1.0, took place on 2018-02-21.
== Description == A cloud agnostic library that enables developers to access a variety of cloud providers using one API. == Project Status == We have finally been able to work on adding support for OpenStack Keystone v3, a long-standing issue that prevents us from supporting modern OpenStack versions. We are actively testing and expect to be able to cut a new release in the short term, which will be a significant step as this is one of the features most eagerly awaited by the community. Separately, the Azure ARM provider has reached a sufficient level of completeness and stability for promotion out of the "labs" in the next release. We have seen continuous contributions to this provider as well as help in testing, and are happy to see that it is one of the providers getting more attention recently. The OpenStack Neutron API has also proven to be very stable, and we intend to work on promoting it out of "labs" too. Progress continues on expanding the BlobStore portable interface which now includes storage tiers. == Community == We have started to use the #jclouds slack channel and are promoting it on the mailing list and website as an alternative to IRC. Several contributors have already joined the channel, which has lead to productive chats about implementation details, source code internals, etc. It seems that Slack is more user-friendly than IRC, and it is easier to engage users there, so we will continue to promote and use this channel. One user has Aliyun OSS support in a private branch and we have asked them to share this code for possible mainline inclusion. The project continues to receive contributions in the form of code and issues from new developers, indicating that development is healthy and that users are feeding back their problems and feature suggestions. There are currently 12 PMC members and 24 committers. Last committer: 2017-02-17 (Svetoslav Neykov) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == - Release jclouds 2.1.0 soon, as it contains long-awaited features, especially around the OpenStack and Azure ARM providers - Continue to monitor our community for potential new committers and PMC members == Releases == The last jclouds release, 2.0.3, took place on 2017-11-30.
WHEREAS, the Board of Directors heretofore appointed Andrew Gaul (gaul) to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrew Gaul from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Andrea Turli (andreaturli) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrew Gaul is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Andrea Turli be and hereby is appointed to the office of Vice President, Apache jclouds, 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. Special Order 7I, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Project Status == We have addressed a long-standing and unpopular compatibility issue that tied jclouds to an old version of Guava, a library that is common in many Java environments. The change will allow users to use the latest jclouds version with a modern Guava version. There has been ongoing work and discussion around object tiering and asynchronous payloads. Although the initial contributors have not been participating in the latest conversations, some progress has been made and concrete proposals have been pushed as pull requests for review. We hope to come to an agreement on the desired asynchronous behaviors and to introduce them so users can start trying them out. We have started validating jclouds builds against Java 9. Several issues have been identified, and we have filed corresponding JIRA tickets to enable the community to properly plan fixes. There has been recent interest in the Azure ARM provider coupled with external contributions to develop a set of new features. We hope to be able to make these features available in the coming 2.1.0 and 2.0.3 releases soon. For the 2.1.0 release, we hope to be able to promote the provider, which has been very stable and is being used in production, out of the jclouds "labs" repo. == Community == We had one GSoC student working on implementing a portable queuing abstraction, but unfortunately the student did not complete the goals. There was very little interaction with the community;the code, submitted late, was insufficient. This is the first time we have had to fail a student; we still believe that GSoC is a positive initiative that can usefully contribute to jclouds, however - in past years, the students have completed their projects and their code is now part of jclouds. Getting students onboard as contributors post-GSoC remains a challenge. The project has seen several new issue reporters of late, but unfortunately this has not (yet) translated into new contributors. There has been some renewed activity on IRC, although the number of regular participants there has decreased. The mailing list activity has slowed down over the last quarter, but we expect to encourage people to participate with the release of jclouds 2.1.0 and 2.0.3, and by spending more time promoting the project on social media. There are currently 11 PMC members and 24 committers. Last committer: 2017-02-17 (Svetoslav Neykov) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == * Release jclouds 2.1.0 and 2.0.3 in 4Q2017 (slipped from previous report) * Promote the Azure ARM provider out of the jclouds labs repo * Improve project outreach and promotion on social media == Releases == The last jclouds release, 2.0.2, took place on 2017-07-06.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Project Status == Ongoing improvements to set of supported providers and APIs have characterised the past few months, with continued welcome support from a variety of sources: * As suggested in the board response to a previous report, we asked the Apache Karaf community for help with a blocking issue regarding the jclouds Karaf integration. The response time and the feedback was great, and the contributions allowed us to unlock our master branch. * We promoted the Packet, B2 and Google Cloud Storage providers from the jclouds labs repository for "incubating" providers to the main jclouds repo. This means that we start providing backward compatibility for their respective APIs. * We've started receiving contributions from DimensionData. They are contributing an API and provider for their cloud, which we expect to be completed by the next release if the contributions continue to arrive at the current pace. * We have started to plan the implementation of the OpenStack Keystone v3 API, which is a major issue in terms of providing continued support for OpenStack. So far, we have received very little feedback from the community, though. We will be starting the effort but have not been able to engage (yet) active users of the OpenStack features, so progress will likely be slower than desired, given the lack of in-depth knowledge of the target API. We have also completed some housekeeping by removing the essentially unmaintained jclouds Clojure bindings, after receiving no responses indicating active use or interest in the community. == Community == We are continuing discussions around async APIs that have been proposed by several community members. The proposal is exciting but will require careful consideration, given that the previous jclouds async API ended but being removed due to its complexity. The contributors of the proposal are doing very well, and we are thankful for their patience and collaboration. We were very happy to have received such quick help from the Apache Karaf community in response to a request for assistance on a blocking issue - a great expression of collaboration between projects. There is ongoing work on a GSoC project to create a Message Queue abstraction. This will allow us to offer a portable API for queue operations across providers, with Azure Queues being the reference implemented by the student. The community composition is largely unchanged, with no new committer or PMC member additions. We have not seen the kind of contributions from the community recently that would put someone "on the radar". There are currently 11 PMC members and 24 committers. Last committer: 2017-02-17 (Svetoslav Neykov) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == * Resolve our compatibility issues with Guava 21 and Java 9. The former will require us to drop support for some previous Guava versions, and we want to make sure users have a smooth upgrade path. * Release 2.1.0 in 3Q2017 == Releases == The last jclouds release, 2.0.2, took place on 2017-07-06.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Project Status == We have completed the Packet.net provider and continued to receive contributions for providers OneAndOne, ProfitBricks, and Azure ARM. We have also started to receive contributions from DimensionData to add support for their cloud. Assuming the current rapid speed of progress continues, we expect to have the DimensionData provider completed soon. To aid users in upgrading to more recent jclouds versions, we are discussing how to keep up to date with the latest Google Guava versions, while still being backwards compatible with reasonably old ones. The Guava versions we support have generally been older ones, representing a conservative choice in terms of required dependencies, but users are now experiencing some issues we would like to address as soon as possible. Although we have several Karaf PMC members in the jclouds PMC, the lack of deep knowledge of Karaf among the active contributors is causing some issues for a jclouds/Karaf integration we maintain. Specifically, we are stuck with an upgrade of the version of Karaf that has broken the jclouds CLI (a convenience tool not widely used), and we are struggling to fix it. We'll probably have to ping the Karaf dev@ list and ask for help there. There has also been a limited amount of activity to support Java 9. == Community == We have received three applications for GSoC for two projects, and some of them are promising. Some discussions about how to extend jclouds to natively support asynchronous operations has been raised from the community, and a related proposal has been discussed. We are very pleased to see community proposals such as this one that require a deep dive into the jclouds code! We've also seen an cluster of recent discussions and activity relating to the OpenStack Swift provider. There are currently 11 PMC members and 24 committers. Last committer: 2017-02-17 (Svetoslav Neykov) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == * Promote Packet, B2, GCS and Azure ARM providers out of labs into the main repository. The cloud APIs for the latter are changing quite fast, so perhaps it will remain in labs a bit more until the latest APIs are more stable. * Evaluate and engage GSoC students. Let's see if we can do better to have them stick around after the project is completed. This has not happened with the previous students. * Release 2.0.2 or 2.1.0 in 2Q2017. == Releases == The last jclouds release, 2.0.1, took place on 2017-02-27.
== Project Status == We have two new providers under review: 'packet.net' and 'vagrant'. Additionally we are reviewing a large feature for the 'oneandone' provider. We have seen some interest in supporting OpenStack Keystone v3. jclouds currently supports the deprecated v2, which makes it hard to use jclouds with new OpenStack installations difficult. Adding support for Keystone v3 is an important step to continued OpenStack support, but will be a significant addition that will require effort and coordination. There are currently no full-time developers dedicated to jclouds, so this will likely be challenging. == Community == The project continues to receive a moderate amount of issues and pull requests, with regular questions and responses from community members on the mailing list. There have been some recent contributions from new contributors, with several questions that demonstrated good understanding of the code. Given that the jclouds codebase is perceived to have a steeper learning curve, this is encouraging. There are currently 11 PMC members and 23 committers. Last committer: 2016-02-05 (Reijhanniel Jearl Campos) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == - Help progress contributions to new and existing providers - Work towards a plan for OpenStack Keystone v3 support - Prepare for 2.0.1 bug fix release in Q1 2017 - Prepare for GSOC 2017 by creating and tagging potential projects with "gsoc2017" == Releases == The last jclouds release, 1.9.3, took place on 2016-11-23. 2.0.0 was released shortly before that, on 2016-11-14.
WHEREAS, the Board of Directors heretofore appointed Ignasi Barrera to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Ignasi Barrera from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Andrew Gaul as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Ignasi Barrera is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Andrew Gaul be and hereby is appointed to the office of Vice President, Apache jclouds, 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. Special Order 7D, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
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 have voted on a new PMC member 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 == The last jclouds release, 1.9.2, took place on 2016-01-16. As discussed above, we are aiming to release jclouds 2.0 shortly.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Project Status == We have continued to receive contributions from various community sources, including several vendors that are developing and contributing providers for their offerings. It is encouraging that we've found them to be very open to discussing design decisions; some of these discussions have also resulted in small additions to the jclouds core, which thus also continues to evolve. We've had some new contributions adding support for the OneAndOne provider, recently added support for Blackblaze B2 storage and expect to have an Azure ARM provider completed shortly. The plan is to then release jclouds 2.0. == Community == Activity on the user and development lists has remained pretty stable. Questions continue to be answered in a reasonable amount of time, and we have been able to encourage users to (with some guidance) open pull requests for their desired changes themselves. There were two jclouds presentations at ApacheCon NA. Unfortunately, we weren't able this time to meet representatives from downstream users such as Apache Brooklyn or Apache Stratos, as they weren't attending. We find these kinds of meetings, which we have conducted at past ApacheCon EU events, to be very useful in understanding the needs of those projects and helping us plan our roadmap. We have one student working on a GSoC project, which looks likely to be completed on time. 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) == Community Objectives == Our immediate aim is to wrap up work on the Azure ARM provider in preparation for a subsequent jclouds 2.0 release. More generally, we continue to try to encourage and supervise, where necessary, new contributors to grow the committer base. == Releases == The last jclouds release, 1.9.2, took place on 2016-01-16. As discussed above, we are aiming to release jclouds 2.0 shortly. Depending on the time required, we are considering an interim jclouds 1.9.3 release to address issues resolved since 1.9.2 for users.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. PROJECT STATUS We are preparing for the 2.0 release. Since the last release (1.9.2), activity has slowed down a bit in terms of code contributions, but we've been successful at engaging ProfitBricks in the project. They are contributing resources to create the provider for their new REST API, and have also donated testing account for jclouds. We have received several GSoC 2016 proposals, and have a couple of mentors on the PMC. We're now in the project evaluation phase and are waiting to see if the proposals are accepted. COMMUNITY Community activity has increased a bit on the dev and user mailing lists, and we've had several approaches from students interested in working on our proposed GSoC projects. Alongside the welcome engagement for ProfitBricks, we've also had a recent contribution for a new Azure compute provider from the Open Source team at Microsoft. They have allocated resources to contribute to the project and are leading the development of an updated provider based on the new Azure ARM API. We've also received and merged several pull requests from new contributors. This is a welcome sign, as the nature of the jclouds codebase can make first-time contributions quite intimidating at first glance. In addtion, two jclouds talks have been accepted for ApacheCon NA, so we will be there and look forward to engaging with the community and interacting with downstream projects. 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) COMMUNITY OBJECTIVES * Finally determine the scope and complete the feature set for jclouds 2.0, to include completion of support for Azure ARM, as well as promotion of the Docker and ProfitBricks REST APIs from jclouds-labs * Encourage and supervise, where necessary, new contributors to grow the committer base. RELEASES The last jclouds release, 1.9.2, took place on 2016-01-16.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- Likely related to the holiday period, activity around jclouds and, specifically, development of the existing code has been relatively quiet over the past quarter. That being said, there have been a number of recent questions from new users expressing interest in developing custom cloud providers, which is a welcome sign of ongoing interest and engagement in the project. The core community has also continued to be very responsive to questions from users. Community --------- We are also having discussions about how to grow the committer base. Due to the nature of the project it is difficult to find people interested in more than one provider or in several areas of the project. We are having discussions to effectively mitigate this and to allow the community to grow faster and better. Regarding this there is a committer candidate under the radar. There are currently 11 PMC members and 22 committers. * Last committer: 2014-08-01 (Chris Custine) * Last PMC member: 2015-09-20 (Zack Shoylev) Community Objectives -------------------- * Finally determine the scope and complete the features for jclouds 2.0.0. * Encourage and supervise, where necessary, new contributors to grow the committer base. Releases -------- The last jclouds release, 1.9.2, took place on Sat Jan 16 2016.
WHEREAS, the Board of Directors heretofore appointed Andrew Phillips to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrew Phillips from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Ignasi Barrera as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrew Phillips is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Ignasi Barrera be and hereby is appointed to the office of Vice President, Apache jclouds, 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. Special Order 7D, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- Development activity in the last quarter has quietened down a bit and has shifted towards updating existing popular providers and extending recent Google and Microsoft contributions. The user community remains active, with regular questions from a diverse set of users being discussed on the mailing list. An important recent step was the successful integration of the first major change to jclouds core code carried out without the involvement of one of the original core developers. Community --------- Last committer: 2014-07-30 (Andrea Turli) Last PMC member: 2015-09-20 (Zack Shoylev) Community Objectives -------------------- * Identify and complete the remaining major changes to be included in jclouds 2.0 * Complete, extend and harden providers recently graduated from the jclouds labs repo * Encourage and supervise, where necessary, new contributors to grow the committer base Releases -------- jclouds has carried out one release in the past quarter: 1.9.1 was released on 2015-08-06.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. ## Project Status jclouds has not carried out any releases in the last quarter. The community is currently discussing and preparing for the release of 1.9.1. Development activity on Google and Microsoft providers has continued at a strong pace, with multiple providers from both families maturing and being considered for promotion from the jclouds "labs" repository. Existing providers have also been updated to new versions. ## Community Last committer: 2014-07-30 (Andrea Turli). A committer vote has just passed; the PMC is waiting for the candidate's response. Last PMC member: 2014-11-30 (Chris Custine) ## Community Objectives * Finish and promote families of new Google and Microsoft providers * Ensure established providers remain up-to-date and support recent versions of the target APIs * Demonstrate and trial more predictable "graduation paths" with new providers * Broaden portable abstractions Releases -------- No releases in the last quarter. 1.9.1 is currently in preparation and discussion.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. # Project Status jclouds has carried out one successful release (1.9.0) in the last quarter. After a quiet period during the 2014 holiday season, development activity has picked up quite substantially at the beginning of 2015, with both Google and Microsoft contributing resources to the project. The latest release is also the first to make use of an almost fully-automated release process, which will hopefully make it much easier to publish minor versions on a more regular basis. # Community Last committer: 2014-07-30 (Andrea Turli) Last PMC member: 2014-11-30 (Chris Custine) # Community Objectives * Ensure that functionality for the most widely used clouds works and is up-to-date: * Remove API and provider cruft (async APIs, stale providers) * Increase integration test coverage * Broaden portable abstractions * Continue to support the ongoing contributions by new committers * Provide example code demonstrating current best coding and design practices * Create a more predictable "graduation path" for new contributions # Releases * 1.9.0 (2015-03-29)
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- jclouds has carried out one successful release (1.8.1) in the last quarter and is currently discussing the planning of the next major (1.9.0) release. The developer and user community remains active, with a welcome increase in involvement by new contributors. The PMC is trying to streamline the project structure and process for contributions in order to make best possible use of limited core team time and in order to encourage continued interest and involvement from cloud developers. Community --------- Last committer: 2014-07-30 (Andrea Turli) Last PMC member: 2014-11-30 (Chris Custine) As resolved at the October 2014 board meeting, the PMC chair is currently Andrew Phillips. The jclouds PMC would like to express its sincere thanks to Adrian Cole, who recently left the PMC, for his years of work in building jclouds and growing the jclouds community. Community Objectives -------------------- What are the projects main plans and expectations for the community in the next period? * Establish consensus on the core purpose and functionality of the project moving forward and focus on ensuring this continues to be delivered * Establish clear guidance on the expectations around new contributions (technical and in terms of the type of contributions likely to be accepted) * Provide example code demonstrating current best coding and design practices * Create a more predictable "graduation path" for new contributions * Reduce overhead of the project setup to simplify releases and maintenance of core functionality Releases -------- Have there been any releases from the project in the last quarter? * 1.8.1 (2014-10-25)
WHEREAS, the Board of Directors heretofore appointed Andrew Bayer to the office of Vice President, Apache jclouds, and WHEREAS, the Board of Directors is in receipt of the resignation of Andrew Bayer from the office of Vice President, Apache jclouds, and WHEREAS, the Project Management Committee of the Apache jclouds project has chosen by vote to recommend Andrew Phillips as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Andrew Bayer is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache jclouds, and BE IT FURTHER RESOLVED, that Andrew Phillips be and hereby is appointed to the office of Vice President, Apache jclouds, 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 Special Order 7B, Change the Apache jclouds Project Chair, was approved by Unanimous Vote of the directors present.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- jclouds has carried out one successful release (1.8.0) in the last quarter and is in the process of releasing 1.8.1. The developer and user community is active, with sustained activity by the core team. The PMC is still looking to grow the committer base and encourage contributions across the spectrum of supported APIs and providers. Community --------- ''When was the last committer voted in?'' 2014-04-02 (Jeremy Daggett) ''When was the last PMC member added?'' 2013-04-29 (initial composition of the PMC when jclouds entered the incubator) There is regular activity on both the user and dev lists. Responses to questions are generally fast, with multiple community members contributing. The project has resolved to change our PMC chair from Andrew Bayer to Andrew Phillips, and we have notified the board. Community Objectives -------------------- What are the projects main plans and expectations for the community in the next period? * Simplify the process for new contributions * Reduce maintenance overhead of the overall project * Remove outdated and unused APIs and providers * Establish levels of interest and usage for remaining APIs and providers, and identify "champions" where possible Releases -------- Have there been any releases from the project in the last quarter? * 1.8.0 (2014-08-05) The 1.8.1. release is currently in progress.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- jclouds has carried out two successful releases (1.7.2 and 1.7.3) in the last quarter and plans to release 1.7.4. The jclouds website and documentation continues to be expanded. The developer and user community is active, with sustained activity by the core team. The PMC is still looking to grow the committer base and encourage contributions across the spectrum of supported APIs and providers. Community --------- A slightly more detailed look at the project community. It should still be brief, issues to think about include: ''When was the last committer voted in?'' 2014-04-02 (Jeremy Daggett) ''When was the last PMC member added?'' 2013-04-29 (initial composition of the PMC when jclouds entered the incubator) There is regular activity on both the user and dev lists. Responses to questions are generally fast, with multiple community members contributing. Community Objectives -------------------- What are the projects main plans and expectations for the community in the next period? * Simplifying the current multi-repo release procedure to allow for more frequent releases * Determine an approximate release cadence and publish a draft roadmap * Encourage involvement and contributions by vendors of supported providers * Help students complete their two Google Summer of Code projects Releases -------- Have there been any releases from the project in the last quarter? * 1.7.2 (2014-04-16) * 1.7.3 (2014-05-30)
@Brett: Clarify TODO
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- jclouds has carried out one successful release (1.7.1) in the last quarter and is currently in the process of releasing 1.7.2. A lot of work has also gone into overhauling the jclouds website, the new version of which is now live. The developer and user community is active, with an increasing number of submissions from outside the usual committer group, and sustained activity by the core team. The PMC is still looking to grow the committer base and has identified some suitable candidates. Community --------- A slightly more detailed look at the project community. It should still be brief, issues to think about include: ''When was the last committer voted in?'' 2014-04-02 (Jeremy Daggett) ''When was the last PMC member added?'' 2013-04-29 (initial composition of the PMC when jclouds entered the incubator) There is regular activity on both the user and dev lists. Responses to questions are generally fast, with multiple community members contributing. Community Objectives -------------------- What are the projects main plans and expectations for the community in the next period? * Onboarding and mentoring new committers * Encouraging involvement and contributions by vendors of supported providers * Improving the user and new developer experience through revamped documentation * Finishing ongoing architectural changes in preparation for the next major version * Evaluate Google Summer of Code proposals and help students begin their projects Releases -------- Have there been any releases from the project in the last quarter? * 1.7.1 (2014-02-11) * 1.7.2 (ongoing)
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status -------------- jclouds was confirmed as a TLP in October 2013 and has carried out two successful releases (1.6.3 and 1.7.0) since then. The developer and user community is active, with a sustained number of improvements being contributed by users. The PMC has recently discussed how to encourage some of these users to become committers and is actively reaching out to grow the committer base. Community --------- ''When was the last committer voted in?'' 2013-08-08 (Zack Shoylev) ''When was the last PMC member added?'' 2013-04-29 (initial composition of the PMC when jclouds entered the incubator) There is regular activity on both the user and dev lists. Responses to questions are generally fast, with multiple community members contributing. Community Objectives -------------------- What are the projects main plans and expectations for the community in the next period? * Growing the committer base by encouraging regular contributors * Encouraging involvement and contributions by vendors of supported providers * Improving the user and new developer experience through revamped documentation * "Freshening up" the project's image via a new site design * Finishing ongoing architectural changes in preparation for the next major version Releases -------- Have there been any releases from the project in the last quarter? * 1.6.3 (2013-11-30) * 1.7.0 (2013-12-23) * 1.7.1 (2014-02-11)
No report was submitted.
AI: Brett to pursue a report for jclouds
Apache jclouds is a cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status: * Released 1.6.3, first post-graduation release! Issues Needing Board Attention: * None at this time Releases: * 1.6.3 released on November 30, 2013 * 1.7.0 initial RC planned for December 16, 2013 Community: * Last PMC addition: 10/16/13 * Last committer addition: 10/16/13 Security: * No issues reported
Apache jclouds is a cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. Project Status: * Graduated to TLP on 10/16/13! * INFRA-6912 resolved - mailing lists, git repos, website, etc all moved to TLP Issues Needing Board Attention: * None at this time Releases: * Planning underway for 1.6.3 (to come in next week or two) and 1.7.0 (to come by end of year) Community: * Last jclouds PMC addition: 10/16/13 * Last jclouds committer addition: 10/16/13 Security: * No issues reported
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 providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "The Apache jclouds Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache jclouds Project be and hereby is responsible for the creation and maintenance of a software project related to providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API; and be it further RESOLVED, that the office of "Vice President, jclouds" 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 jclouds Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache jclouds 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 jclouds Project: * Adrian Cole (adriancole@apache.org) * Andrew Bayer (abayer@apache.org) * Andrew Gaul (gaul@apache.org) * Andrew Phillips (andrewp@apache.org) * Becca Wood (silkysun@apache.org) * Everett Toews (everett@apache.org) * David Nalley (ke4qqq@apache.org) * Ignasi Barrera (nacx@apache.org) * Ioannis Canellos (iocanel@apache.org) * Matt Stephenson (mattstep@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrew Bayer be and hereby is appointed to the office of Vice President, jclouds, 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 jclouds Project be and hereby is tasked with the migration and rationalization of the Apache Incubator jclouds podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator jclouds podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7A, Establish Apache jclouds Project, was approved by unanimous vote of directors present.
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API jclouds has been incubating since 2013-04-29. Three most important issues to address in the move towards graduation: The jclouds IPMC graduation vote passed on Sep 23rd, 2013. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The jclouds community is looking forward to the next ASF Board meeting and hopes to be confirmed as a TLP. How has the community developed since the last report? jclouds held its first committer vote as an Apache project and is proud to have Zack Shoylev on board! How has the project developed since the last report? Our second incubating release was successful, with no issues related to ASF process or guidelines raised. The remaining trademark and IP issues have been resolved, and changes to the project website to bring it in line with ASF guidelines successfully made. The project also held a successful vote to adopt a set of Bylaws. With those items completed and a new committer on board, the jclouds PPMC proceeded to a graduation vote, which was passed and confirmed by the IMPC. Andrew Bayer was elected as the first project PMC chair and will thus be proposed as Vice President, Apache jclouds. Date of last release: 2013-08-28 (1.6.2-incubating) When were the last committers or PMC members elected? 2013-08-08 (Zack Shoylev as committer) Signed-off-by: [ ](jclouds) Brian McCallister [ ](jclouds) Tom White [ ](jclouds) Henning Schmiedehausen [X](jclouds) David Nalley [ ](jclouds) Jean-Baptiste Onofré [ ](jclouds) Mohammad Nour El-Din [X](jclouds) Olivier Lamy [ ](jclouds) Tomaz Muraus [ ](jclouds) Suresh Marru [ ](jclouds) Carlos Sanchez Shepherd notes:
A cloud agnostic library that enables developers to access a variety of
supported cloud providers using one API
jclouds has been incubating since 2013-04-29.
Three most important issues to address in the move towards graduation:
1. Garnering additional committers and growing our community
2. Now that we've been through a first successful release, ensuring that
subsequent releases progress smoothly and can be handled by multiple
members of the community
3. Agreeing upon a new release schedule and roadmap input gathering strategy
as part of our first major Apache release
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Not at the current time. Feedback on the next release will indicate whether
the work we've done around license headers is sufficient.
How has the community developed since the last report?
No changes in committer list. Still plenty of activity from existing
committers as well as submissions from "new faces" across many of the
different jclouds components.
How has the project developed since the last report?
* A very important milestone: our first Apache release!
* First meetup as an incubator project coming up:
http://www.meetup.com/jclouds/events/126378842/
Date of last release:
Jun 19, 2013 (1.6.1-incubating)
Signed-off-by:
[ ](jclouds) Brian McCallister
[X](jclouds) Tom White
[ ](jclouds) Henning Schmiedehausen
[X](jclouds) David Nalley
[ ](jclouds) Jean-Baptiste Onofré
[ ](jclouds) Mohammad Nour El-Din
[ ](jclouds) Olivier Lamy
[ ](jclouds) Tomaz Muraus
[X](jclouds) Suresh Marru
[ ](jclouds) Carlos Sanchez
Shepherd notes:
adc: I think this podling is good to go as far as activity and community
diversity goes. It's hard to discover what their real status since they've
neglected to keep http://incubator.apache.org/projects/jclouds.html up to
date, but it seems to me that none of the issues listed above are a barrier
to their graduation.
It's troubling to see "THE JCLOUDS LOGO IS TRADEMARK OF JCLOUDS, INC." on
the Apache JClouds incubator home page. Either the trademark should be
assigned to the ASF or it should be removed altogether.
A cloud agnostic library that enables developers to access a variety of
supported cloud providers using one API
jclouds has been incubating since 2013-04-29.
Three most important issues to address in the move towards graduation:
1. We are working on our first release - iterating over issues
currently, making sure we have a proper ASF release ready to go. 2.
Since this is the first ASF project for some of the committers,
it's taking some time for everyone to adjust to the Apache way, but
we're getting there. 3. We need to figure out details on our wiki
and site implementaiton.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
Not particularly - we're definitely edging against some of the boundaries of
what's allowed in an Apache project re: license headers, specifically in
test expectation files, but we're getting there.
How has the community developed since the last report?
The community is roughly the same - no changes in committer list. We have
continued to receive patch submissions and JIRAs from new people, which is,
of course, great.
How has the project developed since the last report?
A lot. =) More specifically:
* We've moved our source to the Apache git repos.
* We've moved to ASF JIRA and mailing lists.
* We've renamed our Maven groupIds to org.apache.jclouds, and are
publishing SNAPSHOTs to repository.apache.org.
* The jclouds.{org,com,net} domain names have been transferred to
Apache, and the jclouds trademark is en route.
* We've been working on RCs for Apache jclouds 1.6.1-incubating, ironing
out the many little gotchas, license issues, etc that are to be
expected when folding such a large, complex existing project into
the ASF. We hope to have a viable final RC presented to the IPMC for
voting within a week or so, assuming our mentors sign off on the
next RC.
Date of last release:
No ASF release yet.
Please check this [X] when you have filled in the report for jclouds.
Signed-off-by:
Brian McCallister: [ ](jclouds)
Tom White: [X](jclouds)
Henning Schmiedehausen: [ ](jclouds)
David Nalley: [X](jclouds)
Jean-Baptiste Onofré: [ ](jclouds)
Mohammad Nour El-Din: [X](jclouds)
Olivier Lamy: [ ](jclouds)
Tomaz Muraus: [ ](jclouds)
Suresh Marru: [X](jclouds)
Carlos Sanchez: [ ](jclouds)
Shepherd notes:
Really? 10 mentors and no report? Is everyone relying on everyone else? (rgardler)
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API jclouds has been incubating since 2013-04-29. Three most important issues to address in the move towards graduation: We are in the initial stages of setup. Our mailing lists have just been created, and we are waiting for infrastructure to migrate git repositories. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? This is our first report. How has the project developed since the last report? This is our first report. Please check this [x] when you have filled in the report for jclouds. Signed-off-by: Brian McCallister: [ ](jclouds) Tom White: [X](jclouds) Henning Schmiedehausen: [ ](jclouds) David Nalley: [x](jclouds) Jean-Baptiste Onofré: [ ](jclouds) Mohammad Nour El-Din: [ ](jclouds) Olivier Lamy: [x](jclouds) Tomaz Muraus: [ ](jclouds) Suresh Marru: [X](jclouds) Carlos Sanchez: [ ](jclouds) Shepherd notes: