Great thanks for the pointer. Even more thanks to Zack who took the time to summarize that thread (if only more folks did that in other projects I work on, including me!)
Zacks summary, for the purposes of the archives is: Currently, most of us agree that the following criteria should be met, at a minimum, before an API is promoted to jclouds/jclouds: - It is being maintained - It has an abstraction - Code is up-to-date (tests, style, best practices) This all seems sensible. I don't want to start that thread again but I would point out that the first criteria (it is being maintained) might be true on promotion to core but no longer be true in x months time. Not a problem today, but one day it is possible there will need to be a process for retirement from core too. For the Azure support we'll focus on getting it into core though :-) Looking at other modules that are in core I see there isn't a consistent level of support for compute and storage (our current area of focus). Is there a minimum bar at this point? Perhaps a test suite? No problem if this is still being defined, we can use the Azure support as a use case for defining that minimum bar if it is appropriate. Ross -----Original Message----- From: Andrew Phillips [mailto:aphill...@qrmedia.com] Sent: Wednesday, February 4, 2015 4:31 PM To: dev@jclouds.apache.org Subject: RE: Contributing Azure support Hi Ross > Thanks for the pointer John. Why is Blob in core and Compute in > Labs? What is the criteria for leaving labs? See http://markmail.org/thread/zvsytdvzfeg4w2zi. In short, it's still an ongoing discussion, but support for one of the abstraction layers (which is true for both Azure BlobStore and Compute) is likely to be one of the key ones. Great to see interest from your side in contributing! Regards ap
