diff -r 2eb55cc7d601 coredev.rst --- a/coredev.rst Sun Sep 20 19:06:40 2015 +1000 +++ b/coredev.rst Sun Sep 27 13:02:48 2015 +1000 @@ -132,13 +132,13 @@ reputation for being a very nice group of people and we would like to keep it that way. -Second, please be prompt in responding to questions. We are all volunteers so -what little free time one can dedicate to Python should be spent being -productive. If you have been asked to respond to an issue or answer a question -and you put it off it ends up stalling other people's work. It is completely -acceptable to say you are too busy, but you need to say that instead of -stringing people along. This obviously applies to anything you do on the issue -tracker as well. +Second, please be prompt in responding to questions. Many contributors to Python +are volunteers so what little free time they can dedicate to Python should be +spent being productive. If you have been asked to respond to an issue or answer +a question and you put it off it ends up stalling other people's work. It is +completely acceptable to say you are too busy, but you need to say that instead +of leaving people waiting for an answer. This obviously applies to anything you +do on the issue tracker as well. Third, please list what areas you want to be considered an expert in the :ref:`experts`. This allows triagers to direct issues to you which involve @@ -149,6 +149,14 @@ gets in the way, so no one will be insulted if you remove yourself from the list. +Fourth, please consider whether or not you wish to add your name to the +:ref:`motivations` list. Core contributor participation in the list helps the +wider Python community to better appreciate the perspectives currently +represented amongst the core development team, the Python Software Foundation +to better assess the sustainability of current contributions to CPython core +development, and also serves as a referral list for organisations seeking +commercial Python support. + And finally, enjoy yourself! Contributing to open source software should be fun (overall). If you find yourself no longer enjoying the work then either take a break or figure out what you need to do to make it enjoyable again. diff -r 2eb55cc7d601 index.rst --- a/index.rst Sun Sep 20 19:06:40 2015 +1000 +++ b/index.rst Sun Sep 27 13:02:48 2015 +1000 @@ -222,6 +222,7 @@ buildslave gitdevs faq + motivations .. _Buildbot status: http://python.org/dev/buildbot/ diff -r 2eb55cc7d601 motivations.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/motivations.rst Sun Sep 27 13:02:48 2015 +1000 @@ -0,0 +1,71 @@ +.. _motivations: + +Motivations and Affiliations +============================ + +CPython core contributors participate in the core development process for a +variety of reasons. Being accepted as a core contributor indicates only that +an individual is interested in acquiring those responsibilities, has the +ability to collaborate effectively with existing core contributors, and has had +the time available to demonstrate both that interest and that ability. + +This page allows core contributors that choose to do so to provide more +information to the rest of the Python community regarding their personal +motivations for participating in the core development process (which can be +admittedly trying at times), as well as any personal and professional +affiliations which they consider particularly relevant. + +Contributors that wish to participate should add a new section to the end of +the page, using "Name (Country of Residence)" as the heading. Existing entries +can be used as examples for formatting and layout purposes. + +Core contributors that are available for consulting or contract work, or that +offer professional Python training, may choose to disclose that information +here (including linking out to commercial sites with relevant contact details). + +Restrictions on scope +--------------------- + +With changes to the software and documentation maintained by core contributors, +together with related design discussions, all taking place in public venues, +core contributors are NOT required to publish their motivations and +affiliations if they do not choose to do so. This ensures that core development +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. + +While providing additional information on this page is entirely optional, +contributors that are not facing personal safety concerns are specifically +encouraged to disclose commercial affiliations in the following three cases +(even if not currently paid for time spent participating in the core +development process): + +* contributors working for vendors that distribute a commercially supported + Python runtime +* contributors working for Sponsor Members of the Python Software Foundation +* contributors that are available for consulting or contract work on behalf of + the Python Software Foundation or other organisations + +Contributor entries +------------------- + +This page was started in September 2015. The order of entries reflects the +order in which contributor sections were added following initial publication. + +.. We use the "rubric" directive to avoid creating entries in the main table + of contents + +.. rubric:: Nick Coghlan (Australia) + +* Red Hat (Software Engineer - Developer Experience) +* Python Software Foundation (Board of Directors) + +I originally began participating in CPython core development as an interesting +and enlightening hobby activity. Some time after commencing work for Red Hat, I +also became involved in a range of topics related directly to improving the +experience of Python developers on Fedora Linux and derived platforms. + +In addition to my own personal interest in ensuring Python remains an excellent +choice for Linux-based network service development, I am also interested in +helping to ensure its continued suitability for educational and data analysis +use cases.