On 05/14/2015 12:58 PM, Everett Toews wrote:
Top posting to make it official...Michael McCune (elmiko) is an API Working
Group core!
Cheers,
Everett
thanks everybody!
=)
mike
__
OpenStack Development Mailing List (not
Top posting to make it official...Michael McCune (elmiko) is an API Working
Group core!
Cheers,
Everett
On May 11, 2015, at 8:57 PM, Ryan Brown wrote:
> On 05/11/2015 04:18 PM, Everett Toews wrote:
>> I would like to propose Michael McCune (elmiko) as an API Working Group core.
>
> Not core,
On 05/11/2015 04:18 PM, Everett Toews wrote:
> I would like to propose Michael McCune (elmiko) as an API Working Group core.
Not core, but +1 from me!
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/11/2015 03:18 PM, Everett Toews wrote:
> I would like to propose Michael McCune (elmiko) as an API Working
> Group core.
I'm not core, but I have been impressed by his work. +1 from me.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Vers
On Mon, 11 May 2015, Everett Toews wrote:
I would like to propose Michael McCune (elmiko) as an API Working Group core.
+1
a fine idea
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
O
Hi,
I'm not an API WG core or active participant (unfortunately), but from
Sahara in-project API discussions Michael is very active and he's now
driving our next API design as well as being Sahara liaison in API WG.
Thanks.
On Mon, May 11, 2015 at 11:18 PM, Everett Toews wrote:
> I would like
+1 from me.
On 05/11/2015 04:18 PM, Everett Toews wrote:
I would like to propose Michael McCune (elmiko) as an API Working Group core.
Among Michael’s many fine qualities:
* Active from the start
* Highly available
* Very knowledgable about APIs
* Committed the guideline template
I would like to propose Michael McCune (elmiko) as an API Working Group core.
Among Michael’s many fine qualities:
* Active from the start
* Highly available
* Very knowledgable about APIs
* Committed the guideline template
* Working on moving the API Guidelines wiki page
* Lots of s
