Thursday, 2018-10-25

*** jamesmcarthur has joined #openstack-tc00:17
*** jamesmcarthur has quit IRC00:58
*** jamesmcarthur has joined #openstack-tc01:01
*** diablo_rojo has quit IRC01:07
*** diablo_rojo has joined #openstack-tc01:20
*** jamesmcarthur has quit IRC01:23
*** jamesmcarthur has joined #openstack-tc01:51
*** jamesmcarthur has quit IRC01:56
*** jamesmcarthur has joined #openstack-tc02:20
*** jamesmcarthur_ has joined #openstack-tc02:27
*** jamesmcarthur has quit IRC02:27
*** jamesmcarthur_ has quit IRC03:10
*** diablo_rojo has quit IRC03:21
*** ricolin has joined #openstack-tc03:44
*** whoami-rajat has joined #openstack-tc03:56
*** lbragstad has quit IRC04:00
*** ricolin has quit IRC04:33
*** ricolin has joined #openstack-tc04:33
*** spsurya has joined #openstack-tc04:50
*** whoami-rajat has quit IRC06:54
*** jpich has joined #openstack-tc08:00
*** e0ne has joined #openstack-tc08:42
*** dtantsur|afk is now known as dtantsur09:09
*** tosky has joined #openstack-tc09:16
*** ricolin has quit IRC09:16
*** dangtrinhnt_x has joined #openstack-tc09:27
*** dangtrinhnt_x_ has joined #openstack-tc09:27
*** dangtrinhnt_x has quit IRC09:32
*** dangtrinhnt_x_ has quit IRC09:42
*** dangtrinhnt_x has joined #openstack-tc10:01
*** dangtrinhnt_x has quit IRC10:06
*** cdent has joined #openstack-tc10:10
*** dangtrinhnt_x has joined #openstack-tc10:10
*** dangtrinhnt_x has quit IRC10:14
*** dkrol has joined #openstack-tc10:38
*** openstackgerrit has joined #openstack-tc10:58
openstackgerritThierry Carrez proposed openstack/governance master: Indicate release style for each repository  https://review.openstack.org/61326810:58
*** dangtrinhnt_x has joined #openstack-tc11:04
*** dkrol has quit IRC11:07
*** dangtrinhnt_x has quit IRC11:08
ttxzaneb: I like how your emails brought a new set of people to the draft!12:09
*** jamesmcarthur has joined #openstack-tc12:14
smcginnisLooks like they worked to get more folks looking at that.12:18
*** jamesmcarthur has quit IRC12:19
openstackgerritThierry Carrez proposed openstack/governance master: Indicate release style for each repository  https://review.openstack.org/61326812:19
cdentttx do you have insight into the changes in the bylaws related to the tc. couple of questions:13:12
cdentis the 16 month simply a safety valve in csae things change or is it driven by something else?13:12
cdentsorry, 1813:12
cdentand do you know why  the and "shall appoint a mediator to assist" block was removed? (or was it moved, not re-moved?)13:13
cdentjbryce or fungi  you too on^13:14
jbrycecdent: the the sixteen months is to account for a scenario where there are longer release cycles. that section will have to be edited still...basically we need to define some kind of term, but because the elections go with release cycles, that's very hard to do and we've ended up with kind of a franken-wording13:16
jbrycewe'll talk about it on the call today and see how the board feels about ambiguity there13:17
cdentI thought perhaps that was it: we might change cycles, we're not sure, let's cover that with some hand waving13:17
smcginnisI did think it seemed a little hand wavish. But it did still state 12 month terms I believe.13:17
smcginnisSo the technical part of me doesn't like the ambiguity, but the governance part of me thinks it covers things well. :)13:18
jbryceyeah it's kind of like we don't have even cycles already so hand wave a little, but not surprisingly, it isn't the best from a legal perspective so we'll also say 12-month for now13:18
* cdent shakes tiny fist at legalese13:19
jbryceon removing the mediator piece, that was just in the list of changes that ttx and fungi shared with me13:19
cdentIt's interesting, because as far as I can tell it is the only mode of escalation out of the tc, thus seemed like something which should have been discussed more broadly in the tc13:20
cdentwe _could_ move it into tc charter/resolution and that would probably be fine13:20
cdentbut it would be good to make sure one does go away before the other shows up13:20
cdentsigh... doesn't go away13:21
smcginnisInstead of a mediator, we can have a battle of wits.13:24
ttxyes the "at most sixteen months" is a way to allow to link election to cycles/events13:27
ttxThe mediator thing was deemed a bit too much leaning into implementation details which belong to TC charter13:30
ttxThat was lower priority, iirc it was suggested by fungi13:30
ttxjbryce: for the 16 months, maybe saying something like "approximately 12 months13:32
ttxand at most 16 months"13:32
*** lbragstad has joined #openstack-tc13:33
jbrycei think those were too loosely defined, but we can talk about it on the call too13:33
jbryceunless you just want to move to calendar terms and then it all is a lot easier = )13:37
smcginnisWhat about "within +/- 2 months of the OpenStack release cycle"? That's probably too loosely defined too.13:39
ttxyeah... I feel like capping it is good enough for teh bylaws13:41
ttxThe idea is to remove as much as we can from bylaws while keeping safeguards13:41
*** tobberydberg has joined #openstack-tc13:44
fungicdent: right, i figured dispute mediation provided by the board of directors was just one more thing we can define in our charter. in my opinion the less the bylaws impose on the tc's self-governance choices the better13:45
cdentfungi: is there an alternative already planned or is that something for the todo list?13:45
fungicdent: it was something i planned to jump on _if_ the board was in favor of that change13:46
ttxyeah, let's see how that one flies first13:46
cdentcool, thanks13:46
fungibut for me the biggest improvement, by far, is the declaration that the tc member policy can be changed by a vode of the board of directors now instead of a vote of at least 10% of the entire foundation membership13:46
fungis/vode/vote/13:46
fungiwell, can be changed by a vote of the board of directors and tc members together, obviously13:47
fungito prevent them changing it in ways we don't approve13:47
fungibut we no longer have to muster a vote of the foundation membership to fix a typo (after this next vote, assuming it passes)13:48
smcginnisThat would be nice.13:48
mnasertc-members: reminder that board meeting call is happening shortly in a few minutes13:53
mnaserhttps://openstack.webex.com/openstack/k2/j.php?MTID=t8c39af405243e813e98c15a011ac500713:53
*** tellesnobrega has joined #openstack-tc13:54
toskyhi all, we are going to have the sahara meeting in 7 minutes, would anyone from the TC like to jump in for the cloud vision discussion, or do you prefer us (sahara) to discuss it here at some point?13:54
cdenttosky: I suspect people can jump in, where's the meeting?13:55
cdentevrardjp: you might be interested in ^13:56
tosky#openstack-meeting-3 in 4 minutes13:56
TheJuliaof course webex breaks on me :(14:00
fungii use the telephone14:00
TheJuliaI need to put in a cell repeater for the office. Cinder block walls and absurdly far away cell towers14:01
fungiyeah, that's rough14:02
fungihttp://lists.openstack.org/pipermail/foundation/2018-October/002635.html14:04
fungihttps://wiki.openstack.org/wiki/Governance/Foundation/25Oct2018BoardMeeting14:04
fungihttps://etherpad.openstack.org/p/UnofficialBoardNotes-Oct25-201814:04
fungialso #openstack-board channel14:05
evrardjpcdent: thanks for the ping14:05
zanebtosky: joined14:05
toskythanks14:05
ttxE_TOOMANYJULIAS14:08
TheJuliaheh14:08
TheJuliaThis is not a bad thing...14:08
ttxYes, a good problem to have14:08
cdentfungi: etherpad is doing its slowness thing _right now_, in case you were looking for that14:11
fungicdent: interesting, thanks! i agree it's slow again so my upgrades to the trove instance for it don't seem to have fixed that14:12
fungiand just as before, system cpu utilization has just started spiking up as of 14:00z14:13
smcginnisIt seems really random for me over the last day or so. Some times loading an etherpad takes a veeery long time, sometimes it's instant.14:13
lbragstadis there is link to the slides for this meeting?14:15
smcginnislbragstad: See the attachment here - http://lists.openstack.org/pipermail/foundation-board/2018-October/000449.html14:16
lbragstadaha - perfect, thanks smcginnis14:17
fungismcginnis: yesterday it cleared up because i had to restart the etherpad nodejs process. i think it's memory pressure on the server looking at cacti. etherpad seems to use a large amount of cache memory even more or less at rest14:18
fungiso this may be fallout from last week's upgrade from ubuntu 14.04 to 16.0414:18
smcginnisSounds more like a java app.14:18
fungifully in favor of constraining the osf board to say it can't approve software projects which aren't open source14:21
cmurphyo.0 is that a risk?14:21
ttxcmurphy: probably not, which is why the vagueness in the proposed change is completely superfluous14:23
ttxfungi: we should have caught that in our read a few hours ago14:23
smcginnisI originally thought they were suggesting that something other than software could be managed by the OSF.14:24
smcginnisNot that we would do proprietary software.14:24
* cmurphy hopes it's puppies14:25
fungittx: yeah, i'm disappointed i didn't think of that too14:25
ttxopen puppies are a bit messy14:25
smcginniscmurphy: :)14:25
smcginnisttx: Eeww14:25
fungismcginnis: yeah, i'd like to leave the option for non-software projects without also opening the door for the possibility of the board approving software projects which aren't open source14:26
smcginnisfungi: ++14:26
TheJuliacmurphy: kittens may be more fun. :)14:26
zanebhow out of touch is this guy?14:35
* lbragstad goes back to taking notes in vim - i can update the etherpad later though 14:36
smcginnisfungi: I would expect most members not to be on IRC, unfortunately.14:40
fungismcginnis: a few do show up in the output of /names14:40
-openstackstatus- NOTICE: Zuul and Nodepool services are being restarted to migrate them to a new Zookeeper cluster. THis brings us an HA database running on newer servers.14:40
TheJulialbragstad: was that you typing in etherpad?14:42
TheJulialbragstad: disregard last question14:42
ttxzaneb: quite14:43
zanebshould we require a supermajority of the TC to change the TC member policy?14:48
ttxmaybe yes14:49
ttxWe could overload that in our charter though14:49
TheJulia++14:50
ttx(or we can ask for that in our official feedback)14:50
ttx(pretty sure teh BoD would not care)14:50
TheJuliaSo far everything seems cleanup + Open Infrastucture official governance which I don't feel we really have or should have any official voice in14:51
ttxthe TC member policy appendix is next14:52
ttxTheJulia: you might have more opinion on that14:52
TheJuliaYes, reading now14:52
mnaser..but14:53
mnaserwe're going to get back to it14:53
mnaserthis is just the first presentation14:53
mnaserquestion mark14:53
ttxmnaser: yes14:53
mnaser¯\_(ツ)_/¯14:54
fungizaneb: if we want to flag parts of the charter which require a vote of the tc electorate (not just the tc) we can even do that14:55
TheJulia2(a) changes seem reasonable14:56
fungia bunch of it is just cleaning up no-longer-relevant cruft14:56
*** tobberydberg has quit IRC14:56
ttxIt's all about giving us flexibility to align elections on slightly-longer/slightly-smaller cycles14:56
ttxwith a cap in that flexibility14:56
cdenttc member for life!!!14:57
mnaserfor lyf**14:57
fungiyes, the added/altered bits of 2a are because, in fact, we've probably already violated the way it's currently worded on multiple occasions14:57
ttxfungi: hmm, the wording changed again14:57
fungioof14:58
smcginnisYep14:58
ttxwording is contradictory now :/14:58
TheJuliabreaking 2a into two parts might make more sense15:00
TheJuliaI read it as really just allowing routing around the cycle boundary issue15:00
zanebI assume 16 months was chosen because it's 2x 8 months?15:03
*** tobberydberg has joined #openstack-tc15:04
jbrycezaneb: correct15:05
zanebplease let make the bylaws depend on the release cycle. the last thing we need is release cycles defined in the bylaws15:05
zaneb*don't* let15:06
cdentgood point zaneb . there may come a time when we never have formal releases but still exist15:06
*** ricolin has joined #openstack-tc15:06
evrardjpI agree with zaneb15:07
fungia lot of this is also being said in #openstack-board15:07
fungibut a lot of people don't seem to be in there15:07
cdentoh hey, it's office hours15:07
evrardjpthat would leave room to office hours15:07
evrardjpcdent: haha15:07
zaneboh. I am there but I was not watching :D15:07
smcginniszaneb: That's a fair point. Sounds like it would be too difficult to define in the bylaws anyway.15:09
TheJuliaI'm not sure I can do office hours and keep track of discussion :)15:09
TheJuliaI concur that we don't want that, but we want intent codified. The original was explicitly based upon the original expectations, so a happy medium is really required imho15:10
evrardjpcould we ask that these meeting do not overlap with our office hours next time?15:11
cdentevrardjp: in the past the overlap has been convenient because it means that there's already governance-related chunk of time set aside15:11
TheJuliaEh, the board is going to do what the board wants and what is reasonable time. This does happen to be a moderately reasonable time given the curse of time zones15:11
cdentas in: I'm more likely to attend the board meeting at this time than any other15:12
smcginnisI've unfortunately gotten somewhat used to overlapping attention demands.15:12
*** tobberydberg has quit IRC15:13
cdentdon't normalize your oppression smcginnis15:13
TheJuliaheh15:14
* fungi is triple-booked between this, the board call, and the security sig meeting15:14
fungii agree being this used to overlapping attention demands is unfortunate15:14
*** jamesmcarthur has joined #openstack-tc15:15
fungioh, and infra maintenance happening now too, which i've basically been unable to pay attention to/help with as a result :/15:15
TheJuliaWell this may be interesting discussion now15:16
smcginnisWhen do we get our direct neural cortex fiber optic implants.15:16
TheJuliasmcginnis: Next week, Also when all forms of payments are credits.15:17
smcginnis\o/15:17
smcginnisAnd when we switch to no timezone, no daylight savings time. And metric.15:17
fungiand all restaurants are taco bell15:17
TheJuliaand the ocean is now much closer due to sea level rise15:18
smcginnisBeachfront property!15:18
TheJuliaOh, and we're doing GeoEngineering!15:18
evrardjpsmcginnis: sounds like good demands.15:19
ttxlegalese grammar question now15:19
evrardjptell me when your employer provides it, please.15:19
smcginnis:)15:20
* TheJulia wonders if there is a graph or data points that can help drive the current discussion15:25
*** tobberydberg has joined #openstack-tc15:25
-openstackstatus- NOTICE: The Zuul and Nodepool database transition is complete. Changes updated during the Zuul outage may need to be rechecked.15:32
evrardjpFor people interested, here is the link to the profile of Horace Li, China Community Manager @OpenStack Foundation: https://www.openstack.org/community/members/profile/98596/horace-li (If I am not mistaken) :)15:34
fungievrardjp: yep! he's an awesome person. see also https://www.openstack.org/foundation/staff15:46
fungithe openstack logos under the headshots all link to the corresponding member profiles15:47
evrardjpfungi: I thought it was a good thing to share for the office hour :)15:48
fungiabsolutely!15:48
*** e0ne has quit IRC15:59
*** dtantsur is now known as dtantsur|afk16:22
*** mnaser has quit IRC16:26
*** mnaser has joined #openstack-tc16:26
*** jpich has quit IRC16:28
fungihrm, i just noticed that the osf publishes a list of openstack tc members on their marketing site at https://www.openstack.org/foundation/tech-committee/16:37
fungidoes it rub anyone else the wrong way that we have employer affiliations listed there? we expressly avoid listing things like that at https://governance.openstack.org/tc/#current-members16:38
cmurphysome companies allow employees time to be on the tc in part because that page gives them bragging rights16:41
dtroyerfungi: it does, until the value of $EMPLOYER comes in to play for counting reasons16:41
cdentaw man, my bagpuss pic is not showing up :(16:42
cdentbut i agree, I don't want my company affiliation showing up there16:42
cdentalso, it needs an update16:42
cdent(since election)16:43
fungiyeah, for the other projects at https://www.openstack.org/foundation/ their governing bodies just link to their individual project governance docs16:43
fungiwhich i guess so far is the architectural committee for kata containers16:44
fungiand the working committee16:44
dtroyerthe stx TSC isn't quite fully-formed yet but our docs are live!  :)16:45
fungiclarkb pointed out to me elsewhere that the likely reason kata lists organizational representation there is due to being initially appointed by those organizations who were given a seat on those governing bodies16:46
fungithough that was historical. at least some of those have been elected by their contributors since16:46
dtroyerI think that is unavoidable in the bootstrapping phase, having been going through that now myself.  I hope to see the day when that shift can happen like it did for OpenStack16:48
* zaneb must be coming up to the 10th anniversary of that profile pic17:00
fungijbryce also pointed out elsewhere that because we have a maximum proportional affiliation for the tc, we need to publicly list our affiliations somewhere. for me, i think it's more the mixing of that information with bios and headshots which sends a conflicting message (for the people who do manage to stumble across it)17:03
*** jamesmcarthur has quit IRC17:06
*** jamesmcarthur has joined #openstack-tc17:07
*** jamesmcarthur has quit IRC17:08
*** diablo_rojo has joined #openstack-tc17:26
*** zaneb has quit IRC17:53
*** jamesmcarthur has joined #openstack-tc17:54
*** cdent has quit IRC17:56
*** jamesmcarthur has quit IRC17:58
*** eumel8 has joined #openstack-tc18:04
*** zaneb has joined #openstack-tc18:07
*** whoami-rajat has joined #openstack-tc18:10
*** jamesmcarthur has joined #openstack-tc18:10
*** jamesmcarthur has quit IRC18:13
*** jamesmcarthur has joined #openstack-tc18:23
*** lbragstad has quit IRC19:43
*** lbragstad has joined #openstack-tc19:43
*** irclogbot_3 has joined #openstack-tc20:00
*** mriedem has joined #openstack-tc20:03
*** ricolin_ has joined #openstack-tc20:09
*** ricolin has quit IRC20:12
*** irclogbot_3 has quit IRC20:22
*** ricolin_ has quit IRC20:23
evrardjpfungi: I am not sure to understand what is the conflicting message to you? The photo, the bio, or the affiliation?20:27
smcginnisSeeing my photo anywhere is always conflicting. :)20:37
fungiphoto and bio are about getting to know the tc member, who they work for is more of a technicality which should only matter when it comes to making sure we aren't violating the 50% rule in the bylaws20:58
openstackgerritMerged openstack/governance master: Add cells charm and interfaces  https://review.openstack.org/60886620:59
*** irclogbot_3 has joined #openstack-tc21:13
*** jamesmcarthur has quit IRC21:37
*** jamesmcarthur has joined #openstack-tc21:44
*** jamesmcarthur has quit IRC21:48
*** mriedem has quit IRC22:21
*** tosky has quit IRC22:45

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