ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

just some more grammer, punctuation cleanup.

Browse source
This commit is contained in:
Jason McKerr 2016-02-11 18:42:12 -05:00
parent bab251233a
commit 2d01d43e51
1 changed files with 16 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
ROADMAP.md
View file

@ -2,17 +2,17 @@ Ansible Roadmap
=============
This document is now the location for published Ansible Core roadmaps.
The roadmap will be updated by version. Based on team and community feedback an initial roadmap will be published for a major or minor version (2.0, 2.1) Subminor versions will generally not have roadmaps published.
The roadmap will be updated by version. Based on team and community feedback, an initial roadmap will be published for a major or minor version (2.0, 2.1). Subminor versions will generally not have roadmaps published.
This is the first time we've published this and asked for feedback in exactly this manner. So feedback on the roadmap and the new process is quite welcome. We're aiming for further transparency and better inclusion of both community desires and submissions.
This is the first time we've published this and asked for feedback in this manner. So feedback on the roadmap and the new process is quite welcome. We are aiming for further transparency and better inclusion of both community desires and submissions.
These are our *best guess* roadmaps based on our own experience and based on requests and feedback from the community. There are things that may not make it on due to time constraints, lack of community maintainers, etc. And there may be things we missed, so each roadmap is both published as an idea of what's upcoming in Ansible, but also as a medium for seeking further feedback from the community. Here are the good places for you to submit feedback:
These are our *best guess* roadmaps based on our own experience and based on requests and feedback from the community. There are things that may not make it on due to time constraints, lack of community maintainers, etc. And there may be things we missed, so each roadmap is published both as an idea of what is upcoming in Ansible, and as a medium for seeking further feedback from the community. Here are the good places for you to submit feedback:
* Our google-group ansible-devel
* Our google-group: ansible-devel
* Ansible Fest conferences.
* IRC: Our freenode channel #ansible (this one may have things lost in lots of conversation, so a caution).
2.1 Roadmap, Targeted to End of April
2.1 Roadmap, Targeted for the End of April
==========
## Windows, General
* Figuring out privilege escalation (runas w/ username/password)
@ -22,10 +22,10 @@ These are our *best guess* roadmaps based on our own experience and based on req
## Modules
* Windows
* Finish cleaning up tests and support for post-beta release.
* Finish cleaning up tests and support for post-beta release
* Strict mode cleanup (one module in core)
* Domain user/group management
* finish win\_host and win\_rm in the domain/workgroup modules.
* Finish win\_host and win\_rm in the domain/workgroup modules.
* Close 2 existing PRs (These were deemed insufficient)
* Replicate python module API in PS/C# (deprecate hodgepodge of stuff from module_utils/powershell.ps1)
* Network
@ -62,21 +62,21 @@ These are our *best guess* roadmaps based on our own experience and based on req
* Google (Google/Community)
* Digital Ocean (Community)
* Ziploader:
* Write code to create the zipfile that gets passed across the wire to be run on the remote python.
* Port most of the functionality in module_utils to be usage in ziploader instead.
* Port a few essential modules to use ziploader instead of module-replacer as proof of concept.
* Write code to create the zipfile that gets passed across the wire to be run on the remote python
* Port most of the functionality in module\_utils to be usage in ziploader instead
* Port a few essential modules to use ziploader instead of module-replacer as proof of concept
* New modules will be able to use ziploader. Old modules will need to be ported in future releases (Some modules will not need porting but others will)
* Better testing of modules, caching of modules clientside(Have not yet arrived at an architecture for this that we like. Low priority), better code sharing between ansible/ansible and modules
* Better testing of modules, caching of modules clientside(Have not yet arrived at an architecture for this that we like), better code sharing between ansible/ansible and modules
* ziploader is a helpful building block for: python3 porting(high priority), better code sharing between modules(medium priority)
* ziploader is a good idea before: enabling users to have custom module_utils directories
* Expand module diff support (already in progress in devel)
* Framework done. Need to add to modules, test etc.
* Coordinate with community to update their modules.
* Coordinate with community to update their modules
* Things we are kicking down the road that we said we’d do
* NOT remerging core with ansible/ansible this release cycle.
* NOT remerging core with ansible/ansible this release cycle
* Community stuff
* Define the process/ETA for reviewing PR’s from community.
* Publish better docs and how-tos for submitting code/freatures/fixes.
* Define the process/ETA for reviewing PR’s from community
* Publish better docs and how-tos for submitting code/freatures/fixes