[Python-checkins] devguide: Move core dev affiliation list above page rationale
nick.coghlan
python-checkins at python.org
Thu Jun 2 15:08:52 EDT 2016
https://hg.python.org/devguide/rev/dd2ffafaebd1
changeset: 806:dd2ffafaebd1
user: Nick Coghlan <ncoghlan at gmail.com>
date: Thu Jun 02 11:36:28 2016 -0700
summary:
Move core dev affiliation list above page rationale
Suggested by Bretty Cannon
files:
motivations.rst | 180 ++++++++++++++++++-----------------
1 files changed, 92 insertions(+), 88 deletions(-)
diff --git a/motivations.rst b/motivations.rst
--- a/motivations.rst
+++ b/motivations.rst
@@ -18,91 +18,13 @@
entry to the :ref:`published-motivations` section below. Guidelines relating
to content and layout are included as comments in the source code for this page.
-Core developers that are available for training, consulting or contract work,
-or are seeking crowdfunding support for their community contributions, may also
-choose to provide that information here (including linking out to commercial
-sites with the relevant details).
+Core developers that are available for training, consulting, contract, or
+full-time work, or are seeking crowdfunding support for their community
+contributions, may also choose to provide that information here (including
+linking out to commercial sites with the relevant details).
-Goals of this page
-------------------
-
-The `issue metrics`_ automatically collected by the CPython issue tracker
-strongly suggest that the current core development process is bottlenecked on
-core developer time - this is most clearly indicated in the first metrics graph,
-which shows both the number of open issues and the number of patches awaiting
-review growing steadily over time, despite CPython being one of the most
-active open source projects in the world. This bottleneck then impacts not only
-resolving open issues and applying submitted patches, but also the process of
-identifying, nominating and mentoring new core developers.
-
-The core commit statistics monitored by sites like `OpenHub`_ provide a good
-record as to *who* is currently handling the bulk of the review and maintenance
-work, but don't provide any indication as to the factors currently influencing
-people's ability to spend time on reviewing proposed changes, or mentoring new
-contributors.
-
-This page aims to provide at least some of that missing data by encouraging
-core developers to highlight professional affiliations in the following two
-cases (even if not currently paid for time spent participating in the core
-development process):
-
-* developers working for vendors that distribute a commercially supported
- Python runtime
-* developers working for Sponsor Members of the Python Software Foundation
-
-These are cases where documenting our affiliations helps to improve the
-overall transparency of the core development process, as well as making it
-easier for staff at these organisations to locate colleagues that can help
-them to participate in and contribute effectively to supporting the core
-development process.
-
-Core developers working for organisations with a vested interest in the
-sustainability of the CPython core development process are also encouraged to
-seek opportunities to spend work time on mentoring potential new core
-developers, whether through the general `core mentorship program`_, through
-mentoring colleagues, or through more targeted efforts like Outreachy's paid
-`internships`_ and Google's `Summer of Code`_.
-
-Core developers that are available for consulting or contract work on behalf of
-the Python Software Foundation or other organisations are also encouraged
-to provide that information here, as this will help the PSF to better
-facilitate funding of core development work by organisations that don't
-directly employ any core developers themselves.
-
-Finally, some core developers seeking to increase the time they have available
-to contribute to CPython may wish to pursue crowdfunding efforts that allow
-their contributions to be funded directly by the community, rather than relying
-on institutional sponsors allowing them to spend some or all of their work
-time contributing to CPython development.
-
-.. _issue metrics: http://bugs.python.org/issue?@template=stats
-.. _OpenHub: https://www.openhub.net/p/python/contributors
-.. _core mentorship program: http://pythonmentors.com/
-.. _internships: https://www.gnome.org/outreachy/
-.. _Summer of Code: https://wiki.python.org/moin/SummerOfCode/2016
-
-
-Limitations on scope
---------------------
-
-* Specific technical areas of interest for core developers should be captured in
- the :ref:`Experts Index <experts>`.
-
-* This specific listing is limited to CPython core developers (since it's
- focused on the specific constraint that is core developer time), but it
- would be possible to create a more expansive listing on the Python wiki that
- also covers issue triagers, and folks seeking to become core developers.
-
-* Changes to the software and documentation maintained by core developers,
- together with related design discussions, all take place in public venues, and
- hence are inherently subject to full public review. Accordingly, core
- developers are NOT required to publish their motivations and affiliations if
- they do not choose to do so. This helps to ensure that core contribution
- processes remain open to anyone that is in a position to sign the `Contributor
- Licensing Agreement`_, the details of which are filed privately with the Python
- Software Foundation, rather than publicly.
-
-.. _Contributor Licensing Agreement: https://www.python.org/psf/contrib/contrib-form/
+For more information on the origins and purpose of this page, see
+:ref:`goals-of-the-motivations-page`.
.. _published-motivations:
@@ -170,7 +92,6 @@
python-committers is also the appropriate point of contact for any other
questions or suggestions relating to this page.
-
.. topic:: Brett Cannon (Canada)
* Personal site: `snarky.ca <http://snarky.ca>`_
@@ -178,7 +99,6 @@
* Microsoft (Software Developer)
* Python Software Foundation (Fellow)
-
.. topic:: Nick Coghlan (Australia)
* Personal site: `Curious Efficiency <http://www.curiousefficiency.org/>`_
@@ -228,7 +148,7 @@
.. topic:: Victor Stinner (France)
- * `Personal website <https://haypo-notes.readthedocs.org/>`_
+ * `Personal website <https://haypo-notes.readthedocs.org/>`__
* Red Hat (Senior Software Engineer)
Victor is hacking the development version of CPython to make Python better
@@ -236,6 +156,90 @@
.. topic:: Kushal Das (India)
- * `Personal website <https://kushaldas.in>`_
+ * `Personal website <https://kushaldas.in>`__
* Red Hat (Fedora Cloud Engineer)
* Python Software Foundation (Fellow)
+
+
+.. _goals-of-the-motivations-page:
+
+Goals of this page
+------------------
+
+The `issue metrics`_ automatically collected by the CPython issue tracker
+strongly suggest that the current core development process is bottlenecked on
+core developer time - this is most clearly indicated in the first metrics graph,
+which shows both the number of open issues and the number of patches awaiting
+review growing steadily over time, despite CPython being one of the most
+active open source projects in the world. This bottleneck then impacts not only
+resolving open issues and applying submitted patches, but also the process of
+identifying, nominating and mentoring new core developers.
+
+The core commit statistics monitored by sites like `OpenHub`_ provide a good
+record as to *who* is currently handling the bulk of the review and maintenance
+work, but don't provide any indication as to the factors currently influencing
+people's ability to spend time on reviewing proposed changes, or mentoring new
+contributors.
+
+This page aims to provide at least some of that missing data by encouraging
+core developers to highlight professional affiliations in the following two
+cases (even if not currently paid for time spent participating in the core
+development process):
+
+* developers working for vendors that distribute a commercially supported
+ Python runtime
+* developers working for Sponsor Members of the Python Software Foundation
+
+These are cases where documenting our affiliations helps to improve the
+overall transparency of the core development process, as well as making it
+easier for staff at these organisations to locate colleagues that can help
+them to participate in and contribute effectively to supporting the core
+development process.
+
+Core developers working for organisations with a vested interest in the
+sustainability of the CPython core development process are also encouraged to
+seek opportunities to spend work time on mentoring potential new core
+developers, whether through the general `core mentorship program`_, through
+mentoring colleagues, or through more targeted efforts like Outreachy's paid
+`internships`_ and Google's `Summer of Code`_.
+
+Core developers that are available for consulting or contract work on behalf of
+the Python Software Foundation or other organisations are also encouraged
+to provide that information here, as this will help the PSF to better
+facilitate funding of core development work by organisations that don't
+directly employ any core developers themselves.
+
+Finally, some core developers seeking to increase the time they have available
+to contribute to CPython may wish to pursue crowdfunding efforts that allow
+their contributions to be funded directly by the community, rather than relying
+on institutional sponsors allowing them to spend some or all of their work
+time contributing to CPython development.
+
+.. _issue metrics: http://bugs.python.org/issue?@template=stats
+.. _OpenHub: https://www.openhub.net/p/python/contributors
+.. _core mentorship program: http://pythonmentors.com/
+.. _internships: https://www.gnome.org/outreachy/
+.. _Summer of Code: https://wiki.python.org/moin/SummerOfCode/2016
+
+
+Limitations on scope
+--------------------
+
+* Specific technical areas of interest for core developers should be captured in
+ the :ref:`Experts Index <experts>`.
+
+* This specific listing is limited to CPython core developers (since it's
+ focused on the specific constraint that is core developer time), but it
+ would be possible to create a more expansive listing on the Python wiki that
+ also covers issue triagers, and folks seeking to become core developers.
+
+* Changes to the software and documentation maintained by core developers,
+ together with related design discussions, all take place in public venues, and
+ hence are inherently subject to full public review. Accordingly, core
+ developers are NOT required to publish their motivations and affiliations if
+ they do not choose to do so. This helps to ensure that core contribution
+ processes remain open to anyone that is in a position to sign the `Contributor
+ Licensing Agreement`_, the details of which are filed privately with the Python
+ Software Foundation, rather than publicly.
+
+.. _Contributor Licensing Agreement: https://www.python.org/psf/contrib/contrib-form/
--
Repository URL: https://hg.python.org/devguide
More information about the Python-checkins
mailing list