Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Windows Working Group agenda - 2018 #294

Closed
dagwieers opened this issue Jan 11, 2018 · 52 comments
Closed

Windows Working Group agenda - 2018 #294

dagwieers opened this issue Jan 11, 2018 · 52 comments
Assignees
Labels
meeting_agenda windows Windows community

Comments

@dagwieers
Copy link
Contributor

dagwieers commented Jan 11, 2018

Github windows issues Github windows PRs Windows agenda Windows pinboard

This agenda has been migrated to a new location: #420


The Windows Working Group is focused on improving Ansible's management of Windows hosts. The group meets every week on Tuesdays at 20:00 UTC (see ical)

More information related to the Windows Working Group is available at:
https://github.com/ansible/community/wiki/Windows

Feel free to add your questions to this ticket to be discussed during the upcoming meeting.

After being discussed, raised items are being updated, and after a month resolved items are being hidden from view (but remain accessible).

(Migrated from the previous agenda at #195)

@dagwieers
Copy link
Contributor Author

dagwieers commented Jan 11, 2018

New windows modules waiting for review/feedback:

Please review these tickets on a weekly basis (if there was new progress, otherwise add instructions to the owner how to continue).

Once merged, please add to CHANGELOG.md !

@dagwieers
Copy link
Contributor Author

dagwieers commented Jan 11, 2018

@dagwieers

This comment has been minimized.

@dagwieers

This comment has been minimized.

@dagwieers
Copy link
Contributor Author

I would like to revisit ansible/ansible#29170 since the Unix python modules are doing this all over the place, without any framework.

@jborean93

This comment has been minimized.

@jhawkesworth

This comment has been minimized.

@jborean93

This comment has been minimized.

@dagwieers

This comment has been minimized.

@jhawkesworth

This comment has been minimized.

@jhawkesworth

This comment has been minimized.

@jborean93

This comment has been minimized.

@jhawkesworth jhawkesworth changed the title Windows Working Group agenda - Jan-Mar 2018 Windows Working Group agenda - Jan-May 2018 Apr 24, 2018
@varunchopra

This comment has been minimized.

@jborean93

This comment has been minimized.

@varunchopra

This comment has been minimized.

@gregdek

This comment has been minimized.

@jborean93

This comment has been minimized.

@ksubileau

This comment has been minimized.

@gundalow

This comment has been minimized.

@varunchopra

This comment has been minimized.

@jborean93

This comment has been minimized.

@mattclay

This comment has been minimized.

@jborean93

This comment has been minimized.

@jborean93

This comment has been minimized.

@varunchopra

This comment has been minimized.

@jborean93

This comment has been minimized.

@jborean93

This comment has been minimized.

@dagwieers

This comment has been minimized.

@jborean93

This comment has been minimized.

@dagwieers

This comment has been minimized.

@varunchopra

This comment has been minimized.

@dagwieers
Copy link
Contributor Author

We still have a backlog of known issues listed at our progress tacker and I was wondering what we wanted to do with this.

  • Maybe first evaluate if the current list is still correct.
  • Can we ask the original maintainer to fix some of these issues ?
  • Should we somehow add information to the module documentation what the limitations are ?
    • E.g. This module is not idempotent, this module has not integration tests, this module is unmaintained ?
    • And actively ask for contributors to help fix known issues ?
  • Can we do some effort to clean this up ourselves ?
    • Or create easy-fixes in the issue-tracker.

@dagwieers
Copy link
Contributor Author

The current Windows community plan lists various ideas and functionality, some of which we have implemented (and even have removed since).

In order to prepare the new Ansible v2.8 Windows roadmap, it would be nice if we could collectively think about important issues we still have with Ansible/Windows integration. We've come a long way, and a lot of improvements are in the pipeline, but each of us know of issues that are still prevalent and require work/notes.

This could include modules/lookup-plugins/filters that would be of great value. So feel free to discuss on IRC and add them to the Wiki.

@ksubileau

This comment has been minimized.

@it-praktyk

This comment has been minimized.

@dagwieers

This comment has been minimized.

@jhawkesworth
Copy link
Contributor

jhawkesworth commented Dec 4, 2018

Of the 93 windows modules 33 have now been converted to Ansible.Basic. (AnsibleBasic is a new implementation of common functions/CmdLets available for use within Windows ansible modules)
Are we confident enough with it now to have a push at converting everything over?

Edit: discussed 4-Dec-2018. Downsides would be slight performance hit which is not yet mitigated by other planned changes. Would likely want to wait until we are confident the 2.8 codebase is being used before moving the likely most-frequently-used modules such as win_file, win_copy.

Consensus seemed to be that lesser used windows modules should be ok to move, provided they have tests. If modules don't have tests yet (and can be tested), then we should add tests first before attempting to move to AnsibleBasic.

@nitzmahone
Copy link
Member

Working group meetings for Dec 18, Dec 25, Jan 1 are cancelled due to holidays

See everyone in the new year!

@dagwieers
Copy link
Contributor Author

dagwieers commented Dec 28, 2018


This agenda has been migrated to a new location: #420


@ansible ansible locked as resolved and limited conversation to collaborators Dec 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
meeting_agenda windows Windows community
Projects
None yet
Development

No branches or pull requests

10 participants