PyPA-Committers November 2018

pypa-committers@python.org

4 participants
4 discussions

Proposal: "Lightweight" governance model for PyPA
by Ernest W. Durbin III 30 May '19

30 May '19

Hello PyPA Committers! I'd like to start discussion on a possible governance model for the PyPA. ## Summary The model described here is what I consider a minimum viable governance for the Python Packaging Authority that would open realtime and asynchronous channels of communication for two purposes: - Keeping PyPA projects up to date on what one another are up to, and where they are headed. - Allowing the PSF Packaging Working Group insight into the PyPA's activities. This model is intended for coordination and communication among Python Packaging Authority projects and does not have bearing on the existing project structure or governance of individual projects beyond the existing requirement of adhering to the PyPA Code of Conduct. ## Model Recurring (weekly, monthly, or quarterly) synchronous meeting of the PyPA via a communications channel TBD. This channel should allow for a log of discussions and some moderation. Structure of meeting TBD, but a something along the lines of: Announcements, Old Business, New Business. A moderator and minute-taker would be responsible for summarizing the meeting, collecting project updates, and publishing minutes and updates for archival purposes and public review. Meeting note publication method TBD. Adherence to the PyPA Code of Conduct would be required for all attendees. ### Requirements #### For attendance as an observer: None (Note that observers can read/watch/listen the meeting in realtime but cannot participate/speak in the meeting.) #### For participation: - Maintainer of a PyPA project. - Contributed a summary of activity for the project ahead of meeting. - Contributed agenda items for Announcements or New Business. OR - Member of Python Software Foundation Packaging Working Group. ## Goals The basic design parameters I had in mind were: - Maintain independence of individual PyPA projects. - Provide a cadence to the PyPA's communications. - Create an incentive for centralized reporting of PyPA project activities. - Provide Packaging Working Group a way to understand what is going on in various PyPA projects, to understand how and where grants could make an impact.

13 32

Adding CoC link to the list description
by Nick Coghlan 21 Dec '18

21 Dec '18

Hi folks, It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see [1]), and it occurred to me that the description for this list should also link to the PyPA CoC: https://www.pypa.io/en/latest/code-of-conduct/ Cheers, Nick. [1] https://github.com/pypa/pypa.io/issues/33 -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

3 3

Any general resources available to run bots?
by Paul Ganssle 18 Nov '18

18 Nov '18

At the PyCon CA sprints, we're working on a bot to make pull requests converting your package over from setup.py to setup.cfg if possible. We're in early stages of trying to make it feasible, but if we get it working, are there any PyPA cloud resources we could use to host it? Thanks, Paul P.S. To be clear, this is not an "opt-out" bot that is going to spam people with PRs, it would be a situation where you create an issue in your repo like: @py2cfgbot Convert this project And it generates a PR.

2 1

GitHub 'maintainers' organization (and private repos for PyPA)
by Pradyun Gedam 10 Nov '18

10 Nov '18

Hi all! I was having a conversation with Sviatoslav from RedHat (Ansible) about GitHub and OSS, during the Bloomberg Sprint in London. He suggested that he'd put forth my username to be added to GitHub's "Open Source Maintainers" (maintainers) organization, where apparently GitHub Community Managers talk to open source maintainers directly, in a private repository and there's other perks like early access to unreleased functionality. I just got the invitation for the 'maintainers' organization from GitHub, which I accepted. The acceptance form asked for the GitHub OSS organization I'm a part of. I filled 'pypa' in that field, and then noticed that they might enable private repositories for free for it, after having submitted, in a confirmation email later. Please let me know if this might be an issue and I'll get that reverted if that's what we want. Other than that, I think I have the ability to request for others to be added to the 'maintainers' organization but I'm not sure how that works yet. Please let me know if there's anyone interested and I'll figure out what has to be done. :) Cheers, Pradyun

2 1

2023

2022

2021

2020

2019

2018

PyPA-Committers November 2018