Thursday, 2024-05-30

*** bauzas_ is now known as bauzas00:10
*** bauzas_ is now known as bauzas00:18
*** bauzas_ is now known as bauzas01:32
*** bauzas_ is now known as bauzas02:23
*** bauzas_ is now known as bauzas02:30
*** bauzas_ is now known as bauzas04:01
*** bauzas_ is now known as bauzas04:21
*** bauzas_ is now known as bauzas05:19
*** bauzas_ is now known as bauzas09:55
fungifrickler: from the notifications we got, it looks like you cleaned up ~30 collaborators on pypi so far?11:43
*** bauzas_ is now known as bauzas11:43
fungithanks! from the tinmestamps, seems you knocked that out between 10:29:28 and 10:52:27 so took ~33 minutes or a little over a minute per collaborator?11:46
fungithough once you got in the groove the notifications were coming about 30-40 seconds apart11:47
*** bauzas_ is now known as bauzas11:56
fricklerfungi: yes, I did it in two batches so far, took a total of about 1h and deleted a total of 50 accounts if my count was correct. so it seems totally feasible to finish this up over the next weeks or maybe even faster12:09
fricklerfwiw I marked the deleted collaborators by setting them to strike-through in the etherpad. that works well together with copying the username into the clipboard and pasting that into the pypi confirmaton popup ;)12:57
JayFfrickler: that honestly is my take too; skyline is more active than many projects that predate it12:57
JayFIDK if that means they've passed the emerging projects bar; because we don't really have a clear one set, but it'd seem pretty hypocritical to keep them outta the community when we have less-active projects kept in12:58
*** bauzas_ is now known as bauzas13:05
fricklerJayF: ack, seems it is time to start defining that bar. I have some measure of "openstackyness" in my mind, but that will likely be difficult to formalize. would seem wrong to just leave that to a judgement call by tc-members. at least it should be actionable on the project side and also static, so they don't have to chase a moving target13:06
JayFWhile I agree in sentiment; I'd be worried in the same way we have trouble quantifying "project activity" we'd also have trouble quantifying this13:07
JayFI am probably the minority to view it this way, but if we have people who want to add to our ecosystem and have shown themselves to keep CI running and *actually adding to it* rather than just showing up for a week around election time, my primary concern is getting out of their way13:08
JayFif we failed and made them active, and it turned out to be bad, we inactive it and get it outta openstack; if we fail and keep them in emerging, we may run off contributors -- and to me active contributors are our most valuable resource13:08
fricklerJayF: I tend to agree to that, I don't think that there's anything that couldn't get worked on from the inside. as a side effect, saying "bar? which bar? you're in" would also avoid having to actually define something ... until next time at least ;)13:23
JayF++13:23
*** bauzas_ is now known as bauzas13:33
fungiJayF: frickler: the emerging projects definition states that to exit that state they must meet the requirements set forth in https://governance.openstack.org/tc/reference/new-projects-requirements.html14:09
fungiif that list of requirements is deemed too rigorous, the tc could certainly revise it14:09
fricklerhmm, "review of the pre-existing codebase in regard to the 4 opens" might be the only possibly problematic requirement, in particular in view of some baked-in decisions regarding the choice of libraries and backends14:16
fricklerbut thx for the reference anyway, I wasn't aware of that14:16
fungibasically, when skyline applied to become part of openstack, the tc determined they did not yet meet at least some of those requirements, and so defined them as an "emerging technology" with several release cycles to finish the work necessary to meet the rest of the requirements14:20
*** bauzas_ is now known as bauzas14:43
*** bauzas_ is now known as bauzas15:07
gmannit was not question about it is Active or not. it is if they meet all requirement of new project or not16:08
gmannwhen we added it as official project that time they did not meet all requirements so instead of denying this project we added the concept of 'Emerging technology' and give time for such new project to adopt the community process and requirements16:09
gmann++ what fungi also mentioned16:09
gmanngouthamr: meeting is good but not all existing projects have meeting due to their low activities or less contributors 16:10
gmannIMO, if they complete the existing written requirements we can make them a official project and can guide them extra things as recommendation if they want to do16:11
*** bauzas_ is now known as bauzas16:13
gmanntc-members: on leaderless projects, sent email for kuryr remaining repo and charm PTL appointment change. Remaining one is Trove where PTL appointment is up for review, please check #link https://review.opendev.org/c/openstack/governance/+/92046216:45
opendevreviewGhanshyam proposed openstack/governance master: Fixing the validate-legacy script  https://review.opendev.org/c/openstack/governance/+/92084818:32
opendevreviewGhanshyam proposed openstack/governance master: Fixing the validate-legacy script  https://review.opendev.org/c/openstack/governance/+/92084818:34
*** bauzas_ is now known as bauzas18:35
*** bauzas_ is now known as bauzas19:15
gmanntc-members: while fixing ^^ this script, it is found that many project/repo still not properly retired, I am going to start the cleanup and tracking it in old etherpad where we did similar cleanup- more helping hands are welcome:  https://etherpad.opendev.org/p/tc-retirement-cleanup#L1519:18
opendevreviewGhanshyam proposed openstack/governance master: Fixing the validate-legacy script  https://review.opendev.org/c/openstack/governance/+/92084819:19
*** bauzas- is now known as bauzas19:32
gouthamrwow that's quite a list :|19:47
gouthamrnot including openstack/deb-*19:48
gouthamra lot of them seem to be missing a ".gitreview" file; i wonder if its just okay to leave as is19:49
*** clarkb is now known as Guest808919:49
gmannyeah, I am going to ignore the openstack/deb-* for now as they a lot of them19:53
gmanngouthamr: for consistency we should do so that we can enable this check in script to avoid further incorrect retirements  otherwise list keep growing19:54
gouthamrgmann ack; but we'll be upsetting the message in the readme file that asks folks to checkout HEAD~1 :) 19:55
* gouthamr No good deed goes unpunished ¯\_(ツ)_/¯ 19:56
gmanngouthamr: not exactly, we will  be updating that to checkout HEAD^^ or ^219:56
gouthamrgmann: yeah19:57
fungi.gitreview files are only useful if you're pushing changes to gerrit, and can be combined with other changes, so if it were me i'd only add the missing .gitreview files in cases where some other change was also needed19:58
opendevreviewGhanshyam proposed openstack/governance master: Add retirement flag and date for Tripleo andFuel projects  https://review.opendev.org/c/openstack/governance/+/92085520:03
*** elodilles is now known as elodilles_ooo20:04
*** Guest8089 is now known as clarkb20:04
opendevreviewGhanshyam proposed openstack/governance master: Add retired-on date for a few missing projects  https://review.opendev.org/c/openstack/governance/+/92085520:16
opendevreviewGhanshyam proposed openstack/governance master: Add retired-on date for a few missing projects  https://review.opendev.org/c/openstack/governance/+/92085520:17
fungic20:23
fungimmm, this isn't my mail client!20:23
*** bauzas_ is now known as bauzas20:49
*** clarkb is now known as Guest809421:15
*** Guest8094 is now known as clarkb21:19
spotz[m]hehe21:41
*** bauzas_ is now known as bauzas22:45
*** bauzas_ is now known as bauzas23:02
*** bauzas_ is now known as bauzas23:29

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!