Wednesday, 2020-07-08

*** tetsuro has joined #openstack-tc00:02
*** markvoelker has joined #openstack-tc00:21
*** tetsuro has quit IRC01:32
*** ricolin has joined #openstack-tc01:40
*** tetsuro has joined #openstack-tc01:41
*** tetsuro has quit IRC01:43
*** tetsuro has joined #openstack-tc01:44
*** tetsuro has quit IRC03:11
*** markvoelker has quit IRC03:40
*** markvoelker has joined #openstack-tc04:03
*** markvoelker has quit IRC04:07
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-tc04:33
*** dklyle has quit IRC06:03
*** markvoelker has joined #openstack-tc06:04
*** markvoelker has quit IRC06:09
*** ianw is now known as ianw_pto06:38
*** markvoelker has joined #openstack-tc06:43
*** markvoelker has quit IRC06:48
*** tosky has joined #openstack-tc07:33
*** ralonsoh has joined #openstack-tc07:47
*** tkajinam has quit IRC08:23
*** diablo_rojo has quit IRC08:41
*** e0ne has joined #openstack-tc10:12
*** markvoelker has joined #openstack-tc11:34
*** markvoelker has quit IRC11:39
*** ijolliffe has joined #openstack-tc12:53
*** adriant has quit IRC13:05
*** adriant has joined #openstack-tc13:06
*** gmann has joined #openstack-tc13:08
gmanno/13:09
*** jungleboyj has joined #openstack-tc13:16
jungleboyjo/13:16
jungleboyjJust saw that IRCCloud is down.  :-(13:17
*** lpetrut_ has joined #openstack-tc13:21
njohnstono/13:23
jungleboyjWonder how many people are off because of IRCCloud outage.13:24
gmannjungleboyj there are always outage with irccloud :)13:30
jungleboyjgmann, I haven't had that many.  Only a couple in the 3 years I have been using it.13:40
*** dklyle has joined #openstack-tc14:11
*** lpetrut_ has quit IRC14:28
*** gmann has quit IRC14:38
*** ijolliffe has quit IRC15:09
*** ijolliffe has joined #openstack-tc15:15
*** diablo_rojo has joined #openstack-tc16:03
*** ijolliffe has quit IRC16:24
*** gouthamr has quit IRC16:26
*** gmann has joined #openstack-tc16:36
*** ijolliffe has joined #openstack-tc16:37
*** gouthamr has joined #openstack-tc16:52
*** markvoelker has joined #openstack-tc16:53
*** markvoelker has quit IRC16:53
*** ricolin has quit IRC18:00
*** e0ne has quit IRC18:03
*** ralonsoh has quit IRC18:07
smcginnisI wonder if we should have an OpenStack-wide discussion or common guidelines around https://review.opendev.org/#/c/740013/19:08
fungithis is basically how it's happened in the past, one or two interested projects take the lead and work toward something, then out of those efforts emerges a standard which other projects can follow19:13
fungiusually coming up with guidelines before anyone's attempted to follow them has resulted in design by committee madness19:14
smcginnisTrue.19:14
smcginnisI just worry about common conventions. Like that version of the patch recommends changing blacklist to allowlist, which is conceptually completely opposite of what everyone else is tending to do.19:15
smcginnisSo avoiding things like that is my main concern. Having some kind of common "here are some alternatives we recommend, you decide what is right for your project and context" would help.19:15
fungiwell, the actual implementations weshay linked in his e-mail are using "skiplist" and "skipped"19:15
fungiproblem is, words have multiple meanings (i mean yes that's also the core problem in this case but beyond that), so what words are appropriate replacements will depend highly on context19:17
*** gmann_ has joined #openstack-tc19:17
fungiin some cases "blacklist" is more appropriately replaced by "block" and in others "skip" and in still others "disallow" and so on19:17
fungiultimately, i think the best a spec like that can provide is an array of suggestions, but the actual implementations will be usage-specific19:18
smcginnisHence my last comment above.19:18
*** gmann has quit IRC19:18
*** gmann_ is now known as gmann19:18
fungii expect bogdan's prose there was just missing some words. i doubt he literally meant replacing "blacklist" with "allowlist" makes sense. replacing "whitelist" with "allowlist" might or replacing "blacklist" with "denylist"19:21
gmannwhitelists might be less-common but blacklist is very commonly  known and used word.19:27
*** masayukig has joined #openstack-tc19:29
fungisure, but there is interest at least from some of our community in avoiding it where possible19:30
smcginnisI can provide a list of other communities that are actively working on it too.19:31
toskyI'd like to point out allow/deny<foo> is commonly used too (hosts.allow/hosts.deny)19:31
fungiyep, and some which have already done19:31
*** mnaser has joined #openstack-tc19:32
gmannfor internal code we can do but public interfaces is much difficult or should-not-change, like most of the testing tools use black*list* for excluding tests for loading/run/log etc19:32
fungitosky: sure, in contexts where things are being allowed and denied they are commonly used. blacklist and whitelist are used in other situations where things are not allowed and denied though (they may be included and elided, or used and unused, or applied and skipped, or...)19:32
fungigmann: everything *can* be changed, but i agree that api backward compatibility is important and changes there are not at all low-hanging fruit19:33
*** aprice has joined #openstack-tc19:34
gmanni mean change-without-break :)19:34
fungiand would require multiple cycles of deprecation most likely19:34
fungithey could still be changed, but it would not be easy nor immediate19:34
*** TheJulia has joined #openstack-tc19:35
gmanntempest has lot of deprecated decorator/method and we thought of removing that but it break lot of users/plugins so not worth to do19:35
*** jungleboyj_ has joined #openstack-tc19:35
fungii also think that marking those terms as deprecated is still useful, even if their usage can't be removed for a very long time due to needing to maintain backward compatibility19:35
gmannfungi: believe me, deprecation things for these kind of changes does not work in most case and end up breaking now so blame that you keep breaking us and then fix. very less usage move to new things during deprecation phase.19:37
fungiwhy would deprecation break anything?19:37
gmanni mean when you remove the things after deprecation19:38
fungiremoving support for api methods of course breaks things, but simply marking/documenting as deprecation doesn'y19:38
fungidoesn't19:38
fungithat's literally what i mean, we can say they're deprecated, introduce replacements, but not actually remove them, and that's still useful19:39
gmannTempest is good example of trying such improvement and called as always-breaking-users even we are changes internal things(but those were used as external).19:39
gmannfungi: yeah that is how we did in tempest also. that is better19:39
fungie.g. "don't use the /blacklist method, this has been replaced by /denylist" but then still leave in all the plumbing for /blacklist and still test that it works19:40
*** rpittau has joined #openstack-tc19:40
fungi(i acknowledge that it does increase the test surface area)19:40
gmannbut honestly saying these master/slave and other renaming stuff like blacklist things for me is not much valuable then effort they need. Those are just code name not English as language names. we should not translate code things into English as standard language/convention grammar etc. as long as it does not hurt any culture or not abusing word its fine :)19:43
*** tonyb[m] has joined #openstack-tc19:44
gmannbut may be its just me.19:45
*** jrosser has joined #openstack-tc19:48
*** csatari has joined #openstack-tc19:49
fungii've struggled with this dilemma too, and i understand19:52
*** rm_work has joined #openstack-tc19:53
fungithe upshot of it is that there are people who are made uncomfortable or even offended by these words, regardless of their usage context, etymology, multiple meanings and so on... we should't deny that they feel whatever they feel, and if enough people are uncomfortable then making changes may be warranted19:54
fungius knowing why certain words were chosen and that they were not intended to be taken in a certain way doesn't prevent people from feeling whatever they're going to feel when they encounter them19:55
*** jbryce has joined #openstack-tc19:55
*** ildikov has joined #openstack-tc19:56
fungiand it would be better to try to avoid making someone feel bad than to have to explain to them why they shouldn't feel bad19:56
gmannhumm, those are fair point but that is also true that people uncomfortable on changing the existing are not counted or spoken enough :)19:57
*** gagehugo has joined #openstack-tc19:57
*** tdasilva has joined #openstack-tc19:59
fungiwell, people who are made uncomfortable by software changing are going to have a hard time in openstack regardless ;)20:01
gmannhehe, especially our API users.20:02
*** knikolla has joined #openstack-tc20:06
*** johnsom_ has joined #openstack-tc20:10
*** mwhahaha has joined #openstack-tc20:10
*** coreycb has joined #openstack-tc20:13
*** samueldmq has joined #openstack-tc20:16
*** mnaser is now known as mnaser|ic20:52
*** mnaser|ic has quit IRC21:08
*** mnaser|ic has joined #openstack-tc21:08
*** mnaser|ic has quit IRC21:08
*** mnaser|ic has joined #openstack-tc21:08
*** mnaser|ic is now known as vexxhost21:08
*** gouthamr has quit IRC21:09
*** gouthamr has joined #openstack-tc21:11
*** vexxhost is now known as mnaser21:14
*** mnaser is now known as mnaser|ic21:14
*** gouthamr_ has joined #openstack-tc21:15
*** johnsom_ is now known as johnsom21:19
*** johnsom has joined #openstack-tc21:19
*** ijolliffe has quit IRC21:33
*** slaweq has quit IRC21:54
*** slaweq has joined #openstack-tc21:55
*** slaweq has quit IRC22:00
*** tosky has quit IRC22:30
*** tkajinam has joined #openstack-tc22:58
*** ijolliffe has joined #openstack-tc23:10
*** ijolliffe has quit IRC23:23
*** evrardjp has quit IRC23:25
*** evrardjp has joined #openstack-tc23:26
*** mnaser|ic has quit IRC23:38
*** mnaser|ic has joined #openstack-tc23:38
*** mnaser|ic has quit IRC23:38
*** mnaser|ic has joined #openstack-tc23:38
*** mnaser|ic is now known as mnaser23:38

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!