oVirt community pinboard

[dagwieers]

We could collectively benefit from forming a Working Group related to oVirt integration. We have quite some contributors on Github and users on IRC that are interested in improving this integration.

So this issue is a call for potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:

• test, review and add shipits to existing oVirt PRs
• work collectively on the oVirt roadmap
• provide a single-point-of-contact for interested oVirt contributors
• collaborate on an oVirt-specific Wiki
• have a $team_ovirt in BOTMETA.yml for auto-notifying team members
• implement auto-labeling oVirt issues and PRs

[dagwieers]

cc @dverhelst @sgordon46 @mriedelumab @joshainglis @karmab @nijinashok @dagwieers @machacekondra @tareqalayan @maorlipchuk @bennyz @KKoukiou @danielerez @zuc @lukas-bednar @mykaul @remixtj @dominikholler @tremble @akashihi @snecklifter @pmargara @tiraboschi @mwperina @sgratch @ThomasADavis @mkrish004c @cclauss @leongold @ekultails @mnecas @frangdlt @nasx @petr-balogh @rhodain @imjoey @bverschueren @arielb2 @erav @funixz @vagnerfarias
cc @resmo

[dagwieers]

If you want to actively lead or are interested to be part of this Working Group, add your name to the Wiki page ! If we have a large enough group, we can start our own oVirt Working Group.

I started labeling all the oVirt related issues and PRs so we can more easily track them:

• https://github.com/ansible/ansible/pulls?q=is:pr+is:open+label:ovirt (9 open PRs)
• https://github.com/ansible/ansible/issues?q=is:issue+is:open+label:ovirt (9 open issues)

PS If you no longer want to receive any messages from this pinboard, feel free to unsubscribe from this issue ticket.