# Ansible Community Steering Committee
###### tags: `steering committee`

## Mission:

The Steering Committee helps decide the technical direction of the Ansible Upstream project and is also responsible for avowal of new proposals (feature idea, new policy in collection world), new collection requests, empower contributors, maintainers & reviewers and other technical aspects regarding inclusion and packaging.

## Responsibilities of Steering Committee Members:

The members in the committee handle the below:
* Design policy and procedure for the collection world.
* Review things (collections for now) for compliance with the policies.
* Help create our deliverables (community.general, community.network, the ansible-tarball, docs website).
* Ballot on approval changes to policy and new proposals.
* Identify and train individuals from the community who are interested in contributing to Ansible.

## Members:

1. Toshio Kuratomi (abadger1999)
1. Felix Fontein (felixfontein)
1. Tadej Borovšak (tadeboro)
1. James Cassell (cyberpear)
1. John Barker (gundalow)
1. Andrew Klychkov (andersson007_)
1. Alicia Cozine (acozine)
1. Sorin Sbarnea (zbr)
1. Jill Rouleau (jillr)
1. Brad Thornton (cidrblock)
1. Dylan Silva (thaumos)

*Key: Full name (IRC Nickname)*

- Currently, all the Steering Committee members are selected based on their active contribution to the Ansible Project.
- In future, the selection process will be based on the election model through community.

## New Policy/Proposals & Inclusion Requests:

Requests regarding new collection inclusion requests should be submitted to this [GitHub discussion](https://github.com/ansible-collections/ansible-inclusion/discussions/new) and requests regarding new policy/proposals should be submitted through a new pull request to [ansible-collections/overview](https://github.com/ansible-collections/overview) GitHub repo.

Also, we earlier used a [Community Working Group Meeting Agenda](https://github.com/ansible/community/issues/539) to track agenda topics that needed to be discussed in the weekly Ansible Community IRC meetings. Now, to categorize each topic separately we’ve created a new GitHub repo “[community-topics](https://github.com/ansible-community/community-topics)”. If you want to discuss an idea, improvements or submitted new Policy/Proposals & New Collection Inclusion Requests then create a [new issue](https://github.com/ansible-community/community-topics/issues/new) in the [repo](https://github.com/ansible-community/community-topics) as a topic, and it’ll be discussed publicly in the weekly IRC meeting. After every meeting, the meeting minutes/summaries and meeting logs will be posted to the [original issue](https://github.com/ansible/community/issues/539).

If you cannot join the meeting or from another time zone then you can directly use GitHub Discussions feature to discuss your new proposals/collection inclusion requests and the steering committee will discuss the final conclusions during the weekly IRC meeting and then will vote on them.

## Meetings:

Ansible Community meeting happens on a weekly basis on #ansible-community IRC channel every Wednesday [at 18:00 UTC](https://raw.githubusercontent.com/ansible/community/main/meetings/ical/community.ics).

### Agenda

You can find the Ansible Community Meeting agenda at [Community Working Group Meeting Agenda.](https://github.com/ansible/community/issues/539)

### Minutes of Meeting

Ansible Community weekly meeting minutes can be found at the [fedora meetbot site](https://meetbot.fedoraproject.org/sresults/?group_id=ansible-community&type=channel) and the same will be posted to [Ansible Devel Mailing List](https://groups.google.com/g/ansible-devel) after every meeting.

## Mailing List:

Any important announcements regarding Ansible Community Project will be posted to `[e-mail]`.