The Ansible community requires everyone to be nice to each other, to be empathetic, and to be kind. This is best evidenced by the Ansible Code of Conduct for events. One excerpt: “Ansible is dedicated to providing a harassment-free conference experience for everyone, regardless of age, gender, sexual orientation, disability, physical appearance, body size, ethnicity, religion, or experience level. We do not tolerate harassment of conference participants in any form.” Violation of these requirements can result in expulsion or sanction from the conference organizers.
Held last week in San Francisco, AnsibleFest 2017 was an extremely collegial conference. The influence of Ansible’s code of conduct was everywhere. It was in their email notifications before the conference, at registration, at the booth to get your t-shirts, and even discussed at length during the introduction. By extension, this Ansible code of conduct provides a helpful outline of the ways we should act toward each other in all situations, not just at DevOps-focused conferences. These are human truths that are considered self-evident in the DevOps community. DevOps’ DNA of teamwork requires that community members treat each other with respect and empathy. The Ansible community asks “that you treat your fellow community members with respect and courtesy, and in general, Don’t Be A Jerk.”
Ansible’s community information and contributing page provides additional insight into their intent. It specifically states that community members should be:
Without too much of a stretch, these requirements remind me of the identified characteristics of the Brahmavihāras, which are also known as the “four immeasurables." They are:
A team will not function well if even one person puts themselves above the group’s objectives. When assembling a DevOps team, it is important to evaluate an applicant’s teamwork abilities. It could be cancerous and ruinous if a bad egg slips through the cracks and joins a high-performing DevOps team.
But how can you analyze someone to see if they’ll make a good team member? Ask them about the breadth and depth of their team-based experience. I played American Football for eight years. I played on winning and losing teams, and believe that this experience has given me a fundamental understanding of what it means to be a good teammate. I believe I understand teamwork at its most elemental level. My role as an F5 Networks Senior Product Management Engineer is to be a servant leader to my colleagues and customers. I could also describe my role as a coach. My coaching style comes directly from my own personal experiences of being coached. To be a good DevOps community member, you need to be a good player/coach.
AnsibleFest and DevOps in general can parallel the principles of the Brahmavihara. Treating others in the community as equals and with respect is not an option; it is a requirement. Being a good teammate also mandates it. In the DevOps world, kindness and teamwork are rewarded both intrinsically and extrinsically. If, for whatever reason, you are a person who has struggled getting along with others, now is the time to fix it. Take the present opportunity to get better at teamwork by joining team-based organizations and activities. The dividends will be tremendous.