Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
Dag Wieers edited this page Jan 29, 2019 · 14 revisions

Working Group Roles

While this new Ansible community thing is unfolding and we are finding better ways to collaborate, let's discuss what roles we have and what your role really means.

Lead

One or more leads ensure that the Working Group stays active on working on open issues, open PRs and new functionality or ideas. This is not exclusive to WG leadership, any member of the Working Group can engage others to help out reviewing or commenting on open issues and PRs, but it is the WG leadership that should be aware of keeping the fire burning while at the same time not overexposing members with too much calls for action.

The WG lead is the first person to contact for questions related to the WG or WG membership. In case of unclarity or issues touching other domains the WG lead will raise those issues to the Community WG or the core team.

The lead is added in BOTMETA.yml as a maintainer and has shipit rights. She will be notified of related issues and PRs.

Reviewer

A reviewer is someone interested in helping improve new contributions and supporting others with issues. A reviewer will review issues and PRs regularly, especially when asked by contributors or WG leadership. A reviewer usually has access to infrastructure to run integration tests against, but that is not always necessary for reviewing PR.

If a reviewer does review a PR without the ability to test running code, he should say so when approving a PR (as to ensure that there's no confusion whether the code was actually tested). We encourage reviewers to only add shipits when they have both reviewed the code, as well as tested the code.

A reviewer is added in BOTMETA.yml as a maintainer and has shipit rights. She will be notified of related issues and PRs.

Member

A member is interested to follow and engage into discussions, but has limited time or experience to review code.

A member is added in BOTMETA.yml as being notified for related issues/PRs, but does not have shipit rights.

Pinboard subscriber

Anyone can subscribe to a community pinboard to stay informed on general discussions or news items on the pinboard. They are not added as members on the Working Group as such and are largely anonymous unless they engage in a discussion on the pinboard.

(ARchived) Working groups

Working groups are now in the Ansible forum

Ansible project:
Community, Contributor Experience, Docs, News, Outreach, RelEng, Testing

Cloud:
AWS, Azure, CloudStack, Container, DigitalOcean, Docker, hcloud, Kubernetes, Linode, OpenStack, oVirt, Virt, VMware

Networking:
ACI, AVI, F5, Meraki, Network, NXOS

Ansible Developer Tools:
Ansible-developer-tools

Software:
Crypto, Foreman, GDrive, GitLab, Grafana, IPA, JBoss, MongoDB, MySQL, PostgreSQL, RabbitMQ, Zabbix

System:
AIX, BSD, HP-UX, macOS, Remote Management, Solaris, Windows

Security:
Security-Automation, Lockdown

Tooling:
AWX, Galaxy, Molecule

Communities

Modules:
unarchive, xml

Plugins:
httpapi

Wiki

Roles, Communication, Reviewing, Checklist, TODO

Clone this wiki locally