Name: community
Owner: Ansible
Description: This repository is for management of all Ansible community related initiatives.
Created: 2016-02-22 19:35:08.0
Updated: 2018-01-13 17:03:59.0
Pushed: 2018-01-11 16:13:04.0
Homepage:
null
Size: 187
Language: Makefile
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Email | Most Recent Commit | # Commits |
|---|
README
Ansible Community Working Group
This repository is for management of all Ansible community related initiatives.
What We Do:
We help to support and grow Ansible's community of contributors in their efforts to improve Ansible code, content, outreach, and user and contributor experiences.
This repository serves as a space for the Ansible Community Working Group to manage tools used by the Ansible community, monitor progress on new initiatives, and handle requests for resources or help by various Working Groups in the wider Ansible community.
Our Goals:
- Encourage transparency, collaboration, and accountability through tooling and lightweight project tracking and/or management
- Provide guidance and advice to other working groups in the Ansible community
- Facilitate the creation of new initiatives and Working Groups
- Do all of this by KEEPING THINGS SIMPLE (just like Ansible!).
Infrastructure and processes we build and/or support:
- Ansibullbot: Automation (or aspiring automation) of GitHub pull request processing for ansible/ansible, ansible/ansible-modules-core, and ansible/ansible-modules-extras.
- Meetings: IRC meeting-related infrastructure, including the meeting bot and space for logs; organization of Ansible Contributor Summits.
Groups we help:
Communication:
Find us on Freenode:
- IRC: #ansible - General Discussion
- IRC: #ansible-devel - Channel for discussing pull-requests and contributions only
- IRC: #ansible-notice - Automated messages from various services related to Ansible
- IRC: #ansible-meeting - Ansible community meeting channel. Meeting Schedule and logs
- IRC: #ansible-aws - Channel for discussing AWS and Ansible related things
- IRC: #ansible-azure - Channel for discussing Azure and Ansible related things
- IRC: #ansible-community - Channel for discussing Ansible Community related things
- IRC: #ansible-container - Channel for discussing Containers and Ansible related things
- IRC: #ansible-jboss - Channel for discussing JBoss and Ansible related things
- IRC: #ansible-network - Channel for discussing Network and Ansible related things
- IRC: #ansible-news - Channel for discussing Ansible Communication & News related things
- IRC: #ansible-vmware - Channel for discussing VMware and Ansible related things
- IRC: #ansible-windows - Channel for discussing Windows and Ansible related things
- IRC: #ansible-es - Channel for Spanish speaking Ansible community
- IRC: #ansible-fr - Channel for French speaking Ansible community
- Mailing list
- GitHub issues
What We're Working On:
- New tasks and in-progress work are tracked via GitHub issues (link) in this repository (and in some cases, have accompanying pull requests).
- Backlog and progress can also be seen on our Waffleboard, which provides a kanban-style visualization of the GitHub issues and PRs.
- Additional work items relating to enabling the Ansible community that are owned by Ansible's Community Team (@gregdek & @robynbergeron that were generated outside of a created GitHub issues (email requests, or things we're just doing) are tracked in this repository in the spirit of transparency.
New Issues:
Requests for resources, tools, or help relating to the tools and communication spaces used by the Ansible Community should be added as an issue in GitHub.
If you're not sure where to get started with a new idea relating to growing and
supporting the Ansible Community, ask in an issue.
Pull requests for content or code that will go into the Ansible/Community space
are welcome.
I'd like to help:
YOU ARE ADMIRA-BULL!
If you'd like to help the Ansible Community Working Group, read CONTRIBUTING.md. Existing issues can be seen in our GitHub issues list.
If you'd like to help improve Ansible code or modules, please see .
If you're interested in contributing to the efforts of other Ansible Working Groups, please refer to their contribution guidelines in their repositories.
If you have an idea for a new initiative or team, read on!
I'd like to start a new initiative or team:
YOU ARE INCREDI-BULL.
Someday, we'll probably have more structure around this; for now, we're keeping it simple.
The Ansible Working Group wants you to be able to start doing the things you want to do, so here are a few guidelines:
- Look to see if anyone else has the same idea!
- If you have an idea for the Ansible code itself, this is not the right place to make it happen. Please see the documentation for current and prospective developers.
- If you have an idea THAT YOU WANT TO WORK ON that depends upon or is related to Ansible code, create an issue in this repository, and start a discussion on the ansible-devel mailing list. Encourage others who might be interested in helping to indicate their interest in the GitHub issue.
- If you have an idea THAT YOU WANT TO WORK ON that does not relate to Ansible code, such as content, contributor enablement, outreach, or anything else you can imagine, please open an issue in this repository.
- If you have an idea that you CAN'T WORK ON, create an issue in this repository – but please remember that without a willing contributor wanting to do the work, many suggestions do not turn into actual results.
- And remember: Right now, we have little process around “how to do this” – so being transparent is the best way avoid duplication of effort, and the best way to find people to help you out. “Release early, release often,” even if it's not code!
