Merge pull request #2 from PyCQA/add-management

Start writing management documentation

README.rst

@@ -22,3 +22,10 @@ Then create a pull request with your changes.
 
 .. _tox:
     https://tox.readthedocs.org/en/latest/
+
+Code of Conduct
+===============
+
+This repo contains the shared `Code of Conduct`_ for the PyCQA.
+
+.. _Code of Conduct: http://meta.pycqa.org/en/latest/code-of-conduct/

source/code-of-conduct.rst

@@ -0,0 +1,79 @@
+======================================
+Contributor Covenant Code of Conduct
+======================================
+
+Our Pledge
+==========
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+Our Standards
+=============
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+Our Responsibilities
+====================
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+Scope
+=====
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+Enforcement
+===========
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+Attribution
+===========
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4,
+available at http://contributor-covenant.org/version/1/4/

source/index.rst

@@ -29,6 +29,7 @@ Ian
 .. toctree::
     :maxdepth: 2
 
+    code-of-conduct
     introduction
     history
     management

source/management.rst

@@ -1,3 +1,61 @@
 =============================
  The Management of the PyCQA
 =============================
+
+- Creator:
+
+  * Ian Cordasco
+
+- Organization owners:
+
+  * Amir Rachum
+  * Claudiu Popa
+  * Florian Bruhin
+  * Ian Cordasco
+  * Ian Lee
+
+- Pycodestyle (formerly pep8) Administrator(s):
+
+  * Ian Lee
+
+- PyLint Administrator(s):
+
+  * Claudiu Popa
+  * Florian Bruhin
+  * Sylvain Thénault
+
+- Pydocstyle (formerly pep257) Administrator(s):
+
+  * Amir Rachum
+
+All projects in the PyCQA should have a Code of Conduct that they are willing
+to enforce.
+
+
+Project Management
+==================
+
+Each project is managed by its own members. There is no over-arching
+management over all projects in the PyCQA. While many people *could* merge
+pull requests and close issues on *all* repositories, they are trusted to not
+do so unless they are specifically a member of the team maintaining that
+project. At least one member of each project's administration will be an Owner
+of the organzation. This is to allow them to manage their teams and membership
+of others in teams.
+
+
+Team Structure
+==============
+
+Projects are encouraged to have as many teams as they deem necessary to run
+their project. Most projects operate with the following:
+
+- Team of administrators - this team has "Admin" permissions in GitHub for
+  the project's repository/repositories.
+
+- Team of developers (or cores, or whatever you want to call them) - this team
+  has "Write" permissions in GitHub for the project's repository/repositories.
+
+This set-up allows projects to add more people who can merge pull requests and
+close issues without being able to change settings on the repository itself,
+add or remove services, etc.