Skip to content

Latest commit

 

History

History
104 lines (69 loc) · 3.29 KB

2019-02-15_steering-council-update.md

File metadata and controls

104 lines (69 loc) · 3.29 KB
Raw

Steering Council Update

Date: 2019-02-15

Message from the Steering Council

Thanks to everyone who participated in the governance model creation and selection of the inaugural Steeering Council. We look forward to serving on the Steering Council.

This is the first Steering Council update for 2019. This update will be posted twice a month (typically, the 1st and 15th). We provide this update as an open, transparent communication about Steering Council activity and requests. Formal decisions will not be made in this document. This document is informational.

-- Barry, Brett, Carol, Guido, Nick

Mandate

This section maps Steering Council activity and projects to the mandates listed in PEP 13.

Language

Maintain the quality and stability of the Python language and CPython interpreter

Contributors

Make contributing as accessible, inclusive, and sustainable as possible

PEPs

Establish appropriate decision-making processes for PEPs

Interaction with PSF

Formalize and maintain the relationship between the core team and the PSF

Governance

Seek consensus among contributors and the core team before acting in a formal capacity Act as a "court of final appeal" for decisions where all other methods have failed.

This section provides insight into requests for consideration by the Steering Council.

New Requests for Steering Council input

[Steering Council Note] Longer term, do we wish to have these requests be submitted as an issue on the Steering Council repo so a detailed log exists?

  • [2019-02-11-3] Consider PEP 580 - Chris Jerdonek
  • [2019-02-11-2] Communications channels - email, discourse, blend - Victor Stinner (PENDING - Carol/Pablo/? will co-author a PEP)
  • [2019-02-11-1] Promotion of new core developer - Victor Stinner (PENDING - after vote deadline)

This section contains a brief update on administrative items.

Council operations

  • Create an onboarding document for new Steering Council members.
  • Set a meeting calendar for the Steering Council. (monthly? - 1 hour)
  • Add reminder about off-boarding / graceful exit to the onboarding document. Life happens - health, family, work - that may make it necessary for a member to formally step away. Let's have a reminder about this in the on-boarding document.
  • Communicate process for requesting a PEP review: File an issue on the python/steering-council repo

This section provides visibility and scope for the Steering Council's role.

Mandate (PEP 13)

The steering council shall work to:

  • Maintain the quality and stability of the Python language and CPython interpreter,
  • Make contributing as accessible, inclusive, and sustainable as possible,
  • Formalize and maintain the relationship between the core team and the PSF,
  • Establish appropriate decision-making processes for PEPs,
  • Seek consensus among contributors and the core team before acting in a formal capacity,
  • Act as a "court of final appeal" for decisions where all other methods have failed.

Powers (PEP 13)

The council has broad authority to make decisions about the project. For example, they can:

  • Accept or reject PEPs
  • Enforce or update the project's code of conduct
  • Work with the PSF to manage any project assets
  • Delegate parts of their authority to other subcommittees or processes