Thursday, 2018-07-19

*** dklyle has quit IRC00:02
*** annabelleB has quit IRC00:51
*** annabelleB has joined #openstack-tc00:53
*** annabelleB has quit IRC00:53
*** alex_xu has quit IRC00:57
*** alex_xu has joined #openstack-tc01:02
*** harlowja has quit IRC01:09
*** evrardjp has quit IRC01:44
*** alex_xu has quit IRC01:47
*** ricolin has joined #openstack-tc01:47
*** alex_xu has joined #openstack-tc01:48
*** evrardjp has joined #openstack-tc01:49
*** evrardjp has quit IRC02:02
*** evrardjp has joined #openstack-tc02:08
*** mriedem has quit IRC02:25
*** harlowja has joined #openstack-tc03:51
*** tellesnobrega has quit IRC04:08
*** harlowja has quit IRC04:22
*** diablo_rojo has quit IRC04:51
*** tellesnobrega has joined #openstack-tc05:01
*** fdegir has quit IRC05:29
*** DuncanT_ has joined #openstack-tc05:29
*** johnsom has quit IRC05:29
*** fdegir has joined #openstack-tc05:29
*** portdirect_ has joined #openstack-tc05:30
*** bauzas has quit IRC05:30
*** mwhahaha has quit IRC05:30
*** portdirect has quit IRC05:30
*** lxkong_ has joined #openstack-tc05:30
*** mwhahaha_ has joined #openstack-tc05:30
*** mwhahaha_ is now known as mwhahaha05:30
*** portdirect_ is now known as portdirect05:30
*** johnsom has joined #openstack-tc05:30
*** lxkong has quit IRC05:31
*** aspiers has quit IRC05:31
*** DuncanT has quit IRC05:31
*** lxkong_ is now known as lxkong05:31
*** portdirect is now known as Guest7295205:32
*** bauzas has joined #openstack-tc05:35
*** aspiers has joined #openstack-tc05:40
*** e0ne has joined #openstack-tc06:20
*** openstackgerrit has quit IRC07:04
*** tellesnobrega has quit IRC07:27
*** tosky has joined #openstack-tc07:37
*** dtantsur|afk is now known as dtantsur08:07
*** dtantsur is now known as dtantsur|bbl08:24
*** openstackgerrit has joined #openstack-tc08:24
openstackgerritColleen Murphy proposed openstack/governance master: add validation for new repositories
*** tellesnobrega has joined #openstack-tc08:43
*** cdent has joined #openstack-tc09:24
*** alex_xu has quit IRC10:03
*** alex_xu has joined #openstack-tc10:08
cdentcmurphy: have you started anything with designate and health tracking?10:49
cmurphycdent: no I have not10:53
cdentcmurphy: cool, I'll get that ball rolling10:56
cmurphythanks cdent10:56
*** rosmaita has joined #openstack-tc11:08
*** dtantsur|bbl is now known as dtantsur12:02
openstackgerritDoug Hellmann proposed openstack/governance master: add vice chair role to the tc charter
openstackgerritDoug Hellmann proposed openstack/governance master: designate Mohammed Naser as vice chair
dhellmanntc-members: here's something to consider before office hours ^^12:22
*** cdent has quit IRC12:27
dims+1 from me dhellmann12:31
*** Guest72952 is now known as portdirect12:41
*** edmondsw has joined #openstack-tc12:41
dhellmannEmilienM , dims : thanks!12:42
openstackgerritDoug Hellmann proposed openstack/governance master: show the relative earliest date of approval
*** mriedem has joined #openstack-tc12:53
-openstackstatus- NOTICE: is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown.12:58
*** ChanServ changes topic to " is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown."12:58
*** cdent has joined #openstack-tc13:26
*** cdent has quit IRC13:26
*** cdent has joined #openstack-tc13:31
*** ChanServ changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | | channel logs"13:41
-openstackstatus- NOTICE: is back on-line. Changes with "POST_FAILURE" job results should be rechecked.13:41
*** e0ne has quit IRC13:42
*** ricolin has quit IRC13:58
*** e0ne has joined #openstack-tc14:21
*** hongbin_ has joined #openstack-tc14:22
*** AlanClark has joined #openstack-tc14:46
cdenttc-members, is it office hours time?15:00
* cdent waves hello15:00
TheJuliafeels like that time of the day15:00
cmurphyo/ /me is in another meeting15:00
AlanClarko/ listening in15:01
ttxOh! Oh! I have a question!15:01
TheJuliattx: What is your question?!?15:01
ttxRe: -- what shall we do of completed items15:01
ttxSome are marked done, some are just removed15:01
dhellmannyeah, I haven't been consistent there. I meant to mark them done until I included them in a summary email and then delete them.15:02
ttxGiven the tracker nature, I have sided with removing15:02
*** dtantsur is now known as dtantsur|afk15:02
ttxi just removed the "Diversity tracking" item since all tasks have been completed15:02
dhellmannmaybe as each of us removes an item, we can add a note somewhere at the top to be included in the next summary15:02
dhellmannhaving everyone help with those updates would save me a good bit of effort15:03
ttxyeah, we should ping the summary writer so that can be mentioned15:03
*** lbragstad has joined #openstack-tc15:03
dhellmannor we could send separate emails15:03
dhellmannwe did say we were going to do "status updates" on each initiative15:04
smcginnisShould we add a "summary queue" section to there and move completed things to that. Then that gets cleared out once they actually make it to an update.15:04
* cdent has to step out15:04
cdentback in a few minutes, need to retrieve sarah15:05
dhellmannsmcginnis : that works15:05
dhellmannhow do folks feel about using that wiki page for tracking this stuff in general?15:06
zanebjust had a chat with the public cloud WG folks about trying to get more feedback to the Adjutant team
cmurphydhellmann: I think is done but I don't really feel like it's worth a status email (I didn't actually have to do anything)15:06
*** e0ne has quit IRC15:06
dhellmanncmurphy : did the elections team actually approve that patch to schedule the election? I may have missed that...15:07
smcginnisOnly one +2 so far I believe.15:07
cmurphydhellmann: no I don't think it's approved yet but it's proposed at least15:07
dhellmanncmurphy : ok15:07
dhellmannI'll leave it up to you to decide how to define "done" there15:08
smcginnisI think that should go soon since self nomination needs to start next week IIRC.15:08
dhellmannmaybe we need to nudge them to keep it moving?15:08
smcginnisdiablo_rojo_phon: <nudge15:09
cmurphypersia: ping15:09
cmurphydhellmann: I'll continue to follow up, seems it's not "done" yet15:09
* ttx will salvage his deletion and move it down15:09
dhellmanncmurphy : ok, thank you15:10
dhellmannttx: also thanks :-)15:10
dhellmannzaneb : I'll read that log, but were they generally receptive/interested?15:10
persiaAre we talking about 582109, or did I miss something?15:11
cmurphypersia: yes 58210915:12
ttxdhellmann: check to see if that's what you had in mind
zanebdhellmann: don't think there were actually enough people there to answer that, but I think they'll be very helpful in getting the message out to the people we need to be interested15:12
persiaAh, good.  I always fear I miss things on travel.15:12
smcginnisfungi is on vacation and tonyb is excluding himself since he would have a conflict, so I think diablo_rojo_phon is probably the one that will need to get that going.15:13
dhellmannttx: wfm. if you want to add any notes to help with creating the summary that would be good, too, but this looks fine.15:13
dhellmannzaneb : ok, that's a good start15:13
dhellmannsmcginnis : perhaps if we invoke diablo_rojo_phon one more time the magic will work15:13
smcginnisIt worked for beetlejuice. ;)15:15
dhellmann3 *is* a magic number15:16
dhellmanndoes anyone have any questions or concerns about the vice chair proposal I posted this morning?
smcginnisDoes it need to be that formalized?15:16
dhellmannI see one point about wording from TheJulia. I can address that as a follow-up15:16
dhellmannsmcginnis : I went back and forth on that, but since one of the responsibilities is being the point of contact with the board, I thought it would be good to be clear.15:17
smcginnisOK, fair enough.15:17
TheJuliaI simply wanted to raise it since the associated term was implied15:17
ttxdiablo_rojo_phon is in PTO, so probably not15:17
dhellmannTheJulia : yep, I think your point is valid15:18
dhellmannttx: ah. we may need to find another election official to help, then.15:18
persiaGiven that we want to start next week, that's an awkward time to not have enough approvers.15:18
smcginnispersia: Maybe you need to just push that one through.15:18
smcginnisAt least there have been a couple +1 votes on it as well.15:18
smcginnisUnless someone wants to track down Tristan.15:19
persiasmcginnis: I'll try to catch diablo_rojo later in the day (it's early for folk in negative timezones), and maybe do that if I have no success.  fungi has also been demonstrating limited skills at disconnected holiday :)15:19
smcginnispersia: Did you see ttx's comment above - she's on holiday as well.15:20
dhellmannyeah, I would prefer that we not rely on a culture of people being bad at disconnecting15:20
persiasmcginnis: Yes.  I take that as "not actually working" and "definitely not getting up at dawn", but I'm less certain about "forcing oneself to stay off comms" :)15:20
dhellmannpersia: are you prepared to actually run (or at least start) the election? you seem to be the only official present to do so...15:21
dhellmannpresent and not recused, I should say15:21
persiadhellmann: I think that's on us officials.  We should probably be better at scheduling the scheduling of elections, so that we don't end up at this point.  I'll bring that up when we next have more interactive meetings.15:21
dhellmannI would offer to help, but I'm OOO next week as well15:22
persiadhellmann: I think so.  It would be the first one I kicked off, so I have to check the docs, but I believe that it involves sending a couple of emails: likely one Friday and definitely one early next week.15:23
dhellmannok, good15:23
cmurphythanks persia15:23
*** dklyle has joined #openstack-tc15:23
dhellmannyes, thank you15:23
persiaMy main concern is confirming with others that at least one other person is available to double-check the rolls before we close the election.  Depending on how disconnected folk are and/or how long holidays last, I may need help to actually certify the election.15:23
dhellmannI would have to check the election schedule, but I expect we'll have more folks around by the time we need to do that15:24
dhellmannwhen would we need to do that?15:24
persiaBefore the end of the month.15:25
persiaBest practice is to get it done by mid-next week.15:25
dhellmannoh, that soon15:25
dhellmannperhaps we can get another TC member to volunteer then?15:25
persiaYes.  Nominations start Tuesday (or should start Tuesday, if we want to do things on the regular schedule)15:26
dhellmannsomeone who won't be running, or expects to run uncontested?15:26
persiaThis is just for PTL.  Also, we don't prefer the uncontested as officials (hence the recusion)15:26
dhellmannI was reading "close" as something happening later15:26
*** annabelleB has joined #openstack-tc15:27
persia"close the election" meaning confirm to the voting system the set of people who may vote, etc.15:27
dhellmannso if we need another person to help, we need to recruit someone. I was proposing we try recruiting from among tc-members as an interested body of people15:27
dhellmannand by "uncontested" I meant tonyb, but I respect the recusal if that's the way you prefer to do it15:27
persiaThat makes sense.  I feel there is time for folk to think, and a good chance that we can know if help is actually required for Monday office hours.15:28
smcginnisLooks like I may be running again, so I can help as a non-core set of eyes, but better to have someone else.15:28
dhellmannpersia : ok, it sounds like you have it in hand so I'll leave it to you. let us know if you need a backup, though.15:29
persiaI certainly shall.  Thank you for the offer of support.15:29
dtroyeris this PTL or TC election up first?15:29
dhellmanndtroyer : PTL15:29
dtroyerok… I would be available to step in for the TC if needed, still planning to run as PTL again...15:30
ttxI would volunteer,m except I'm also off next week.15:30
cmurphyI could help on Monday or Tuesday of next week, I'm also leaving mid week15:31
dhellmannpersia : in that opening email we should probably make sure that it's clear to folks that the next cycle is going to be a bit longer than usual to let us sync back up with summits at the end of the cycle15:31
dhellmannother than that it should be business as usual15:32
persiadhellmann: I'll play with wording a bit, although in the absence of review, I am a bit uncomfortable deviating from template too far.15:33
dhellmannpersia : ok15:33
dhellmannI don't think we have an official schedule approved yet, do we smcginnis ?15:33
persiacmurphy: In the event that I remain the only available official Monday, I would definitely appreciate someone else able to calculate voter rolls.15:33
smcginnisdhellmann: Stein release schedule?15:34
cmurphypersia: okay I'll be available15:34
smcginnisNo, not yet. I have the proposed one up there we should finalize, but I thought ttx still had some background work to do.15:34
cmurphypersia: I'm sure you can teach me exactly what that entails15:34
dhellmann is the proposal15:34
persiacmurphy: Thanks.15:35
smcginnisttx: Do you have a feel for whether this is going to be what we end up with or not? ^^15:35
ttxdhellmann: regarding would you have an example of how to do a redirect ?15:35
dhellmannttx: yes, let me find you those instructions15:35
ttxsmcginnis: let me check real quick15:35
dhellmannttx, smcginnis : if we don't have an official schedule, we can at least point to the rough proposal15:36
persiaMy feeling is that most folk who might be nominated for PTL are not in a position where they must cease being PTL on a specific date (or if they are, that date is probably not tied firmly to the release schedule and may not yet be known).15:38
smcginnisYeah, as long as we don't expect it to be too much different then that's probably good enough.15:38
TheJuliaI concur with persia15:39
persiaSimply reminding folk that the term of service is a bit longer is probably sufficient.  If the TC feels strongly, I'm happy to reference a review that folk should watch to get dates, but less happy pointing directly at a draft schedule object.15:39
smcginnispersia: That makes sense to me.15:40
dhellmannmy main concern is someone signing up thinking there will be a PTG in February when they could/would stop when it will really be 2 months later; that's a big relative difference15:40
dhellmannbut yes, I agree, the main point was to mention that the term will be a bit longer, just like for ocata we made clear that the term was a bit shorter15:40
ttxsmcginnis: I think we are clear. Summit+PTG in Denver is now a 99.9% chance and will stay that way until all details are worked out which should take a bit15:40
dhellmannover communication ftw15:41
ttxsmcginnis: so feel free to communicate more15:41
persiadhellmann: Would your concern be covered by "This term is expected to be slightly longer, as the release cycle is expected to adjust to match the Summit schedule"?15:42
dhellmannpersia : yes, that wording would cover it15:42
*** alex_xu has quit IRC15:42
dhellmannif anyone has questions about what "slightly longer" means we can address that separately15:42
persiaExcellent.  One of my sources of joy is finding appropriate levels of vague.15:42
* ttx tries some whereto voodoo15:44
cdenthave people seen this:
smcginnisqueues to read...15:45
cdentit has a few interesting strategies/models and some useful illustrations and references15:47
cdentbut it doesn't quite nail it (and acknowledges that)15:47
*** alex_xu has joined #openstack-tc15:47
jrollI may have missed it - is there an email announcement about merging PTG + summit back together?15:53
cdentjroll: you mean you haven't just assimilated that from the air?15:55
cdent:D :(15:55
jrollcdent: I have assimilated it from the air, but the air is not something I can link in slack for management :)15:55
cdentI was making snark15:55
jrollI know :P15:56
* jroll /giphy the winds are telling me15:56
TheJuliaI feel like there was hint to it from the notes sent out from the leadership meeting, but an official "this is going to happen" was pending information to finalize the decision.15:57
pabelangerI only know because of TC meeting, not sure if anything else was made public15:57
jrollok, I didn't miss it then15:57
pabelanger(TC / board meeting @ summit)15:57
openstackgerritThierry Carrez proposed openstack/project-team-guide master: Evolve project setup into a tech guidance chapter
smcginnisttx: That's a good point above. Can we get some kind of official statement sent out letting folks know that the summit and PTG are more than likely merging back together?16:02
smcginnisUnless folks have been following along closely, that may come as a surprise to some.16:02
ttxyes, let me see how that can be done first16:03
smcginnisI could also just announce that if/when we approve the longer release cycle, but I would be afraid it wouldn't be as visible.16:03
*** diablo_rojo has joined #openstack-tc16:03
*** annabelleB has quit IRC16:04
TheJuliaI suspect it may not be able to be formally announced if due diligence and related negotiations are not yet complete. We might just have to use tentative language or state that it is expected, but not finalized, or something along those lines.16:05
smcginnisAs persia said - the appropriate level of vague. ;)16:05
*** diablo_rojo has quit IRC16:08
*** annabelleB has joined #openstack-tc16:16
*** masayukig has quit IRC16:33
*** masayukig has joined #openstack-tc16:34
openstackgerritMerged openstack/project-team-guide master: Update documentation
*** ricolin has joined #openstack-tc16:52
*** edmondsw has quit IRC17:13
*** edmondsw has joined #openstack-tc17:18
*** ricolin has quit IRC17:44
openstackgerritDoug Hellmann proposed openstack/governance master: clarify wording of length of term for vice chair
*** edmondsw has quit IRC18:03
openstackgerritMerged openstack/project-team-guide master: Evolve project setup into a tech guidance chapter
*** AlanClark has quit IRC18:06
*** edmondsw has joined #openstack-tc18:31
*** tosky has quit IRC19:16
dhellmanncdent : that's an interesting article; thanks.19:19
dhellmannI'm not sure how to account for feature-complete projects under that model. I have the sense that "health" is relative to the phase of its lifecycle a project is in.19:21
cdentthat was one of my main questions19:21
cdentI suppose one metric might be issue responsiveness19:21
smcginnisI was thinking about that too. Lifecycle and "code complete" state aren't really addressed.19:21
cdentso not the number of issues19:21
smcginniscdent: That's a good aspect.19:21
cdentbut the rate at which any new issue gets some kind of response19:21
dhellmannI see now in the conclusion she mentions this issue, too19:22
dhellmannperhaps some sort of comparison of the rate of bugs opened vs. closed would do it19:22
dhellmannwhich I guess is what you mean by "responsiveness"19:22
dhellmannalthough a project with 0 issues may also have 0 users; or it may just be simple, solid, code19:23
*** zhipeng has joined #openstack-tc19:25
cdentdhellmann: yeah, that's why I'm wondering if there is a snazzy math way to encapsulate that in one equation: if there are 0 bugs then responsiveness is infinitely good19:27
*** annabelleB has quit IRC19:42
*** e0ne has joined #openstack-tc19:50
*** annabelleB has joined #openstack-tc19:56
*** e0ne has quit IRC19:57
*** gcb has joined #openstack-tc20:16
*** cdent has quit IRC20:18
*** zhipeng has quit IRC20:21
*** zhipeng has joined #openstack-tc20:57
*** zhipeng has quit IRC21:02
* fungi will take a look at the ptl election changes21:28
fungi(limited skills at disconnected holiday indeed)21:28
smcginnisfungi: I think it was covered.21:38
tonybAlternastely on the topic of elections, if we convert Stable into a SIG then we don't need to hold elections ans I can help out21:42
tonybwe've talked befoer about making it a SIG it just hasn't been high on the list21:42
tonyband I don21:42
tonybt want to fast track it and bypass discussion21:42
smcginnistonyb: That's a good point (and idea).21:43
* tonyb will leave it to the TC, but I'm supportive of the idea. I am aware that dhellmann is traveling (what's with it with y'all traveling)21:44
openstackgerritDoug Hellmann proposed openstack/governance master: change format of output
dhellmanntonyb : I think having it be a sig makes some sense but I haven't given it much thought. I support the idea if the contributors do, though21:45
fungias for "feature complete" projects, an interesting dynamic is when a project's original authors feel it has met its intended scope but users are regularly cropping up wanting to expand its scope and add new features21:48
fungido you hand over the reigns at risk the tool suddenly morphs and drops old features the maintainers wanted preserved? tell those users to fork or start a competing/complimentary tool? something else?21:50
fungitonyb: from an election official standpoint, i'll say not needing to run special rolls filtered by stable branch commits would certainly simplify things21:54
tonybfungi: Yes it would.21:55
*** zhipeng has joined #openstack-tc22:17
*** dklyle has quit IRC22:18
smcginnistonyb: Might be worth proposing it as a sig and see what kind of feedback we get on the review.22:18
*** harlowja has joined #openstack-tc22:21
*** zhipeng has quit IRC22:21
*** edmondsw has quit IRC22:30
*** edmondsw has joined #openstack-tc22:31
*** hongbin_ has quit IRC22:34
*** edmondsw has quit IRC22:35
*** annabelleB has quit IRC22:51
tonybsmcginnis: Okay  I'll do that hopefully today22:51
*** dklyle has joined #openstack-tc23:00
*** zhipeng has joined #openstack-tc23:08
*** dklyle has quit IRC23:17
*** zhipeng has quit IRC23:19
*** zhipeng has joined #openstack-tc23:25
*** mriedem is now known as mriedem_away23:45
*** rosmaita has quit IRC23:50
*** dklyle has joined #openstack-tc23:50

Generated by 2.15.3 by Marius Gedminas - find it at!