# 2.2 Roadmap is Posted for Feedback **URL:** \ **Category:** Ansible Developer\ **Created:** [June 3, 2016, 5:52pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663 "2016-06-03T17:52:40Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![jmckerr](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jmckerr](https://forum.ansible.com/u/jmckerr)\ **Post date:** [June 3, 2016, 5:52pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/1 "2016-06-03T17:52:40Z")
Hello All, Now that 2.1 is out, we’re starting to work on what’s next in Ansible. We’ve done a couple of first passes on what we (Ansible/Red Hat) think we should propose for the next release, but we need your feedback. The new Roadmap is linked below. Please let us know what we’ve missed or mistaken. We’ll review the Roadmap in one of the Ansible Community meetings in the next week in order to get feedback from the community. We’ve reorganized the Roadmap docs a little. There’s now a document ROADMAP.rst at the root of the Ansible project on Github that has links to current and past roadmaps. [https://github.com/ansible/ansible/blob/devel/ROADMAP.rst](https://github.com/ansible/ansible/blob/devel/ROADMAP.rst) Regards, Jason McKerr Ansible by Red Hat. ---
**Author:** ![willthames](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@willthames](https://forum.ansible.com/u/willthames)\ **Post date:** [June 6, 2016, 2:49am UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/2 "2016-06-06T02:49:34Z")
I would like more information on what is happening with roles - particularly with all the delay to [https://github.com/ansible/proposals/issues/7](https://github.com/ansible/proposals/issues/7) while the details about what’s happening with roles is being fleshed out. Any news on open sourcing Galaxy? Will ---
**Author:** ![christophercundill](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@christophercundill](https://forum.ansible.com/u/christophercundill)\ **Post date:** [June 6, 2016, 10:04am UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/3 "2016-06-06T10:04:04Z")
+1 on your proposal Will. Jason, can I confirm that the PR changing Ansible Galaxy CLI to connect to the API server lazily ([https://github.com/ansible/ansible/pull/15632](https://github.com/ansible/ansible/pull/15632)) will be part of the 2.2 release? Thanks! -Chris C. ---
**Author:** ![Timothy\_Appnel1](https://avatars.discourse-cdn.com/v4/letter/t/278dde/32.png) [@Timothy\_Appnel1](https://forum.ansible.com/u/Timothy_Appnel1)\ **Post date:** [June 7, 2016, 4:57pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/4 "2016-06-07T16:57:38Z")
No need to verify. It was added into v2.1. (Read to the bottom of the comments.) ---
**Author:** ![christophercundill](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@christophercundill](https://forum.ansible.com/u/christophercundill)\ **Post date:** [June 7, 2016, 6:35pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/5 "2016-06-07T18:35:47Z")
Ah, even better - thanks! ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [June 13, 2016, 10:52pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/6 "2016-06-13T22:52:56Z")
Hi, I appreciate there’s a lot in there already but if there’s any room it would be great to at least work out how we want to document all of the different pluggable bits of Ansible - right now things like callback plugins don’t really have a pattern for how they are documented, I believe. Personally I’d like a way to add documentation to playbooks too but perhaps that’s a discussion for another day. Jon ---
**Author:** ![Filipe\_Felisbino](https://avatars.discourse-cdn.com/v4/letter/f/ee7513/32.png) [@Filipe\_Felisbino](https://forum.ansible.com/u/Filipe_Felisbino)\ **Post date:** [June 16, 2016, 12:05pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/7 "2016-06-16T12:05:44Z")
I like the Role Revamp proposal. It will make easier to express relationship between roles for more than just dependencies. ---
**Author:** ![alexk4work](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@alexk4work](https://forum.ansible.com/u/alexk4work)\ **Post date:** [June 16, 2016, 1:50pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/8 "2016-06-16T13:50:10Z")
Any docker bug fixes planned? It’s almost broken for now (especially docker/docker\_container/docker\_image modules). ---
**Author:** ![Hajo\_Kliemeck](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@Hajo\_Kliemeck](https://forum.ansible.com/u/Hajo_Kliemeck)\ **Post date:** [June 19, 2016, 8:29pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/9 "2016-06-19T20:29:28Z")
is it possible to include [https://groups.google.com/forum/#!topic/ansible-devel/--HRQQ9vo8A](https://groups.google.com/forum/#!topic/ansible-devel/--HRQQ9vo8A) as well? it would support the idea of multiple roles working together (as proposed by will) Hajo ---
**Author:** ![Ton\_Kersten](https://avatars.discourse-cdn.com/v4/letter/t/65b543/32.png) [@Ton\_Kersten](https://forum.ansible.com/u/Ton_Kersten)\ **Post date:** [June 21, 2016, 6:26am UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/10 "2016-06-21T06:26:57Z")
I was wondering if it isn’t time to define a standard of documenting playbooks and roles? I discussed this about 2.5-3 years ago with Michael and he didn’t care for that, at that time. But at this moment in time everybody is creating a way to embed documentation in playbooks and roles. And everybody has their own way, which could break things like the Galaxy. I think we should create a standard. And my proposol would be to have something like a Python Docstring, containing reStructuredText that can be processed with Sphinx. ---
**Author:** ![Serge\_van\_Ginderacht](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@Serge\_van\_Ginderacht](https://forum.ansible.com/u/Serge_van_Ginderacht)\ **Post date:** [June 21, 2016, 7:18am UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/11 "2016-06-21T07:18:26Z")
How about not only documenting, but also having some meta information available that defines input and output variables? (the recently merged handler notifications could be part of that) ---
**Author:** ![Ton\_Kersten](https://avatars.discourse-cdn.com/v4/letter/t/65b543/32.png) [@Ton\_Kersten](https://forum.ansible.com/u/Ton_Kersten)\ **Post date:** [June 21, 2016, 7:21am UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/12 "2016-06-21T07:21:13Z")
Yes!! Totally agree. That way we get a standard for everything in a role and in playbooks. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 21, 2016, 1:22pm UTC](https://forum.ansible.com/t/2-2-roadmap-is-posted-for-feedback/21663/13 "2016-06-21T13:22:24Z")
[http://github.com/ansible/proposals](http://github.com/ansible/proposals) once we have proposals, we can consider adding it to a roadmap.