Committer Oversight (2014-2015)

Owned by BradleyW (Unlicensed)
Last updated: Nov 02, 2021 by Randy Kuehn

Members

  • Esmé Cowles (leader)

  • Chris Fitzpatrick

  • Mike Giarlo

  • Cory Nimer

Purpose

  • Encourage the development of a committer group

  • Provide ongoing support for development process

Work Plan

  1. Reviewing and testing developer-focused documentation

    1. From a new developer’s point-of-view, is it easy to find information on how to get started?

    2. Are the instructions for how to setup a development environment easy to follow?

    3. Is it clear how to request access to necessary resources?

  2. Validating bug reports received via mailing list, github issues, etc. and creating tickets in Pivotal Tracker as needed

  3. Prioritizing Pivotal tickets

    1. Ongoing review to make sure tickets are well-described, remove duplicates, etc.

  4. Reviewing and testing pull requests

  5. Developing best practices for code style, testing, continuous integration, and documentation

  6. Guide development of legal agreements for code committers

  7. Formulate document for Contributing ( example : https://github.com/discourse/discourse/blob/master/CONTRIBUTING.md )

    1. See Contributing draft

    2. How do hackfest participants (open events) contribute?

    3. Whose responsibility is it to review and test code (particularly in the context of plugins, and products resulting from hackfests?)

Previous Committer Oversight Documents

These documents were migrated from Google Docs, and some formatting, comments, etc. were lost.  The originals are still available at https://drive.google.com/#folders/0By8xePZIKXw6a0lINVJWNUh5Nmc.