jclouds development has slowed down, in part due to maturity of the code base but also due to shifting priorities of the original maintainers. Without dedicated volunteers, we are having trouble maintaining the project as we have previously. I would like to solicit ideas on how we can reduce the maintenance burden. Some ideas:
* spin out components, similar to what we did with jclouds-karaf previously * release from master and stop maintaining release branches, e.g., 2.2.x * reduce the Java compatibility matrix, e.g., Java 8 and newer only * upgrade key dependencies, e.g., BouncyCastle, Guava, to avoid dependency headaches * graduate more providers in labs -- Andrew Gaul http://gaul.org/
