Wednesday, 2019-08-21

*** jamesmcarthur has joined #openstack-tc00:06
*** jamesmcarthur has quit IRC00:11
*** markvoelker has joined #openstack-tc00:11
*** markvoelker has quit IRC00:15
*** bnemec has joined #openstack-tc00:16
*** markvoelker has joined #openstack-tc00:26
*** zhurong has quit IRC00:27
*** bnemec has quit IRC00:35
*** ianychoi has quit IRC00:57
*** ianychoi has joined #openstack-tc00:59
*** spsurya has joined #openstack-tc00:59
fungioffice hour is upon us once more01:02
zanebo/01:02
*** ricolin has joined #openstack-tc01:05
ricolintc-members, FYI here's result for U release naming http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008624.html01:07
zanebricolin: thanks!01:09
fungithanks for your hard work ricolin! (and also to those who labored on it before)01:11
*** dtruong has quit IRC01:24
*** dtruong has joined #openstack-tc01:25
ricolinthanks zaneb fungi :)01:28
*** jamesmcarthur has joined #openstack-tc02:20
*** jamesmcarthur has quit IRC02:41
*** jamesmcarthur has joined #openstack-tc02:44
*** jamesmcarthur has quit IRC03:26
*** jaosorior has quit IRC04:34
gmannthanks ricolin.04:50
*** jaosorior has joined #openstack-tc05:49
*** jaosorior has quit IRC06:21
*** ianychoi has quit IRC06:34
*** ianychoi has joined #openstack-tc06:34
*** ianychoi has quit IRC07:00
*** ianychoi has joined #openstack-tc07:01
*** jaosorior has joined #openstack-tc07:04
ttxo/07:10
*** e0ne has joined #openstack-tc07:56
*** jaosorior has quit IRC08:00
asettleThanks ricolin :D08:31
*** ianychoi has quit IRC08:32
*** ianychoi has joined #openstack-tc08:33
ricolinasettle, gmann thanks:)09:00
*** jaosorior has joined #openstack-tc09:19
openstackgerritMerged openstack/project-team-guide master: Use promote for publishing  https://review.opendev.org/67754510:40
*** jamesmcarthur has joined #openstack-tc11:49
*** jamesmcarthur has quit IRC12:07
*** jamesmcarthur has joined #openstack-tc12:08
*** jamesmcarthur has quit IRC12:28
*** jamesmcarthur has joined #openstack-tc12:50
*** lbragstad has joined #openstack-tc13:00
*** mriedem has joined #openstack-tc13:39
*** bnemec has joined #openstack-tc13:55
*** coreycb has quit IRC14:14
*** aprice has quit IRC14:15
*** kmalloc has quit IRC14:15
*** tiffanie has quit IRC14:15
*** dhellmann_ has joined #openstack-tc14:15
*** cmurphy has quit IRC14:16
*** jbryce has quit IRC14:16
*** dhellmann has quit IRC14:16
*** mgagne has quit IRC14:16
*** csatari has quit IRC14:16
*** logan- has quit IRC14:16
*** dhellmann_ is now known as dhellmann14:16
*** irclogbot_1 has quit IRC14:17
*** logan_ has joined #openstack-tc14:17
*** mgagne has joined #openstack-tc14:17
*** cmurphy has joined #openstack-tc14:18
*** logan_ is now known as logan-14:18
*** tiffanie has joined #openstack-tc14:18
*** coreycb has joined #openstack-tc14:18
*** irclogbot_1 has joined #openstack-tc14:18
*** csatari has joined #openstack-tc14:19
*** kmalloc has joined #openstack-tc14:19
*** aprice has joined #openstack-tc14:19
*** jbryce has joined #openstack-tc14:19
*** Jeffrey4l_ has quit IRC14:19
*** Jeffrey4l has joined #openstack-tc14:21
*** jaosorior has quit IRC14:41
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after major cities  https://review.opendev.org/67578814:41
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after the ICAO alphabet  https://review.opendev.org/67578814:41
openstackgerritJames E. Blair proposed openstack/governance master: Ask the Foundation to name releases  https://review.opendev.org/67578814:41
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after random words  https://review.opendev.org/67578814:41
openstackgerritJames E. Blair proposed openstack/governance master: Clarify the existing release naming process  https://review.opendev.org/67578814:41
openstackgerritJames E. Blair proposed openstack/governance master: Stop naming releases  https://review.opendev.org/67578814:43
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after major cities  https://review.opendev.org/67774514:43
asettleomg what's happening14:43
corvusi messed up a rebase :)14:44
asettleHAHA corvus ya freakin' me out man14:44
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after the ICAO alphabet  https://review.opendev.org/67774614:44
openstackgerritJames E. Blair proposed openstack/governance master: Ask the Foundation to name releases  https://review.opendev.org/67774714:44
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after random words  https://review.opendev.org/67774814:45
openstackgerritJames E. Blair proposed openstack/governance master: Clarify the existing release naming process  https://review.opendev.org/67774914:45
asettlecorvus, do you often refer to things as condorcet?14:45
corvusasettle: it's how i prefer my elections, yes :)14:46
asettleI do enjoy how declarative this is.14:47
corvussince 'stop naming releases' doesn't seem to be a winner, i've tried to push up a change for each of the ideas that have come up, along with one or two others that i thought of14:48
corvus(or at least, 'stop naming releases before z' doesn't seem to be a winner -- after z may be a different story)14:48
asettleIn fairness to the objections (including my own) discussion should be had before dropping the system before the system is complete. In theory, U is the perfect time to discuss next steps. Not drop the hot potato.14:49
asettleI'm not convinced the best way to have that discussion is via 6 separate patch suggestions.14:50
fungiwell, it provides a clear set of options to discuss14:50
asettleThat it does.14:51
asettleCan't deny that.14:51
fungi(as well as a way to provide feedback for each one individually)14:51
corvusasettle: i hear that -- my own view is more akin to 'rip the bandage off', but i certainly see the appeal of trying to get to Z (i shared that view until recently)14:51
asettleDispersed feedback over 6 different patches is inevitably going to become convoluted and confusing, fungi14:51
asettleI'd prefer this was in a centralised location for it all to be collated at once. So it can be seen.14:51
asettlecorvus, ohh you reformist, you.14:52
*** lbragstad has quit IRC14:52
corvuswell, i did set all their topics to 'release-naming'14:52
asettleAnd I reset them :)14:52
fungiit's akin to how we approached the "driver teams" debate, where there were a bunch of possibilities to evaluate14:52
asettlefungi, are "driver teams" usually done through a series of patches?14:52
corvusmy idea was to send out a message asking folks to review each of these, leave indicative votes, and then in a week come back and see which ones are good/bad/need refining, then ask the tc to vote on (perhaps a reduced set of) final choices14:53
fungino, we discussed the possibility of forming specific recognized teams around driver projects, and that's how we organized the discussion14:53
asettlefungi, that sounds a little more organised.14:53
corvusi think we've already had a centralized discussion about this on the mailing list; that's where these ideas came from14:53
corvusnow we need a way to find out whether they have any support from the community and the tc14:54
fungibecause there were a lot of different ways we could approach making drivers official projects or not, so writing each one up as a formal proposal was helpful in comparing each14:54
asettlecorvus, I'm not sure I would have called the dissolution of the voting process into a debate a centralised discussion. No decisions were made to change the way things are currently done14:54
asettlefungi, do we have this written down anywhere?14:54
corvusasettle: i understand no decisions have been made, i'm attempting to help drive us to a decision to change14:55
asettlecorvus, I do see that. You're going real fast. I'm not sure my little governance brain is catching up the way I'd like it to.14:55
asettleYou're driving a merc and I'm over here in my Toyota pickup14:55
asettleNOW14:55
asettleOkay14:55
fungiasettle: there is a record of the discussions we had around the possibility of allowing driver teams, which would have required we loosen some of our requirements for what it means to be an official team. the discussions we had around those options were the record14:55
asettle-.-14:56
asettleI love this place14:56
asettleOkay, so to clarify the two discussions we're having here14:56
asettle1. This is corvus coming in and attempting to generate discussion and solutions (cool cool cool)14:57
fungi2. and the way he's going about it is similar to the way we discussed options for making drivers official openstack projects14:57
asettle2. We don't have a formalised way  of actually making these changes (?) other than the previously discussed "driver teams"14:57
asettle... thank you fungi :)14:57
asettleI have nothing against doing it this way, as long as we're all in agreeance that this is the way we're going and we see it as a fair and able way for everyone to have their say.14:58
fungii was providing precedent for holding a discussion this way, by relating it to a similar discussion we had about a different topic a couple years ago14:58
asettleMy concerns would be that we may lose feedback in the reviews and not everything cna be considered. Of course, same thing can be said for the ML14:58
asettlefungi, makes sense.14:58
fungiin the case of the drivers discussion, there was a corresponding ml thread which laid out the options and linked to the proposed alternative resolutions for each option14:59
asettleYou wouldn't happen to know when that was so I don't have to spend 36 hours deep diving through the archives?14:59
fungibut in the end we chose to not pass any resolution because none had sufficient backing, so we instead stuck with the status quo as defined in our project requirements document14:59
fungii can get a reference14:59
fungijust a sec15:00
corvusit's nice that a precedent is handy, but i don't think we need a precedent15:00
asettleThansk fungi :D15:00
asettlecorvus, we don't. But if there's something already in place, or that would potentially be received better by ~others~ then I'd rather go the path of slightly less resistance15:00
asettleI'm a sensitive flower15:00
fungimostly trying to counter asettle's concerns that having multiple competing proposals isn't a way to have a debate15:00
fungiasettle: i don't know what you mean by "in place" i'm just saying we've used this pattern to debate issues in the past15:01
asettleWhich is fair :)15:01
asettleCoolio hoolio15:01
asettleLook, honestly, I should express I'm really not that stressed about it :D I'm just... looking at it and well, yeah, concerns15:01
fungiif we documented every possible way of having a discussion then i don't think we'd ever have time for actual discussions15:01
corvusasettle: one of the options is the status quo15:02
asettlefungi, heh15:02
asettlecorvus, I did see that.15:02
fungiasettle: http://lists.openstack.org/pipermail/openstack-dev/2016-November/108074.html15:02
asettleGracias amigo15:03
fungithat was how we framed the discussion in that case15:03
corvusok -- it just occurred to me that you may be concerned that i pushed up 6 proposals to change things without the decision to change having been made, but the status quo option is a place to say "i don't want anything to change"15:03
asettle^^ bingo15:03
*** jamesmcarthur has quit IRC15:04
asettleI would like to avoid the status quo, because like yourself, I believe something needs to change. But we haven't had any discussion ABOUT a change, other than a slightly rollercoaster debate about the U naming15:04
asettleAnd then the subsequent comments on your initial patch15:04
corvusthere were several suggestions for alternates in the ML thread too15:05
asettleThat there was.15:05
mugsieI like the citie one personally (for covering us until Z anyway)15:05
mugsiecities*15:05
asettleBut again, no actual decision to change anything of such. Perhaps corvus it would be good to start a thread suggesting it's time we discuss what happens after Z on the back of the U discussion15:05
asettleSo it's formally begun15:06
* asettle makes dramatic arm gestures to the ceiling 15:06
asettlemugsie, I agree. But hey15:06
asettle the naming convention is a bit of "we should do x y... oh look a squirrel! and the name for the U release is UNICORN"15:07
corvusasettle: you have said in a few words what i have been barely able to express in hundreds :)15:07
corvusi'm not sure i'm the best person to drive the post-z discussion;  i'm most concerned about v-z15:07
asettleI do my best at short notice15:07
asettleYou can hire me for christmas parties and bah mitzvah's15:08
asettlecorvus, alright, I'll do you a deal. You start a thread formally on what to do vor v-z and offer your options off the back of the U discussion15:08
asettleAnd I'll start a separate thread when that Titanic effort is done regarding post Z15:08
asettledo for*15:08
asettleIt's a good deal. Comes with a low 3% per annum.15:10
corvusasettle: so i know what i'm agreeing to, are you asking me to abandon my openstack/governance proposals?15:12
asettleHmmm. Not exactly. I think if you write the email such that you explain you extracted these solutions from the U thread, it would come across a lot less like we've pre-determined solutions without letting the community speak15:13
corvusthat sounds reasonable.  i'll be sure to let folks know they can leave feedback in the ML thread or on the individual changes, and all will be considered15:14
asettleCool, that's great thanks corvus :)15:17
asettlecorvus, if we end up with vasectomies I personally put that on you :p15:39
*** jamesmcarthur has joined #openstack-tc15:41
*** tdasilva has joined #openstack-tc15:44
openstackgerritZane Bitter proposed openstack/governance master: Align release naming process with practice  https://review.opendev.org/67777115:53
openstackgerritZane Bitter proposed openstack/governance master: Clarify proscription of generic release names  https://review.opendev.org/67777215:53
zanebit felt like we didn't have enough reviews on this topic...15:53
* asettle side eyes zaneb 15:54
asettleBro15:54
asettleY u do dis15:54
*** mgagne has quit IRC15:54
asettleWe JUST decided corvus would send an email and OUT you come15:54
*** mgagne has joined #openstack-tc15:55
zanebI wasn't watching IRC because I was busy drafting those changes :)15:56
asettlezaneb, ya killin me15:56
asettletc-members - could we maybe nottt propose anymore ideas to fixing the name conventions until corvus sends an email detailing the fact that we're seriously discussing changes in the first place?15:57
*** tdasilva has quit IRC15:57
*** diablo_rojo has joined #openstack-tc15:58
mnaseri (think) multiple goverannce patches is a good idea to have folks vote on the change that makes the most sense to them16:04
asettleTotally. But can be *please* make this clear to the community that we're actually officially starting this discussion and it's not just something we're flipping out of thin air.16:05
mugsieyeah, but we need to broadcast it more, and allow people suggest ideas (the ML works for this), rather than a fait acompli of "choose from these 6"16:05
*** ricolin has quit IRC16:05
mnaserright, i was under the assumption that we'd push out an email about this to the ML soon so the community at large wants to voice their opinion16:06
asettlemnaser, discussion with corvus resulted in him agreeing (sorta?) to send out the email to initiate that discussion.16:07
mnaseri figured as much, i was just commenting that multiple patches is an good solution to gather 'voting' towards one of the options16:07
*** markvoelker has quit IRC16:08
mnaserit's hard to gauge popularity of an option using ML posts or a single review16:08
mugsieyeah, lets get the list first, then worry about popularity16:12
openstackgerritJames E. Blair proposed openstack/governance master: Name releases after random words  https://review.opendev.org/67774816:14
corvusokay, wow16:16
corvusi have sent the email16:16
corvusi'm sorry i didn't type fast enough to make everyone happy16:16
corvusthat last patchset updates the random words with the output of the RNG.  there are some obvious bad choices there, but also some perfectly bland ones.  since it seems that one may have been unclear, the proposal is for the TC to pick from that random list.  you are obviously not going to choose a bad one.  just choose a good one and call it done.16:17
corvuszaneb: regarding your proposal -- while that seems a fine addition, it only explains one of the seven names which was removed16:19
corvusso it's a partial fix16:19
zanebcorvus: did you see both of my patches?16:19
corvuszaneb: yes, the second explains university.  but not the 6 hanyu names.16:21
corvuszaneb: (though i think the second change could use a clarification)16:22
*** markvoelker has joined #openstack-tc16:22
*** tdasilva has joined #openstack-tc16:22
zanebcorvus: I believe the first one explains why the rest of the names were removed. we received feedback (both on the mailing list and from Horace) that using GR transliteration was not culturally appropriate16:24
asettleThanks for sending the email corvus16:25
*** tdasilva has quit IRC16:27
corvuszaneb: i believe that's still very much in doubt.  i don't recall anyone saying it was offensive.  i suspect that it may be difficult for me to fully understand the context there, but the way i read the feedback was that it was "unusual" or "unfamiliar".16:28
*** e0ne has quit IRC16:30
zanebthe poll co-ordinator(s) decided it was inappropriate after receiving feedback. we can (but I won't) debate the exact nature and merits of the feedback, but it doesn't change the process16:32
corvuszaneb: that's the problem with this proposal -- it doesn't resolve conflict, it creates more.  trying it on for size -- it doesn't adequately resolve the confusion around "U" because we can't even determine that it was offensive (or even inconsiderate).  you heard something that i did not hear.  it's guaranteed to create more conflict rather than less.16:38
*** diablo_rojo has quit IRC16:40
*** spsurya has quit IRC16:43
mugsiecorvus: we did recieve feedback that that method of romanisation was not one that party liked, or had sactioned as the official one. we also recieved feedback that it wasn;t the case, but the supervisor went with the cautious route (which is fine)16:51
corvusmugsie: i'm not sure about "party liked" (i don't remember that one) but it is certainly not in dispute that it is not the official romanization -- we're all agreed on that.  so the bearing this has on zane's proposal is that even after all that, it's unclear whether that makes it 'inconsiderate' or just 'unusual'.16:55
corvusso my argument is that rather than clearing this up, the change as written would not have avoided a discussion about whether the hanyu names on the poll should be removed16:56
mugsieit makes it a judement call? for which we have a TC, who appoints a poll supervisor, who makes the call about it being inconsierate, which is what happened?16:57
mugsiehumans are squishy, random beings, that it are basically impossible to write hard and fast rules for, which is why things like parlements and TCs exist.16:58
corvusi agree, which is why asking a single person to evaluate suggestions like this is fraught with problems.  we should be avoiding it altogether by using a completely different system which reduces the chances of contentious choices or discussions.  this increases those chances by adding in more opportunities for disagreement.17:04
corvusthe confusion around the hanyu names isn't that some people think it's offensive, and some people don't -- it's that we literally don't know if someone has said it's offensive or not.17:05
corvus(the fact that that very point was discussed at length before the entire process even began, and the tc agreed that they were not offensive, only for that to be reversed at the end only further illustrates the difficulty)17:06
*** lbragstad has joined #openstack-tc17:24
*** e0ne has joined #openstack-tc17:49
*** e0ne has quit IRC18:01
*** lbragstad_ has joined #openstack-tc18:04
*** lbragstad_ has quit IRC18:04
cmurphydiablo_rojo_phon: persia fungi i wanted to confirm that https://releases.openstack.org/train/schedule.html is correct and ptl nominations start next week? i haven't seen any communication about it and the election repo isn't set up with project placeholders for U yet18:06
fungiyeah, i guess we need to make the call to proceed with elections even though we don't have the cycle name nailed down18:11
fungi661674 and 661675 should probably be updated (or used as examples for replacement changes and then abandoned)18:12
*** diablo_rojo has joined #openstack-tc18:13
dhellmannI think it's safe to go ahead with the election and just say "U" for now18:16
*** markvoelker has quit IRC18:16
fungicmurphy: oh, though we did already approve the scheduling info and it's published to https://governance.openstack.org/election/18:17
fungiso we mainly just need the placeholders change18:17
fungi(and communication, obviously)18:17
*** markvoelker has joined #openstack-tc18:22
*** markvoelker has quit IRC18:30
*** e0ne has joined #openstack-tc18:44
*** mriedem has quit IRC18:58
*** mriedem has joined #openstack-tc18:59
*** e0ne has quit IRC19:32
*** e0ne has joined #openstack-tc19:33
fungidiablo_rojo has kick-started the discussion between the electionfolk at http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008651.html and we should hopefully get communication underway asap19:34
cmurphythanks fungi and diablo_rojo19:38
fungii'm working on placeholder files change now19:41
*** markvoelker has joined #openstack-tc19:44
*** markvoelker has quit IRC19:49
diablo_rojocmurphy, no problem19:55
diablo_rojofungi, is doing the real work ;)19:55
*** e0ne has quit IRC20:10
fungier, this will be less work than sending an e-mail20:11
*** e0ne has joined #openstack-tc20:12
fungihardest part was deciding whether to leave it named "u-TBD" or change it to "U"20:13
corvusi'm starting to think we should add another option to the release names discussion: "just use letters"20:14
corvusthis isn't the first release where we've spent a very long time just calling it by its letter20:15
fungiand then after z we can switch alphabets ;)20:20
corvusor we can declare that it's ascii and switch to 'a' which is > 'Z', and put all our problems off for another 13 years.20:21
fungiafter the [, \, ], _, and ` releases, i think you mean20:23
*** jamesmcarthur has quit IRC20:23
corvusobviously!20:23
fungioh, i missed ^ between ] and _20:23
fungisee, naming *is* hard20:24
corvusayup20:24
openstackgerritZane Bitter proposed openstack/governance master: Align release naming process with practice  https://review.opendev.org/67777120:40
openstackgerritZane Bitter proposed openstack/governance master: Fix formatting  https://review.opendev.org/67782020:40
openstackgerritZane Bitter proposed openstack/governance master: Clarify proscription of generic release names  https://review.opendev.org/67777220:42
*** jamesmcarthur has joined #openstack-tc20:44
*** e0ne has quit IRC20:44
openstackgerritJeremy Freudberg proposed openstack/governance master: Name releases after ATCs  https://review.opendev.org/67782720:51
fungi^ makes me wonder if the cycle after "u" will be the "vish" cycle20:53
corvusthe thing i'm driving at in most of my proposals is to try to find a way where we can do less work, stay out of cultural trouble, and have fewer arguments about names.  we all have so little time to do real work.20:58
*** jamesmcarthur has quit IRC21:01
fungii'm inherently lazy, so any proposal to do less unnecessary work gets my support21:10
*** jamesmcarthur has joined #openstack-tc21:16
*** altlogbot_2 has quit IRC21:16
*** mriedem has quit IRC21:18
corvusasettle, stephenfin, amotoki: i've updated https://review.opendev.org/677028 to a final form which i think is mergeable.  i think that's the smallest change which addresses the issues in building the nova docs in pdf.21:18
amotokicorvus: yes, my understanding is same but we need some more cleanup as I did for index.rst in https://review.opendev.org/#/c/676730/321:22
corvusamotoki: oh, you already solved all the problems21:23
amotokicorvus: I see many things to be improved in the nova pdf doc (from doc perspective). how do we move it forward?21:23
corvusi'm now unclear on what stephenfin and asettle asked me to do21:23
corvusamotoki: i didn't find that changes to index.rst were necessary21:24
amotokicorvus: I just tried nova doc as stephenfin said the latex builder does not work for nova doc. I just tried to apply my experiences on neutron.21:25
amotokicorvus: we need an assignee in nova, so you can continue the work if needed. for example, TOC in PDF file is a bift confusing.21:27
amotokis/bift/bit/21:27
amotokimany sections are located under Contributor Guide :(21:28
corvusamotoki: sorry, i don't have time to drive this for nova21:29
corvusi jumped in because stephenfin said he needed some latex help21:29
amotokiah, I see.21:31
corvusamotoki: though i didn't come up with anything you hadn't already found, so it seems i'm superfluous :)21:31
openstackgerritJeremy Freudberg proposed openstack/governance master: Name releases after ATCs  https://review.opendev.org/67782721:31
*** altlogbot_2 has joined #openstack-tc21:37
amotokicorvus: thanks anyway. I don't think it is so superfluous. we could double check them21:38
*** altlogbot_2 has quit IRC21:38
*** altlogbot_2 has joined #openstack-tc21:41
*** altlogbot_2 has quit IRC21:42
amotokicorvus: btw, I am now working on store PDF doc file in the log dir (fetch-pdf-docs) in https://review.opendev.org/#/c/664555/. AJaeger suggested to work with you on how to do this as part of opendev/base-jobs. Your feedback would be appreciatd.21:45
*** jamesmcarthur has quit IRC21:46
*** jamesmcarthur has joined #openstack-tc21:47
*** jamesmcarthur has quit IRC21:51
*** jamesmcarthur has joined #openstack-tc21:51
*** markvoelker has joined #openstack-tc21:59
*** bnemec has quit IRC21:59
*** diablo_rojo has quit IRC22:04
*** jamesmcarthur has quit IRC22:15
*** markvoelker has quit IRC22:24
*** markvoelker has joined #openstack-tc22:35
*** markvoelker has quit IRC22:40
*** jamesmcarthur has joined #openstack-tc22:57
*** jamesmcarthur has quit IRC23:56

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