Nick Coghlan added the comment: Ezio's right I ended up mixing together a few different objectives here, which is an artifact of how the idea came about:
* my starting point was wanting a list of folks that already have commit access (and hence are demonstrably familiar to the core development community) that the PSF can either contract with directly for work on the toolchain (and perhaps for devoting time to the tracker patch backlog), or else refer companies to. At the moment we do this based on personal knowledge, which means there are going to be missed opportunities to make connections with folks the current Board of Directors don't know personally. * in the ensuing discussion, I realised the "we're all volunteers here" disclaimer isn't true at the moment, and is unlikely to ever be true again, and that's something that would be good to disclose to help folks understand the sustaining engineering model that has emerged around CPython The draft patch ended up being framed as the latter, while still covering the former, which I agree is confusing. As a result, I like the idea of making the page title "Motivations and Affiliations" to focus on the "Why are we here?" aspect. At the end, we can then have a section "Availability for PSF Referrals" and ask core developers that are potentially able to take on contract and freelance work to let the PSF Board know. We can then maintain that list in confidence, rather than requiring people to broadcast their availability for contract work to the entire internet. ---------- _______________________________________ Python tracker <[email protected]> <http://bugs.python.org/issue25194> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
