Get ansible-xml part of ansible core about ansible-xml

[dagwieers]

The xml module is upstream now (and ships with Ansible v2.4).

Anyone interested in helping to maintain this module upstream is welcome. We need a few people in order to be able to work independently on this module (with the existing review-process you need 2 shipits from maintainers to get stuff merged). Ideally we have about 5 to 6 people maintaining it. So please speak up !

Please close this issue.

[cmprescott]

@tbielawa thanks! Works been crazy lately, but I'll try to make time for this. It's long long overdue. I don't want to answer questions how to install it forever...

[ssbarnea]

I do see this as a meta-ticket, there are quite a few bugs that do need to be fixed in order to do this.

I think it would be wise if we specify them here in order to see what blocks this ticket, it would be much easier to move things into the right direction.

@cmprescott you know the PR much better than any of us, could you link the issues that were not addressed yet, maybe some of us could fix them.

[tbielawa]

👍

[ssbarnea]

Here is the Feature request made on Ansible ansible/ansible#16147 -- add your feedback and/or up-thumbs there.

[tbielawa]

nudge

[cmprescott]

1. Need to incorporate feedback from ansible/ansible-modules-core#4122
2. Need to resubmit to ansible-module-extras
3. Opening individual issues for some of the comments.

[liquidat]

Any news on this? I would like to help with the submission of the module upstream. Or if you do not want to pursue that anymore, I would like to for it here on Github and push it upstream, if you would be ok with it.

[dagwieers]

TBH I think we should get this merged ASAP in Ansible Core now that v2.3 has been branched. And then work on having integration tests, additional documentation and closing the existing PRs upstream to get this finished for v2.4 (which gives us 4 to 5 months probably).

Using the upstream integration tests will speed up fixing issues (without breaking existing use-cases) and doing this upstream will also help to find new testers and contributors as the module will be listed in the modules index.

[ssbarnea]

I don't need this anymore for my job but I will help with getting the PR reviewed and merged by Ansible team. Indeed timing is essential here, we don't want to lose that window.

BTW, I hope there are no licensing issues, as these to have the bad habit of ruining things.

[liquidat]

Are there any possible license issues you have on your mind?

[ksylvan]

Any news on this?

[ksylvan]

Looks like this is proceeding nicely. This is the latest work, correct? ansible/ansible#25323

[dagwieers]

Yes. So we prefer not to have any new PRs on this repository before this is merged.
Once merged I would like to move all feature requests and (valid) bug reports to the ansible/ansible repository. This will take some time to validate and possible fix the reported issues.

Still looking for people willing to help maintain the xml module upstream.