Hi All,
The "cloud market" when Apache Libcloud was conceived in 2010 is very
different to how it looks today, some trends we are seeing
1- IaaS (our compute API) is one of many features in public clouds. Amazon,
Azure and GCP have 100's of individual services now [1]. Text-to-speech,
functions,
Hi Anthony,
I used to be an active contributor to libcloud, and am technically still a
committer although I don’t think I’ve been active at all since you stepped into
the fold. I just wanted to start by saying thanks for your hard work!
I fully support your proposal. It will take a while to be
+ a million to John, and I’m actually in the same boat. I stepped away
due to a conflict, though I technically remain on the PMC (it seems).
Every time I’ve wanted to come back the current design stops me, and
that’s not speaking negatively, just that I have a difficult time
approaching mod
I also want to reiterate that I'm not bashing on the current design. It
absolutely serves a purpose, has many happy users and delivers on many of
the goals initially set out.
But, things have changed hugely in 5 years.
--
John >>
"primitives for waiting, paginating, retrying, etc" < absolutely.
Thanks Anthony! We do need this kind of discussion.
So libcloud right now is an healthy project that continues to improve,
mostly with external contributions. Which is nice! However it's difficult
for me to keep up with those pull requests, so for any other developments
we would need more reviewer
Wow, that's a serious thread! I hope you're coming to PyCon Quentin. I'll
be there and hard to miss (I carry a 6ft "Python Staff")
I happened to bump into both Cory Benfield and Kenneth and picked their
brains on some of the thinking for requests 3.0.
The design in my email is going to take a yea
