Committers Guidelines (for people with commit rights to Ansible on GitHub)¶

Features, High Level Design, and Roadmap¶

As a core team member, you are an integral part of the team that develops the roadmap. Please be engaged, and push for the features and fixes that you want to see. Also keep in mind that Red Hat, as a company, will commit to certain features, fixes, APIs, etc. for various releases. Red Hat, the company, and the Ansible team must get these committed features (etc.) completed and released as scheduled. Obligations to users, the community, and customers must come first. Because of these commitments, a feature you want to develop yourself may not get into a release if it impacts a lot of other parts within Ansible.

Any other new features and changes to high level design should go through the proposal process (TBD), to ensure the community and core team have had a chance to review the idea and approve it. The core team has sole responsibility for merging new features based on proposals.

Our Workflow on GitHub¶

As a committer, you may already know this, but our workflow forms a lot of our team policies. Please ensure you’re aware of the following workflow steps:

• Fork the repository upon which you want to do some work to your own personal repository
• Work on the specific branch upon which you need to commit
• Create a Pull Request back to the Ansible repository and tag the people you would like to review; assign someone as the primary “owner” of your request
• Adjust code as necessary based on the Comments provided
• Ask someone on the Core Team to do a final review and merge

Roles on Core¶

• Core Committers: Fine to do PRs for most things, but we should have a timebox. Hanging PRs may merge on the judgement of these devs.
• Module Owners: Module Owners own specific modules and have indirect commit access via the current module PR mechanisms.

General Rules¶

Individuals with direct commit access to ansible/ansible are entrusted with powers that allow them to do a broad variety of things–probably more than we can write down. Rather than rules, treat these as general guidelines, individuals with this power are expected to use their best judgement.

• Don’t
  • Commit directly.
  • Merge your own PRs. Someone else should have a chance to review and approve the PR merge. If you are a Core Committer, you have a small amount of leeway here for very minor changes.
  • Forget about alternate environments. Consider the alternatives–yes, people have bad environments, but they are the ones who need us the most.
  • Drag your community team members down. Always discuss the technical merits, but you should never address the person’s limitations (you can later go for beers and call them idiots, but not in IRC/Github/etc.).
  • Forget about the maintenance burden. Some things are really cool to have, but they might not be worth shoehorning in if the maintenance burden is too great.
  • Break playbooks. Always keep backwards compatibility in mind.
  • Forget to keep it simple. Complexity breeds all kinds of problems.
• Do
  • Squash, avoid merges whenever possible, use github’s squash commits or cherry pick if needed (bisect thanks you).
  • Be active. Committers who have no activity on the project (through merges, triage, commits, etc.) will have their permissions suspended.
  • Consider backwards compatibility (goes back to “don’t break existing playbooks”).
  • Write tests. PRs with tests are looked at with more priority than PRs without tests that should have them included. While not all changes require tests, be sure to add them for bug fixes or functionality changes.
  • Discuss with other committers, specially when you are unsure of something.
  • Document! If your PR is a new feature or a change to behavior, make sure you’ve updated all associated documentation or have notified the right people to do so. It also helps to add the version of Core against which this documentation is compatible (to avoid confusion with stable versus devel docs, for backwards compatibility, etc.).
  • Consider scope, sometimes a fix can be generalized
  • Keep it simple, then things are maintainable, debuggable and intelligible.

Committers are expected to continue to follow the same community and contribution guidelines followed by the rest of the Ansible community.

People¶

Individuals who’ve been asked to become a part of this group have generally been contributing in significant ways to the Ansible community for some time. Should they agree, they are requested to add their names and GitHub IDs to this file, in the section below, via a pull request. Doing so indicates that these individuals agree to act in the ways that their fellow committers trust that they will act.