diff -r a55c0ddbd6cb coredev.rst --- a/coredev.rst Tue Oct 06 20:37:03 2015 -0700 +++ b/coredev.rst Sat Oct 10 13:23:02 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 also applies to anything you +do on the issue tracker. 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 from the core development community. + 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 a55c0ddbd6cb index.rst --- a/index.rst Tue Oct 06 20:37:03 2015 -0700 +++ b/index.rst Sat Oct 10 13:23:02 2015 +1000 @@ -222,6 +222,7 @@ buildslave gitdevs faq + motivations .. _Buildbot status: http://python.org/dev/buildbot/ diff -r a55c0ddbd6cb motivations.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/motivations.rst Sat Oct 10 13:23:02 2015 +1000 @@ -0,0 +1,117 @@ +.. _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. + +Core contributors that wish to participate in this program add a new entry to +the :ref:`published-motivations` section. Guidelines relating to content and +layout are included as comments in the source code for this page. + +Core contributors that are available for training, consulting or contract work, +or are seeking crowdfunding support for their community contributions, may also +choose to disclose that information here (including linking out to commercial +sites with the relevant details). + +Restrictions on scope +--------------------- + +Changes to the software and documentation maintained by core contributors, +together with related design discussions, all take place in public venues, and +hence can be fully audited by anyone that cares to do so. Accordingly, core +contributors 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. + +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 + +The first two cases are areas where disclosure of commercial interests 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 contribute productively to the core development process, while +the last helps the PSF to better facilitate funding of development work by +organisations that don't directly employ any core contributors themselves. + +.. _published-motivations: + +Published entries +----------------- + +The following core contributors have chosen to participate in this program: + +.. Entry guidelines: + + We use the "topic" directive rather than normal section headings in order to + avoid creating entries in the main table of contents. + + Topic headings should be in the form of "Name (Country)" to help give some + indication as to the geographic dispersal of core contributors. + + Entries should be written as short third person biographies, rather than + being written in first person. + + Entries should be maintained in alphabetical order by last name, or by first + name (relative to other last names) if "last name" isn't a meaningful term + for your name. + + Include a "Personal site" bullet point with a link if you'd like to highlight + a personal blog or other site. + + Include a "Commercial contact" bullet point with a link if you'd like to be + contacted for professional training, consulting or contract work. + + Include a "Crowdfunding" bullet point with a link if you'd like to highlight + crowdfunding services (e.g. Patreon) that folks can use to support your core + development work. + + Include additional bullet points (without links) for any other affiliations + you would like to mention. + + If there's a kind of link you'd like to include in your entry that isn't + already covered by the categories mentioned above, please start a discussion + about that on the python-committers mailing list. + + python-committers is also the appropriate point of contact for any other + questions or suggestions relating to this page. + + +.. topic:: Nick Coghlan (Australia) + + * Personal site: `Curious Efficiency `_ + * Red Hat (Software Engineer, Developer Experience) + * Python Software Foundation (Board of Directors) + + Nick originally began participating in CPython core development as an + interesting and enlightening hobby activity while working for Boeing Defence + Australia. After commencing work for Red Hat, he also became involved in a + range of topics related directly to improving the experience of Python + developers on the Fedora Linux distribution and derived platforms, and now + works for Red Hat's Developer Experience team. + + In addition to his personal and professional interest in ensuring Python + remains an excellent choice for Linux-based network service development, he + is also interested in helping to ensure its continued suitability for + educational and data analysis use cases.