Thursday, 2019-04-25

*** jamesmcarthur has quit IRC00:04
*** lbragstad has quit IRC00:05
*** diablo_rojo has quit IRC00:21
*** lbragstad has joined #openstack-tc00:24
*** jamesmcarthur has joined #openstack-tc00:33
*** jamesmcarthur has quit IRC00:50
*** jamesmcarthur has joined #openstack-tc00:52
*** jamesmcarthur has quit IRC00:53
*** jamesmcarthur has joined #openstack-tc00:54
*** jamesmcarthur has quit IRC00:56
*** jamesmcarthur has joined #openstack-tc00:56
*** whoami-rajat has joined #openstack-tc01:02
*** ricolin has joined #openstack-tc01:05
*** diablo_rojo has joined #openstack-tc01:07
*** mriedem has quit IRC01:11
*** diablo_rojo has quit IRC01:49
*** jamesmcarthur has quit IRC02:00
*** jamesmcarthur has joined #openstack-tc02:01
*** jamesmcarthur has quit IRC02:02
*** jamesmcarthur has joined #openstack-tc02:02
*** lbragstad has quit IRC02:36
*** ricolin has quit IRC02:46
*** jamesmcarthur has quit IRC02:52
*** jamesmcarthur_ has joined #openstack-tc02:53
*** smcginnis has quit IRC03:06
*** jamesmcarthur_ has quit IRC03:14
*** jamesmcarthur has joined #openstack-tc03:16
*** jamesmcarthur has quit IRC03:58
*** ricolin has joined #openstack-tc04:10
*** e0ne has joined #openstack-tc05:05
*** e0ne has quit IRC05:08
*** gagehugo has quit IRC05:23
*** Luzi has joined #openstack-tc05:27
*** gagehugo has joined #openstack-tc05:31
*** adriant has quit IRC05:38
*** adriant has joined #openstack-tc05:38
*** Luzi has quit IRC06:33
*** Luzi has joined #openstack-tc06:34
*** ricolin has quit IRC06:53
*** evrardjp has quit IRC06:55
*** evrardjp has joined #openstack-tc06:55
*** evrardjp has quit IRC06:58
*** evrardjp has joined #openstack-tc06:58
*** ricolin has joined #openstack-tc07:28
*** jpich has joined #openstack-tc07:55
*** e0ne has joined #openstack-tc08:08
*** gmann has quit IRC08:28
ttxdone08:46
asettleMorning o/08:57
asettlealso done08:57
*** dims has quit IRC09:20
*** dims has joined #openstack-tc09:26
*** dims has quit IRC09:33
*** dtantsur|afk is now known as dtantsur09:33
*** dims has joined #openstack-tc09:34
*** dklyle has quit IRC09:50
*** dklyle has joined #openstack-tc09:50
*** tosky has joined #openstack-tc12:25
*** ijolliffe has joined #openstack-tc12:30
*** altlogbot_3 has quit IRC12:33
*** altlogbot_3 has joined #openstack-tc12:39
*** altlogbot_3 has quit IRC12:47
*** altlogbot_2 has joined #openstack-tc12:49
*** smcginnis has joined #openstack-tc13:13
*** ricolin has quit IRC13:21
*** lbragstad has joined #openstack-tc13:22
*** mriedem has joined #openstack-tc13:22
*** altlogbot_2 has quit IRC13:23
fungidhellmann: also i was asked to provide a list of openstack contributors for the calendar leading up to the summit (so a few days shy of a full year as i generated it yesterday) and came up with 1841 distinct individuals13:33
*** altlogbot_1 has joined #openstack-tc13:33
funginot sure if that helps13:34
funginot the same timeframe obviously as it's from april last year to april this13:34
fungibut at least provides some sense of magnitude13:34
dhellmannfungi : I went with my usually vague "about 2000 contributors" and that number is close enough for me to feel comfortable that I'm not entirely misleading anyone13:37
dhellmannthough I should probably dial it down for next time :-)13:38
fungithis is science. if it's within an order of magnitude i say that's a viable model ;)13:38
fungiat least that's what my profs always told me!13:39
*** altlogbot_1 has quit IRC13:42
dtantsurditto :)13:43
asettleLOL13:48
*** Luzi has quit IRC13:55
*** altlogbot_1 has joined #openstack-tc13:57
*** e0ne has quit IRC14:16
evrardjpI hope that's not how we ranked the score for your exams14:21
evrardjphe*14:21
evrardjp"an order of magnitude lower" :(14:22
*** Sundar has joined #openstack-tc14:25
*** gmann has joined #openstack-tc14:26
*** zaneb has joined #openstack-tc14:42
ijolliffe@serverascode HI Curtis - I am putting some stuff around Packet on slide 7 - please have a look when you get a chance14:47
evrardjpijolliffe: correct chan?14:48
ijolliffesorry my nistake14:48
evrardjpno worries :)14:48
*** zaneb has quit IRC14:56
jrollthe impending office hours inspired me to finally send the mail about archiving stale github repos: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005629.html15:00
lbragstado/15:00
gmanno/15:00
fungialoha15:02
ttxohai15:02
fungiand thanks jroll!15:02
jroll:)15:02
ttxQuick reminder that we have a 20-ish-min segment at the PTG for the TC to address the crowd15:02
mriedemif anyone is in any sort of stable branch discussion at the forum it'd be interesting to know if users/vendors/operators are benefiting from the extended maintenance change now that it's been in place for 2 releases (ocata and pike)15:03
ttxyeah the visible impact has been... limited15:03
mriedemand we no longer have the session-at-every-get-together about EOL and all that15:03
ttxmnaser: maybe that is something you could raise at the Board meeting too15:03
mriedemi think red hat is benefiting since they are still backporting things to the EM branches for their downstream support15:04
mriedemsince rhosp has LTS support now15:04
gmannalong with that can we include this question in user survey too ?15:04
fungimriedem: you nailed it. the biggest benefit seems to be that we've stopped having semi-annual arguments about lts ;)15:05
ttxhmm. currently there is no "TC questions" in the survey, but I guess there could/should be15:05
gmann+1. user can give feedback about openstack overall pain points/feedback to TC survey if we will have one.15:07
gmannmriedem: anything went from EM->UM ? i think no.15:08
gmannmay be that time we could know what all users care and benefit from EM15:08
mriedemgmann: idk, there are a lot of projects, smcginnis or dhellmann on the release team would probably know better about that. i think some projects have wanted to opt out, like i think tripleo was wanting to not do EM.15:09
mnaserttx, mriedem: that could be interesting, though, I don't know if that's the audience that might have the best answer to be honest.15:10
dhellmannmriedem , gmann : yes, pike and queens are EM now. https://releases.openstack.org15:10
dhellmannor at least in the process of becoming so15:10
dhellmannI think some of the pike tags may have been caught up in the recent release tool breakage15:11
mriedemdhellmann: pike and ocata15:11
evrardjpnot queens yet15:11
gmanndhellmann: anything 'unmaintained' ? Ocata might be the first gor from EM to UM15:11
evrardjpocata is already EM and pike is still in process (or at least was 2 weeks ago)15:12
evrardjpwhat is UM?15:12
smcginnisI haven't seen any teams specifically ask to go to EOL uet.15:12
evrardjpit's not EOL after EM?15:12
smcginnisUnmaintained15:12
evrardjpI thought these were synonyms15:12
dhellmannoh, sorry, I was looking at the wrong column15:12
smcginnisUnmaintained for 6 months, then EOL. Unless the team asks to go eol.15:12
mriedemevrardjp: https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases15:13
gmannevrardjp: Unmaintained :) and then EOL15:13
evrardjpmriedem: I should know this, my memory is bad15:13
smcginnisWe haven't really sorted out how we are going to determine if an EM repo is being unmaintained for 6 months to determine if it should go EOL.15:13
evrardjpI probably have a mental block of unmaintained15:13
mriedemsmcginnis: if tests are busted and you can't land code and no one cares to fix it15:13
mriedemis my acid test15:13
smcginnisNot a bad one.15:13
gmannyeah, Tempest do not gate EM branch on master gate so we do not know till when tests keep passing there15:14
smcginnis6 months of being broke? Or 6 months of patches not being accepted?15:14
mriedemdifferent problems15:14
mriedemif ci is busted for 6 months and no one has pushed a change to fix it, then it's clearly unmaintained and should be eol15:15
smcginnisStill "unmaintained" though.15:15
mriedemif people are pushing patches and cores aren't reviewing them, or worse they refuse to review them, then it's a social issue15:15
*** openstackgerrit has joined #openstack-tc15:15
openstackgerritMerged openstack/governance-website master: Replace git.openstack.org URLs with opendev.org URLs  https://review.opendev.org/65501115:15
mriedemthere was something about the latter in the resolution15:15
evrardjpmriedem: in that case, why having an official "Unmaintained" state, why not EM->EOL ?15:15
smcginnisAt that point, it may be worth advertising for whether a different team wants to take over that maintenance.15:15
smcginnisIIRC, we said EM didn't have to be the normal project team.15:15
* mriedem didn't really want to stir up this nest that was debated a year ago15:16
* mnaser has noticed people back port changes, see jobs fail and nothing happens after15:16
mriedemit's the same stable core team15:16
mriedemif you want on the stable core team, you do the normal things to get there15:16
mriedemnot just for the EM branch15:16
mriedemhttps://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#core-teams15:16
smcginnisJust found that. Good. I thought we had landed on keeping it open for another team to step in.15:17
mriedemyay for writing stuff down15:18
cmurphyftr suse has backported things to pike but i guess that only just now gone EM, we don't support ocata so no opinion there so far15:18
mriedemi believe VIO has moved on from pike as well15:19
mriedemso likely depends on the vendor and their LTS policies15:19
mriedemwhich is why we could never have a standard LTS upstream15:20
mriedemwell, one of many reasons why15:20
*** jamesmcarthur has joined #openstack-tc15:20
dhellmannit would be interesting to see who is backporting how many patches to which repos in those EM branches15:21
fungimriedem: if a test falls in the forest and no dev is around to hear it, does it actually make a sound?15:23
mriedemyes15:23
fungijust thinking that if a project is actually unmaintained and has broken jobs, we're just as likely to not hear about it15:23
dhellmannand lo, there was a script: https://opendev.org/openstack/goal-tools/src/branch/master/queries/ocata-em/run_contributor_report.sh15:23
mriedemfungi: yeah sure15:24
fungiperhaps if an em branch goes 6 months/one cycle with no backports, it's de-facto unmaintained and can be eol after that?15:24
mriedemi can't speak for other projects, but i'd hope if they have the stable:follows-policy tag or whatever they are conscious of (1) having stable branches, (2) if there is activity and (3) the health of them15:25
mriedemidk, some people also don't upgrade for longggg strethes15:25
mriedem*stretches15:25
mriedemand then they do, and say "oh i just upgraded from mitaka to pike and hit this issue"15:25
mnaserwe can hack something with Gerrit search too15:26
mnaserbranch:stable/pike is:merged15:26
mnaseror somethign15:26
fungiright, i suppose we can claim a branch is indefinitely under extended maintenance, and as long as nobody ever tries to backport anything to it... schrödinger's ci?15:29
dhellmannand some stats: http://paste.openstack.org/show/749755/15:29
dhellmannremember that goal-tools counts reviews, approvals, and patches as separate "contributions"15:30
evrardjpfungi: I am in favour of this15:30
evrardjp(except calling it schrodinger, because it's not technically in both states)15:30
dhellmannand those stats are for ocata, built with the script linked earlier15:30
fungithe branch is simultaneously both working and broken until you look at its job results ;)15:30
*** jamesmcarthur has quit IRC15:32
*** jamesmcarthur has joined #openstack-tc15:34
mnaserwhile most are here15:34
mnaserplease try to give some love to https://review.opendev.org/#/c/653545/ :)15:34
dhellmannstats after updating my stale gerrit cache: http://paste.openstack.org/show/749756/15:34
mnasergmann has done an absolute *amazing* work in following up with everyone.15:34
mnaserjust wanna highlight that15:34
mriedemheh | VexxHost                           |            91 |15:38
mriedemwonder who that is15:38
mriedemdhellmann: the vmware and rackspace numbers in there surprise me, i wonder what projects those are15:38
dhellmannlet me see...15:39
*** efried has quit IRC15:43
dhellmannmriedem : http://paste.openstack.org/show/749757/15:43
mriedemok OSA that makes more sense15:43
dhellmannmriedem : also https://review.opendev.org/65572315:43
dhellmannI should probably write some instructions for using those tools. They make it relatively easy to answer questions like this.15:45
cmurphydhellmann: what is the timeline for those stats?15:49
dhellmannall patches matching: after:2018-08-30 branch:stable/ocata ( is:merged OR is:open )15:50
dhellmannfiltered to only governed projects15:50
cmurphyoh got it15:50
dhellmannI no longer remember what is special about that date. maybe that was when we declared the branch em, though?15:50
mriedemdhellmann: that's when rocky was released15:58
mriedemso N-3 would be ocata15:58
mriedemthe traditional EOL date for the oldest branch15:59
dhellmannah, yeah15:59
*** weshay|rover is now known as weshay15:59
ttxtc-members Reminder, we have a dinner at 8pm on Saturday16:14
ttxI'm traveling tomorrow, and will be seeing y'all on the other side16:14
fungimy flights landing around 4:30mdt so that should be time for me to get checked into my hotel and head to the restaurant16:15
*** dklyle has quit IRC16:15
*** dklyle has joined #openstack-tc16:15
gmannMy flight is still not finalized hope i will make it before 8 PM.16:16
*** jamesmcarthur has quit IRC16:18
scasthings have aligned such where i have time but getting there would be extremely difficult. doable, just difficult16:24
*** jpich has quit IRC16:28
*** Sundar has quit IRC16:30
*** jamesmcarthur has joined #openstack-tc16:31
scasi wouldn't be able to make it before saturday morning at the earliest. my travel pack has grown legs, so that's where the difficulty comes in16:33
asettleWill be there! I think I get in around 5pm or so.16:37
asettlettx, did you send the dinner details by email or is it in an etherpad I've lost?16:37
scasthese past few months have been interesting for me personally, having had a forced time away from most things technology. too much to bloviate about on irc16:39
mugsieasettle: I think it is in an eitherpad ...16:42
asettleAdddd as you say that, i find it16:42
asettleGracias16:42
mugsiehere to help :)16:42
mugsieI am also flying out tomorrow morning - will be in DEN friday night / saturday morning16:43
scasalas, i cannot actually make the trip as i have a court date pending as a result of the fun times. either that, or i would have to make it a short trip16:46
scasby short, i mean basically i'd be around until monday night then catch a flight back to pdx16:48
scasthis requires more c2h5oh to talk about in further detail16:50
scasit16:50
scasit's not /too/ early for that somewhere, is it?16:50
*** Sundar has joined #openstack-tc17:10
*** dtantsur is now known as dtantsur|afk17:14
*** ricolin has joined #openstack-tc17:20
clarkbscas it is quite nice outsude right now17:28
*** tosky has quit IRC18:20
*** corvus is now known as jeblair18:23
*** jeblair is now known as corvus18:23
fungic2h5oh was basically my lunch18:39
fungi"carb loading" to fuel pre-travel yardwork18:39
fungiand also to properly condition my liver so i can survive a full week with all of you18:40
*** jamesmcarthur has quit IRC19:02
*** e0ne has joined #openstack-tc19:06
*** jamesmcarthur has joined #openstack-tc19:14
*** jamesmcarthur has quit IRC19:17
*** e0ne has quit IRC19:17
*** jamesmcarthur has joined #openstack-tc19:18
*** jamesmcarthur has quit IRC19:32
*** ijolliffe has quit IRC19:37
*** samueldmq has joined #openstack-tc19:45
*** Sundar has quit IRC20:07
mnasermriedem, mtreinish, tonyb: I like evrardjp idea of hearing your feedback on https://review.opendev.org/#/c/652084/20:24
mriedemi thought i had already commented on that but guess not20:28
openstackgerritMerged openstack/governance master: Expand on the business value of Designate  https://review.opendev.org/64906920:29
mriedem+1, sure. added smatzek from ibm who i know cared about trove at one point in recent memory20:32
*** jamesmcarthur has joined #openstack-tc20:32
mnaserdhellmann: I feel like you linked this nice article a while back about not re-wrapping text inside git changes20:38
dhellmannI think I know the one you mean, hang on20:38
dhellmannhttps://rhodesmill.org/brandon/2012/one-sentence-per-line/20:38
mnaserdhellmann: ahh yes, thank you.20:40
fungiyeah, that's a useful technique. i prefer it and i follow it *if* i see it is an established pattern in a file i'm editing20:40
fungibut for me, it's still trumped by local convention because collaborating with others and observing established customs is equally, if not more, important20:41
smcginnis++20:42
fungialso, it's only really applicable in situations where single linefeeds are eaten or can be marked as non-semantic20:42
fungiso for things like html or rst it's quite useful20:43
fungialso places like code comments or python docstrings20:43
scasclarkb: it is a great day outside today, but i've done too much outside these past few months20:45
fungion the other hand, i think we're all (me included) a bit too attached to line-by-line diffs. for char-by-char diffs it doesn't matter much20:45
fungithose are harder to render though... we need better tools20:48
*** ricolin has quit IRC20:49
tonyb[m]mnaser:  when I get my laptop out I'll review that20:51
openstackgerritMohammed Naser proposed openstack/governance master: help-most-needed: remove reference to infracloud  https://review.opendev.org/65579320:52
*** gmann is now known as gmann_afk21:01
openstackgerritMerged openstack/governance master: Elaborate on the business value of infra admins  https://review.opendev.org/64189021:04
*** jamesmcarthur has quit IRC21:44
*** jamesmcarthur has joined #openstack-tc21:51
*** jamesmcarthur has quit IRC21:53
*** jamesmcarthur has joined #openstack-tc21:56
*** jamesmcarthur has quit IRC22:04
tonyb[m]mnaser: done (+1)22:14
*** jamesmcarthur has joined #openstack-tc22:27
*** jamesmcarthur has quit IRC22:32
*** whoami-rajat has quit IRC22:51
*** jamesmcarthur has joined #openstack-tc23:19
*** jamesmcarthur has quit IRC23:48
*** jamesmcarthur has joined #openstack-tc23:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!