With much thanks, welcome new cloud module lieutant/czar/santa-helpers

Hi all,

(Feel like I’ve sent this note but apparently I have not)

Good news! I’ve recently added a few folks with commit access to the ansible-modules-core and ansible-modules-extras repos.

These are:

Eric Johnson - Google - @erjohnso on github

Matt Martz - Rackspace - @sivel
Monty Taylor - OpenStack (Monty hails from HP) - @emonty

The goal here is to allow them to run point on merging many things related to these topics, and also we’ve talked about doing some renames (with aliases) of these modules, as I’ve alluded to in another thread.

The ultimate goal is to get these modules to move forward using the smartest possible folks that know the most about the given services, and allowing us to focus more on everything else including the core application/language, getting in changes to new PRs, and stuff like that.

To be honest, we’ve already been doing this for a while, as I’ve long taken the lead from Matt, Eric, and more recently Monty for “should I merge this?” and they have been surpremely helpful.

There may also be replacement versions of some modules if we decide certain module signatures need to be improved, which we’ll do by keeping older versions around for some time.

From time to time we may also decide to grant folks commit access for specific modules, if you are so interested, we’re looking for a strong history of contribution coupled with a vested interest in the modules in question.

For instance, if folks work for say, FooCorp and want to maintain the FooCorp module, the new module structure makes this quite possible. This isn’t just limited to cloud modules either.

It’s not always the case that someone needs to work for a vendor, though we would be looking for a strong history of contribution to the existing modules in those cases. In either case, someone needs to have a good understanding for how Ansible ticks and should be using those modules regularly.

In any case, thanks a ton to Eric, Matt, and Monty. We’ll continue to use this list - and github - just like before for discussion on all of those modules and their future (as well as announcement about changes or upgrades), so nothing really changes, just contribution on these projects - and velocity in these areas, goes way up.

(For questions, contact me off list!)

Hi all,

(Feel like I’ve sent this note but apparently I have not)

Good news! I’ve recently added a few folks with commit access to the ansible-modules-core and ansible-modules-extras repos.

These are:

Eric Johnson - Google - @erjohnso on github

Matt Martz - Rackspace - @sivel
Monty Taylor - OpenStack (Monty hails from HP) - @emonty

The goal here is to allow them to run point on merging many things related to these topics, and also we’ve talked about doing some renames (with aliases) of these modules, as I’ve alluded to in another thread.

The ultimate goal is to get these modules to move forward using the smartest possible folks that know the most about the given services, and allowing us to focus more on everything else including the core application/language, getting in changes to new PRs, and stuff like that.

To be honest, we’ve already been doing this for a while, as I’ve long taken the lead from Matt, Eric, and more recently Monty for “should I merge this?” and they have been surpremely helpful.

There may also be replacement versions of some modules if we decide certain module signatures need to be improved, which we’ll do by keeping older versions around for some time.

From time to time we may also decide to grant folks commit access for specific modules, if you are so interested, we’re looking for a strong history of contribution coupled with a vested interest in the modules in question.

For instance, if folks work for say, FooCorp and want to maintain the FooCorp module, the new module structure makes this quite possible. This isn’t just limited to cloud modules either.

I work for DigitalOcean and would be willing to maintain the digital_ocean module.

-s

That would be excellent. I’ll pass along some info in a later email!