Friday, 2019-09-06

*** jamesmcarthur has quit IRC00:06
*** jamesmcarthur has joined #openstack-tc00:40
*** ricolin has joined #openstack-tc00:43
*** markvoelker has joined #openstack-tc00:51
*** markvoelker has quit IRC00:56
*** jamesmcarthur has quit IRC01:06
*** jamesmcarthur has joined #openstack-tc01:06
*** jamesmcarthur has quit IRC01:21
*** spsurya has joined #openstack-tc01:27
*** jamesmcarthur has joined #openstack-tc02:05
*** jamesmcarthur has quit IRC02:18
*** jamesmcarthur has joined #openstack-tc02:20
*** jamesmcarthur has quit IRC02:26
*** jamesmcarthur_ has joined #openstack-tc02:26
*** jamesmcarthur_ has quit IRC02:31
*** jamesmcarthur has joined #openstack-tc02:34
*** jamesmcarthur has quit IRC03:34
*** jamesmcarthur has joined #openstack-tc03:37
*** jamesmcarthur has quit IRC03:42
*** dhellmann has quit IRC03:58
*** dhellmann_ has joined #openstack-tc03:58
*** dhellmann_ is now known as dhellmann03:59
mnaserhttps://google.github.io/eng-practices/04:03
mnaserInteresting read04:04
*** jamesmcarthur has joined #openstack-tc04:05
*** jamesmcarthur has quit IRC04:12
*** jaosorior has quit IRC04:34
*** jaosorior has joined #openstack-tc04:34
*** Luzi has joined #openstack-tc04:52
*** jamesmcarthur has joined #openstack-tc05:09
*** jamesmcarthur has quit IRC05:13
*** zhurong has quit IRC05:15
*** markvoelker has joined #openstack-tc05:15
*** markvoelker has quit IRC05:20
*** zaneb has quit IRC05:35
*** zaneb has joined #openstack-tc05:35
*** jamesmcarthur has joined #openstack-tc05:49
*** jaosorior has quit IRC05:49
*** jaosorior has joined #openstack-tc05:51
*** jamesmcarthur has quit IRC05:54
*** markvoelker has joined #openstack-tc06:06
*** markvoelker has quit IRC06:10
*** lpetrut has joined #openstack-tc06:16
*** markvoelker has joined #openstack-tc06:36
*** ildikov has joined #openstack-tc06:40
*** markvoelker has quit IRC06:41
evrardjpmriedm that's very nice. Both the start of the work internally to have a team on that, and the reference to music.06:44
*** jamesmcarthur has joined #openstack-tc06:51
*** jamesmcarthur has quit IRC06:55
*** markvoelker has joined #openstack-tc07:06
*** markvoelker has quit IRC07:11
*** zhurong has joined #openstack-tc07:16
*** markvoelker has joined #openstack-tc07:16
*** markvoelker has quit IRC07:20
*** jamesmcarthur has joined #openstack-tc07:22
*** diablo_rojo__ has joined #openstack-tc07:35
*** diablo_rojo has quit IRC07:39
*** jamesmcarthur has quit IRC07:42
*** zhurong has quit IRC07:43
*** e0ne has joined #openstack-tc08:24
mugsieI liked this bit a lot:08:24
mugsieIn general, reviewers should favor approving a CL once it is in a state where it definitely improves the overall code health of the system being worked on, even if the CL isn’t perfect.08:24
mugsieThat is the senior principle among all of the code review guidelines.08:24
ttxclaudiub: that is a fair point, there is a clear dependency there. If we turned winstackers into a SIG, we'd probably have to move os-win to Oslo (with winstackers core as maintainers)09:08
*** markvoelker has joined #openstack-tc09:10
asettleo/09:18
*** markvoelker has quit IRC09:20
*** ricolin has quit IRC10:15
evrardjpmugsie: isn't that always the case? :)11:10
*** johnsom has quit IRC11:53
*** johnsom has joined #openstack-tc11:55
*** bnemec has quit IRC11:55
*** bnemec has joined #openstack-tc11:56
*** EmilienM is now known as EvilienM12:24
*** spsurya has quit IRC12:26
*** ijolliffe has joined #openstack-tc12:29
mugsieevrardjp: not always - especially in OpenStack in the past12:32
asettlehey ttx - jroll and I emailed Jimmy about this: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008188.html12:33
asettleWe put our hands up since we won't be going12:33
asettleGuessing that was not communicated? Or sent? Or something?12:34
*** markvoelker has joined #openstack-tc12:45
*** mriedem has joined #openstack-tc12:46
ttxasettle: I remember you answered on that thread... why do you think it was not communicated ? Did you receive another request?12:55
ttxI assumed raising your hand up would be enough12:55
* smcginnis wonders if we can generate an ics file that folks can subscribe to for election deadlines13:00
*** jamesmcarthur has joined #openstack-tc13:07
evrardjpsmcginnis: not a bad idea, not sure it will change things though13:08
smcginnisYeah, just maybe one extra chance that someone that isn't really paying attention could get reminded.13:10
fungii probably just don't understand how most people's calendar applications work... when we update the published ics file will their calendars poll it and update?13:13
smcginnisfungi: I think that depends on the calendar app. I *think* Google calendar does automatically update, but it doesn't appear Outlook does. Not sure about others.13:14
smcginnisProbably not worth the effort if changes are not automatically reflected in most calendar apps.13:15
fungijust wondering because we generally only decide these deadlines a few months before13:15
fungiso unclear what the recommended workflow is for people to be aware of the calendar file13:16
ttxI feel like that will just give another excuse to miss it13:18
asettlettx, ah because it was on the meeting agenda for yesterday without too much context. So I wanted to tap in and just check that it had been communicated that we were happy to help out :D13:18
ttx"my calendar did not update"13:18
smcginnisIt was just a thought. But I think the lack of universal auto-update is a critical flaw in that approach.13:19
fungismcginnis: though more broadly, incorporating election and release activity into a cycle calendar file might be useful to some people13:20
ttxBack when I did an ICS with all release cycle milestones I have no evidence anyone ever used it13:21
smcginnisI use it.13:21
ttxsmcginnis: hah!13:22
smcginnisI wonder if we have any analystics that could tell us how often https://releases.openstack.org/schedule.ics is accessed.13:22
ttxyou mean it still exists :)13:22
smcginnisCombined and per cycle. It's at the end of the top paragraph on https://releases.openstack.org/13:22
ttxused to be done by hand before Doug started removing the humans from the loop13:22
fungimnaser: asettle: for consistency, can we get the current state of the governance repo tagged "sept-2019-elections" when you have a moment? we didn't end up needing it to mark the state of governance used to generate electoral rolls because there were no polls, but it's probably good to still have that tag as a breadcrumb13:22
smcginnisWe have that nice sphynx ics extension that makes it automagic.13:22
smcginnisI guess we do have at least the PTL dates on the train release schedule. So there is at least kind of something in place. But I suppose the ones that aren't aware of the election schedule aren't likely to be the ones that care to subscribe to the release schedule.13:25
njohnstonsmcginnis: I was having a conversation with one of the newly elected PTLs, and they were wondering at what point they are "sworn in" and the election takes place.  I looked at the schedule document and it doesn't call that out specifically.  What is the customary practice?13:29
njohnstons/election takes place/election takes effect/.13:30
smcginnisnjohnston: That's been a gray area for me. Some do an immediate hand over after the election completes. Most I think have the current PTL finish out this release, then do the hand over. Or something inbetween those two.13:31
ttxIt's a bit overlapping. In theory the previous cycle PTL handles up to release, and the other takes over master13:33
ttxbut in some cases it's just immediate13:33
njohnstonThanks smcginnis and ttx!13:34
smcginnisOr the outgoing PTL leaves for Burning Man and disappears for a couple months and the brand new PTL needs to figure out a couple weeks later that they need to quickly learn where things stand and what they need to do to wrap up the previous release when they were fully expecting to start at the beginning of the next.13:35
smcginnisJust saying... could happen.13:35
smcginnis:)13:35
njohnstonsmcginnis: LOL, that sounds like a story13:35
mnaserfungi: sure, let me take caer of it13:38
fungithanks mnaser!13:39
* mnaser doesn't think they've ever manually made tags using gerrit13:40
mnaseralways using release infra..13:40
fungimnaser: https://docs.openstack.org/infra/manual/drivers.html#tagging-a-release13:41
asettleLet me know if you need anything mnaser13:41
fungimnaser: i don't *think* the governance repo is set up so that the release team can review tag proposals for it. ttx can clarify if he's done anything special in the past to create those tags13:42
fungialso possible dhellmann pushed some of them13:43
mnaseryeah its not an access shows that tech-commitee-chair and push signed tags13:43
dhellmannsmcginnis , ttx: I recommend just adding more info to the existing calendar and reminding folks that it exists. Having *a* place to look for community schedule information is simpler than deciding which of several places new information should go13:46
smcginnisdhellmann: I agree. I forgot we still had election info in there. We could maybe do a better job of updating that as specific dates are declared.13:47
dhellmannfungi , mnaser : edit deliverables/_independent/openstack-governance.yaml in openstack/releases13:47
mnaseroh so it can be managed there13:47
dhellmannsmcginnis : ++13:47
dhellmannmnaser : yes, do you think I'd ever do anything by hand? ;-)13:48
fungineat!13:48
fungidhellmann: i bet you edited that file by hand ;)13:48
dhellmannfungi : nope, there's a command in the releases repo to add a new release13:48
fungibwahahaha13:49
fungii stand corrected!13:49
dhellmann.tox/venv/bin/new-release independent openstack-governance feature13:49
mnaserhttps://review.opendev.org/#/c/680691/13:49
mnaserhopefully it doesnt complain too much..13:50
dhellmannoh! you're talking about the election tag. hmm. I think I actually did do that by hand because it's not a version number.13:50
* dhellmann slinks away sheepishly13:50
mnaserpoop13:50
dhellmannwe could probably make that work in the releases repo, give me a second13:51
*** Luzi has quit IRC13:59
*** lbragstad has quit IRC14:04
*** lbragstad has joined #openstack-tc14:07
*** jamesmcarthur has quit IRC14:07
*** markvoelker has quit IRC14:07
dhellmannfungi : how important is it that the tag say "sept" instead of "sep"?14:13
dhellmannit would be nice if I could build the regex using locale versions of the abbreviated month names14:15
*** jamesmcarthur has joined #openstack-tc14:15
dhellmannfungi : https://review.opendev.org/68070614:19
dhellmannmnaser ^14:19
fungidhellmann: oh! in fact it looks like we want it to be sep-2019-elections anyway14:33
dhellmannheh, well, good then :-)14:33
fungidhellmann: https://opendev.org/openstack/election/src/branch/master/configuration.yaml#L414:33
fungithere's some inconsistency among the tags anyway, so i don't see deviating from the historical tag pattern as a problem14:34
dhellmannok, well, as long as we're always consistent about what's expected there in the future we should be good14:34
fungii think that's fine14:34
dhellmannwe could also just say that if the tag ends with "-elections" then anything goes14:34
fungipreferred, even14:34
fungii'm not picky about the implementation, personally14:35
fungialso this allows us to update our election process so that the election officials can propose the tag and then just need the tc chair or whoever to +1 it14:35
dhellmannbonus!14:36
*** jaosorior has quit IRC14:38
*** diablo_rojo__ has quit IRC14:50
*** markvoelker has joined #openstack-tc14:51
*** markvoelker has quit IRC14:55
*** lpetrut has quit IRC15:03
*** bnemec is now known as beekneemech15:04
*** mriedem is now known as mriedem_lunch16:11
*** zhipeng has quit IRC16:21
*** e0ne has quit IRC16:39
*** markvoelker has joined #openstack-tc17:25
*** mriedem_lunch is now known as mriedem17:38
*** jamesmcarthur has quit IRC17:45
*** markvoelker has quit IRC17:57
*** e0ne has joined #openstack-tc17:59
*** markvoelker has joined #openstack-tc18:03
*** markvoelker has quit IRC18:12
*** e0ne has quit IRC18:15
*** markvoelker has joined #openstack-tc18:15
*** markvoelker has quit IRC18:26
*** markvoelker has joined #openstack-tc18:28
*** markvoelker has quit IRC18:38
*** gagehugo has quit IRC19:07
*** markvoelker has joined #openstack-tc19:11
*** markvoelker has quit IRC19:15
*** njohnston_ has joined #openstack-tc19:29
*** njohnston has quit IRC19:30
*** markvoelker has joined #openstack-tc19:41
*** markvoelker has quit IRC19:45
*** diablo_rojo__ has joined #openstack-tc20:06
*** ricolin has joined #openstack-tc20:08
*** markvoelker has joined #openstack-tc20:19
openstackgerritRico Lin proposed openstack/governance-sigs master: Update link for Auto-scaling SIG  https://review.opendev.org/68076920:21
*** njohnston has joined #openstack-tc20:26
*** njohnston_ has quit IRC20:28
*** markvoelker has quit IRC20:29
*** gagehugo has joined #openstack-tc20:43
*** markvoelker has joined #openstack-tc20:50
*** markvoelker has quit IRC20:54
*** ijolliffe has quit IRC21:12
*** ricolin has quit IRC21:14
*** KeithMnemonic1 has quit IRC21:40
*** mriedem has quit IRC21:41
*** EvilienM is now known as EmilienM21:47
*** e0ne has joined #openstack-tc22:02
*** diablo_rojo__ has quit IRC22:13
*** markvoelker has joined #openstack-tc22:15
*** markvoelker has quit IRC22:20
*** e0ne has quit IRC22:34
*** mtreinish has quit IRC23:49

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