Thursday, 2019-07-18

*** jamesmcarthur has quit IRC00:06
*** jamesmcarthur has joined #openstack-tc00:08
*** jamesmcarthur has quit IRC00:09
*** jamesmcarthur has joined #openstack-tc00:09
*** iurygregory has quit IRC00:17
*** jamesmcarthur has quit IRC00:33
*** jamesmcarthur has joined #openstack-tc00:33
*** jamesmcarthur has quit IRC00:39
*** jamesmcarthur has joined #openstack-tc01:09
*** jamesmcarthur has quit IRC01:15
*** whoami-rajat has joined #openstack-tc01:31
*** jamesmcarthur has joined #openstack-tc01:40
*** jamesmcarthur has quit IRC02:54
*** jamesmcarthur has joined #openstack-tc02:55
*** jamesmcarthur has quit IRC02:59
*** redrobot has quit IRC03:32
*** jamesmcarthur has joined #openstack-tc03:35
*** Guest99405 has joined #openstack-tc03:39
*** Luzi has joined #openstack-tc05:09
*** jamesmcarthur has quit IRC05:10
*** logan- has quit IRC06:00
*** logan_ has joined #openstack-tc06:01
*** logan_ is now known as logan-06:01
*** sapd1 has quit IRC06:37
*** asettle has joined #openstack-tc07:47
*** tosky has joined #openstack-tc08:31
*** iurygregory has joined #openstack-tc08:46
*** tdasilva_ has quit IRC09:25
*** tdasilva_ has joined #openstack-tc09:26
asettleo/ hola09:37
*** tdasilva_ has quit IRC09:47
*** tdasilva_ has joined #openstack-tc09:47
*** jamesmcarthur has joined #openstack-tc10:15
*** thiago__ has joined #openstack-tc10:15
*** tdasilva_ has quit IRC10:17
*** jamesmcarthur has quit IRC10:19
*** whoami-rajat has quit IRC10:30
*** thiago__ has quit IRC12:26
*** thiago__ has joined #openstack-tc12:27
*** thiago__ has quit IRC12:33
*** thiago__ has joined #openstack-tc12:33
*** tdasilva_ has joined #openstack-tc12:35
*** thiago__ has quit IRC12:38
*** Guest99405 is now known as redrobot13:13
*** beekneemech has joined #openstack-tc13:36
*** bnemec has quit IRC13:37
*** tdasilva_ has quit IRC13:41
*** tdasilva_ has joined #openstack-tc13:42
*** Luzi has quit IRC13:52
*** whoami-rajat has joined #openstack-tc13:55
*** tdasilva_ has quit IRC14:09
*** tdasilva_ has joined #openstack-tc14:09
mnaserasettle: welcome back? :)14:10
asettleThanks mnaser :D14:10
*** tdasilva_ is now known as tdasilva14:15
openstackgerritMerged openstack/project-team-guide master: Mention the new cycle-automatic release model  https://review.opendev.org/66654814:18
*** jamesmcarthur has joined #openstack-tc14:19
*** iurygregory has quit IRC14:23
*** jamesmcarthur has quit IRC14:23
*** jamesmcarthur has joined #openstack-tc14:24
*** ricolin_ is now known as ricolin14:34
*** lbragstad has joined #openstack-tc14:36
*** iurygregory has joined #openstack-tc14:40
*** jamesmcarthur has quit IRC14:43
fungioffice hour, folks15:01
lbragstado/15:01
ricolino/15:01
fungi(which doubles as a good excuse for me to procrastinate mowing the lawn for a bit)15:01
tobberydbergHello folks! o/15:03
ricolinfungi, let's keep this office hour as long as it can for you;)15:03
fungi;)15:03
ricolintobberydberg, regarding public cloud WG->SIG, what's the next plan for your group?15:05
*** tdasilva has quit IRC15:05
tobberydbergI have a question for you ... regarding the irc_meetings repo ... public cloud wg have become public cloud sig ... about to puha a change for that, at the same time change the storage directory in eavesdrop from "publiccloud_wg" to "publiccloud_sig" to have that matching ... but I don't want to loose all old logs15:05
asettleo/15:05
*** tdasilva has joined #openstack-tc15:05
tobberydbergricolin ... plan right now is to continue our discussions regarding "billing implementation proposal" as its called right now (just a meeting around that)15:06
fungitobberydberg: normally you just note somewhere what the link to the old logs is15:06
fungithe html is statically generated and includes the meeting name in a number of references which would need in-place editing across the entire corpus of logs15:07
zanebo/15:07
fungitobberydberg: also the links to the meeting logs which get echoed in-channel would need updating in old copies of the logs (or would 404)15:07
fungiwhen the infra team changed its name from the ci team, we simply included a hyperlink in our agenda to the old meeting logs directory15:08
tobberydbergfungi aha, ok ... so old logs are not deleted even if it doesn't have a matching "meeting" in the repo then15:08
fungiright, they're retained forever15:08
tobberydbergperfect, fine with that15:08
fungiwe still have logs of the old "openstack" project meeting from 2011 or 201215:08
tobberydberg+115:09
ricolinfungi, so is there policy for how long we will keep logs for public cloud WG, once all move to SIG15:09
fungiand there have been multiple occasions where i've found those handy too (in digging into very early project history)15:09
tobberydbergI'll suggest that change for this soon then. Thanks fungi15:09
fungiricolin: forever15:09
ricolinfungi, super:)15:10
fungii see no reason to delete old meeting logs. that's project history, and can be valuable when trying to gain context for old decisions15:10
ricolintrue15:10
fungiwe don't delete old channel logs either15:10
fungii mean, our text and html versions of logs and corresponding minutes for all meetings we've ever held with the meetbot in ~7 years or so comes to just over a gigabte (uncompressed)15:13
ricolintc-members, as action report for U-release name wechat poll: WeChat poll for U release name (hosted by OpenStack official WeChat account, thanks Horace for that!) has ended, and here are the top five plus one from voting Urumqi (Urumqi city) 84 votes, Ussuri (Ussuri River) 78 votes, Ulansu (Ulansu sea) 37 votes, Ulanhot (Ulanhot city) 28 votes, Ulanqab (Ulanqab city) 18 votes, and one extra (6th) is Urad (Urad Middle Banner) with 15 votes15:13
fungiby comparison, a month of our ci job logs ot 10 terabytes15:14
fungier, is 10 terabytes15:14
fungiricolin: that looks like a great list!15:14
ricolinfungi, I do hope we can keep those logs longer so I don't have to recheck sometimes;)15:15
jrollricolin: nice!15:15
asettlethanks for the update ricolin15:16
fungiTheJulia: if you're around, i'd like to figure out whether the way i phrased things in 670741 is really terrible and led you to misinterpret the thrust of the policy, or whether i've misunderstood your objection to the proposed policy15:20
fungi(see review comments i responded with)15:20
*** tdasilva_ has joined #openstack-tc15:26
*** tdasilva has quit IRC15:28
lbragstadthanks ricolin15:31
ricolintc-members, FYI I did set the title of poll from wechat to `pick up some suggest name list for TC's consideration` to make sure TCs got the control of the final list, so we still need to discuss and voting to add other options or remove options15:50
mnaseri personally don't mind/care whatever ends up being selected.  if it's somewhere in china, it qualifies15:51
fungisame for me15:52
jrollditto15:53
fungiwe're already having to dance around the lack of a name for the next cycle in governance docs, no doubt others are having similar challenges... the sooner we have any name for it the better in my opinion15:53
*** beekneemech has quit IRC15:57
*** bnemec has joined #openstack-tc15:58
*** iurygregory has quit IRC16:01
ricolinthe poll didn't includes any name that do not meet the criteria, so those names still need to have chance to vote by TCs?16:02
ricolinI'm talking about https://wiki.openstack.org/wiki/Release_Naming/U_Proposals#Proposed_Names_that_do_not_meet_the_criteria.3B_.E4.B8.8D.E7.AC.A6.E5.90.88.E8.A1.A8.E5.87.86.E7.9A.84.E5.90.8D.E7.A7.B0.E6.8F.90.E5.90.8D16:03
mnaserricolin: i'm curious, is there any odd cultural connotations from some of those proposed names (just thinking back to previous releases where we messed up a little bit :))16:05
mnaseri really like Ussuri16:06
mnaserpersonally :P16:06
ricolinmnaser, you mean the propose name from the wechat poll or from the wiki page?16:07
mnaserricolin: the proposed names from the wchat poll16:07
ricolinI mean, the name is from wechat groups, but IMO we still need to avoid any issue/concerns globally16:11
ricolinmnaser, Ussuri is definitely fine to use:)16:11
ricolinI still like unicorn the best TBH:)16:11
ricolins/the name/the name list/16:12
mnaseraha, i would like us to pick up something relevant to the chinese community tho16:15
openstackgerritRico Lin proposed openstack/governance master: Add team format differentiate document  https://review.opendev.org/66809316:19
ricolinasettle, ^^^16:19
ricolinasettle, I update the patch base on your comment, except for the having a `is responsible for` list, since I don't record to have such list anywhere in current TC document16:20
ricolinmaybe we should have one?:)16:20
* zaneb would also vote for Ussuri16:43
zanebbtw Ussuri is misspelled on the wiki page IIUC16:46
fungizaneb: given your objection to broadening the qualifying area to all of china, i take it ussuri is within two prefectural borders of the shanghai administrative area?16:46
zanebfungi: it's not but I'd be ok with adding it as a special case, as is our prerogative16:47
fungiahh17:03
funginoted17:03
openstackgerritMerged openstack/governance master: Add empty deliverables list to (retired) refstack  https://review.opendev.org/67114117:11
*** tosky has quit IRC17:17
*** tdasilva_ is now known as tdasilva17:45
*** aprice has quit IRC17:45
*** hogepodge has quit IRC17:45
*** hogepodge has joined #openstack-tc17:47
*** aprice has joined #openstack-tc17:47
*** irclogbot_0 has quit IRC18:07
*** altlogbot_2 has quit IRC18:07
*** irclogbot_1 has joined #openstack-tc18:09
*** altlogbot_3 has joined #openstack-tc18:09
openstackgerritMerged openstack/governance-sigs master: Add Matt Oliver to FC SIG Chair List  https://review.opendev.org/66771518:20
TheJuliafungi: sorry, my life has absolutely consumed :(18:29
TheJuliaI'm around and have... some remaining braincells today18:30
fungino sweat, whenever you have time18:59
*** lbragstad has quit IRC19:02
*** ricolin_ has joined #openstack-tc19:03
*** ricolin has quit IRC19:05
TheJuliafungi: so the way I read it, which was completely without context as may would surely read it once codified, was that the resolution was conveying that perceived inactive repositories are considered repositories that are actively not releasing as part of19:26
TheJuliaeach release cycle, at which point they would be ejected from governance for not releasing and removed from the openstack namespace and ultimately declared dead/archived. This was first from reading the first two paragraphs and re-enforced once I reached the last ?two? of paragraphs.19:26
fungihuh19:27
fungiit has nothing to do with whether projects release nor what projects we remove from governance19:27
fungithe entire point of the resolution is that *if* a deliverable repository is removed from governance for any reason, the copy in the openstack git namespace needs to follow the usual repository retirement process19:29
TheJulianot projects but repositories that belong to projects is the way I read it19:29
fungiyeah, that resolution isn't saying to remove any particular repositories from governance, just saying what happens when a repository is removed19:29
TheJuliaIf that is simply the purpose of the resolution... then that seems like a lot to parse and grok :(19:29
fungithe majority of the text is attempting to provide background for the decision, and cover the grandfathering and grace period before the decision goes into effect19:30
TheJuliaI will totally grant that it is easy for me to have a skewed perception right now with all the stressors that exist at the moment, but I read that and my jaw quite literally dropped while reading it.19:31
fungii reread it several times over and can't figure out what wording in there would have given that impression, but i'm willing to try rewriting it from scratch and see if it comes out any clearer a second time19:32
TheJuliaI can go back and re-read it, but it won't be for a day... or two19:33
fungithere no hurry--take you time19:33
TheJuliait feels silly to admit this, but I may have also lost or two while reading it which may have caused me to come away thinking something skewed19:33
zanebfungi: if you're rewriting, I think it would help to explicitly separate it into sections like "Background", "Now Hear This", &c.19:34
fungithere are also some good suggestions in there from other reviewers already on places where things could be reworded a bit to make it clearer, so maybe that'll help19:35
fungizaneb: makes sense. also one challenge i realized when writing it is that it's a resolution amending an implicit/de facto policy19:35
fungii wonder if it should be rewritten to codify the existing policy too and not just the change in behavior19:36
fungiwe don't currently have any hard policy that says repositories which cease development are retired following the process recommended in the opendev infra manual, we just do it19:37
fungiso it may make sense to write that down19:37
TheJuliasectioning it would really delineate things and would have caused me to at least go "wait, did I get that right?"19:37
fungiyep, it's a bit rambling. totally agree19:38
fungishould the rationale go first? or the policy first?19:38
*** e0ne has joined #openstack-tc19:38
fungii'm thinking start with some semblance of legalese policy text, and then have a background/context section after it19:39
TheJuliahmmmmmm19:39
TheJuliaThat is a good question which I am not sure has a good answer :\19:39
TheJuliaThat would likely be best, as long as nobody needs to pull out their latin translation books :)19:40
fungireason being the policy is the important part of the document, so if people read no further than that at least they got what the rule is19:40
TheJulia++19:40
fungiand yeah, i'll dispense with the wherefores and hithertos19:41
fungiplain speak19:41
*** whoami-rajat has quit IRC19:44
TheJuliaWell, latin can always be useful :)19:45
fungijust not for this ;)19:49
TheJuliaheh19:50
*** e0ne has quit IRC21:17
*** beekneemech has joined #openstack-tc21:38
*** beekneemech has quit IRC21:38
*** bnemec has quit IRC22:03
*** bnemec has joined #openstack-tc22:13
*** bnemec has quit IRC22:42
*** bnemec has joined #openstack-tc22:43
*** tdasilva has quit IRC23:19

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