| *** diablo_rojo is now known as Guest3941 | 00:52 | |
| *** dasm|rover is now known as dasm|out | 00:55 | |
| opendevreview | Vishal Manchanda proposed openstack/governance master: Retire xstatic-font-awesome https://review.opendev.org/c/openstack/governance/+/872837 | 04:19 |
|---|---|---|
| *** gthiemon1e is now known as gthiemonge | 10:38 | |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen's candidacy for Watcher PTL https://review.opendev.org/c/openstack/election/+/872677 | 11:04 |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen's candidacy for Watcher PTL https://review.opendev.org/c/openstack/election/+/872677 | 11:07 |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen's candidacy for Watcher PTL https://review.opendev.org/c/openstack/election/+/872677 | 11:18 |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen's candidacy for Watcher PTL https://review.opendev.org/c/openstack/election/+/872677 | 11:18 |
| fungi | tc-members: don't forget, openstack community call with members of the openinfra board od directors tomorrow at 20:00 utc, three hours after the tc meetings ends. connection info, topics brainstorming and notes here: https://etherpad.opendev.org/p/2023-02-board-openstack-sync | 13:22 |
| *** dasm|out is now known as dasm|rover | 13:53 | |
| *** dasm|rover is now known as dasm|afk | 15:15 | |
| *** dasm|afk is now known as dasm|rover | 15:50 | |
| JayF | I'm working on my items for follow up on the meeting tomorrow; have a sample email and some rough steps laid out here: https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup-email-template | 16:23 |
| JayF | I'm mainly trying to figure out where this should live permenantly; it seems unwise to put the pypi maintainership instructions on an etherpad where someone could easily edit to to be malicious | 16:24 |
| JayF | is there any suggestions as to where this could go? Preferably a place that could also take pypi screenshots | 16:24 |
| JayF | As a hilarious aside, the login.launchpad.net_154 user that created IPA that made me worry so much in the beginning -> it's apparently my pypi account that I hadn't logged into in a long, long time | 16:24 |
| clarkb | there is a document on setting up an openstack project iirc | 16:26 |
| clarkb | could put screenshots in that | 16:26 |
| JayF | like add a section specifically about how to remove excess pypi access | 16:26 |
| JayF | I like that | 16:26 |
| fungi | yeah, if it's something that's going to be useful past the end of this cleanup exercise, then the project teams guide seems like the best place for it | 16:28 |
| gmann | JayF: thanks, looks good to me. did you figure out the exact place in project-team-guide where to add pypi instruction ? | 17:31 |
| JayF | I'm about to take that on now, just got out of a meeting | 17:32 |
| gmann | I do not think we have something in p-t-g side on project creation but this opendev doc another relavant place? https://docs.opendev.org/opendev/infra-manual/latest/creators.html#pypi | 17:36 |
| gmann | if this is not openstack specific things. otherwise you can create new page in p-t-g or maybe in release management page? doc/source/release-management.rst | 17:37 |
| JayF | https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-opendev-permission-to-publish-releases I'll add a section after this | 17:38 |
| JayF | on how to ensure only automated systems retain access | 17:38 |
| gmann | +1, sounds good | 17:39 |
| fungi | yeah, there's still a lot of openstackisms in that document which need to be forklifted to openstack's documentation | 17:58 |
| JayF | fungi: are you OK with my plan as stated? | 18:09 |
| fungi | JayF: yes, for now there's enough mention of openstack policies in that document that a little more won't hurt as long as things that are openstack governance choices/mandates are called out as such | 18:16 |
| JayF | ack | 18:17 |
| fungi | i'm not the only reviewer for that repo though, so this is just my opinion | 18:17 |
| clarkb | maybe write it to be generic in how to do it and leave the policy out | 18:22 |
| clarkb | "you may want to remove additional access to prevent unexpected packaging changes" | 18:23 |
| JayF | that's pretty much the route I'm going | 18:23 |
| JayF | So one thing I see while doing this, now that Igot around to it | 21:30 |
| JayF | the existing guide tells people to make openstackci a maintainer, not an owner | 21:30 |
| JayF | I'm going to change that along with my change, but it does mean we're more likely to have annoying cases than good cases :( | 21:31 |
| clarkb | ye that was called out by johnsom | 21:31 |
| gmann | +1. on fixing that. none of us checked that till now | 21:52 |
| gmann | noonedeadpunk: If i can recall correctly from previous meeting discussion, you will add some doc in governance about the policy on PyPi ownership? | 21:53 |
| gmann | that is make it explicitly in TC policy also | 21:53 |
| JayF | https://review.opendev.org/c/opendev/infra-manual/+/873033 is the change I pushed, fwiw | 21:55 |
| JayF | tried to keep it very generic | 21:55 |
| JayF | and https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup-email-template is the proposed email template | 21:55 |
| fungi | JayF: gmann: clarkb: note that projects using opendev to publish to pypi don't need to make our account an owner, maintainer is sufficient. openstack policy is going to be to make it an owner i guess, but that's not something we want to state is required in the opendev infra-manual | 22:19 |
| JayF | can you put that on the review as well, please? | 22:19 |
| JayF | I suspect we'll end up having to split the guides or do a oneoff doc | 22:19 |
| fungi | i'll try to remember when i have time to review it | 22:19 |
| JayF | ack | 22:20 |
| fungi | but this is one of those places where the nuances of describing openstack community policy in an opendev document becomes important | 22:20 |
| JayF | that comment makes me think you're going to hate all of it | 22:20 |
| JayF | lol | 22:20 |
| fungi | not going to hate it, we just need to make it clear "this is the minimum you'll need, but if your project is going to be an official part of openstack you need to do it this other way" | 22:21 |
| fungi | there's already quite a few of those in the same document | 22:21 |
| gmann | let's put the policy in governance in this page https://github.com/openstack/governance/blob/master/reference/new-projects-requirements.rst | 22:22 |
| fungi | all things which should eventually move to an openstack-focused document to remove a lot of the potential confusion | 22:22 |
| gmann | and step to do can be in project team guide | 22:22 |
| gmann | tc-members: gentle reminder to review the 2023.2 testing runtime, this is needed by release team and to prepare the job template https://review.opendev.org/c/openstack/governance/+/872232 | 22:31 |
| *** dasm|rover is now known as dasm|off | 22:40 | |
| johnsom | This all sounds like things I was advocating for (the documentation improvements). | 22:53 |
| gmann | johnsom: +1 | 23:05 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!