Tuesday, 2019-06-25

*** zaneb has quit IRC00:15
*** zaneb has joined #openstack-tc00:15
*** wxy-xiyuan has joined #openstack-tc01:08
*** whoami-rajat has joined #openstack-tc02:07
*** diablo_rojo has quit IRC02:17
*** jaypipes has joined #openstack-tc02:36
*** lbragstad has joined #openstack-tc03:18
*** mnaser has quit IRC03:19
*** mnaser has joined #openstack-tc03:20
*** gagehugo has quit IRC03:22
*** gagehugo has joined #openstack-tc03:22
*** gagehugo has quit IRC03:25
*** gagehugo has joined #openstack-tc03:28
*** lbragstad has quit IRC03:59
*** zaneb has quit IRC04:57
*** Luzi has joined #openstack-tc05:44
*** lpetrut has joined #openstack-tc06:01
*** e0ne has joined #openstack-tc06:29
openstackgerritTakashi NATSUME proposed openstack/governance master: Add Geographic Region for M release  https://review.opendev.org/66727406:43
*** altlogbot_2 has quit IRC06:46
*** altlogbot_3 has joined #openstack-tc06:56
*** e0ne has quit IRC06:57
evrardjpgood morning06:58
*** jpich has joined #openstack-tc07:07
gmannmorning07:08
*** iurygregory has joined #openstack-tc07:27
*** tosky has joined #openstack-tc07:28
*** iurygregory has quit IRC07:37
*** e0ne has joined #openstack-tc08:01
*** ricolin has joined #openstack-tc08:05
*** ricolin has quit IRC08:13
*** ricolin has joined #openstack-tc08:22
asettleo/08:56
*** jaosorior has joined #openstack-tc09:03
ricolinasettle, o09:04
ricolino/09:04
ricolintc-members please review https://etherpad.openstack.org/p/explain-team-formate-differentiate before I put the review patch up (also review it's graph too: https://imgur.com/FkrtN8s)09:07
*** jaosorior has quit IRC09:11
ttxohai09:12
ttxricolin: looking09:12
ttxricolin: so I'd start with "project teams" and then explain that "mission-oriented" is for groups who have a mission that goes beyond the scope of one specific project team.09:16
ttx(because project teams also have a "mission", so starting with "mission-oriented" is a bit confusing09:16
ttx)09:16
ttxricolin: is it fine if I just move it ?09:21
openstackgerritcaoyuan proposed openstack/governance master: Replace git.openstack.org URLs with opendev.org URLs  https://review.opendev.org/65501009:31
openstackgerritcaoyuan proposed openstack/governance master: Replace git.openstack.org URLs with opendev.org URLs  https://review.opendev.org/65501009:32
*** gmann has quit IRC09:57
openstackgerritAlexandra Settle proposed openstack/project-team-guide master: Reviewing the PTL document for accessibility  https://review.opendev.org/66569910:19
*** tdasilva_ has quit IRC10:24
asettleGracias, dhellmann10:27
asettleReviewing now10:27
*** gmann has joined #openstack-tc10:58
*** jaosorior has joined #openstack-tc10:59
*** jaosorior has quit IRC11:02
*** jaosorior has joined #openstack-tc11:03
*** e0ne has quit IRC11:05
*** e0ne has joined #openstack-tc11:05
*** iurygregory has joined #openstack-tc11:15
*** zaneb has joined #openstack-tc11:19
*** zaneb has quit IRC11:22
*** zbitter has joined #openstack-tc11:22
*** lbragstad has joined #openstack-tc11:33
*** tdasilva has joined #openstack-tc11:46
gmanncoreycb: i saw you are not adding/removing the py36 env from tox. if we have both version jobs IMO we should keep both version tox env for local testing - https://review.opendev.org/#/c/667094/111:52
smcginnisgmann: I responded on the patch, but I disagree with that. We should not make it a requirement that developers have both  py36 and py37 installed and have to run both targets by default.12:04
fungithere's a tox config directive which says that12:09
fungimissing_okay=true or something like that12:09
smcginnisYeah. A few repos have that set.12:09
fungiso that when you only have py37 installed and run tox with the default envlist, not having python3.6 installed doesn't report failure12:10
fungithough for my personal projects i just list py3 in my default envlist instead12:10
smcginnisBut do we want to just skip all py3 tests if neither are installed? I think we should just make it a requirement that py37 is needed for local dev testing.12:10
fungithere are pros and cons to each option there12:11
fungiare we targeting devs who are going to run tests locally and don't realize they are missing an appropriate version of python, in order to prevent them from being surprised when the ci system rejects their patch for a problem with the relevant python version(s)?12:12
smcginnisBoth will end up being tested anyway. I'd rather we not raise that bar even higher for someone new coming in and needing to figure out all these little expectations we've put on them.12:12
fungigot it, so better to list just one python version and tell everyone to make sure they (somehow) get that installed onto the operating system they're using even if their os doesn't provide that version (but provides another version we're also testing per the pti)?12:13
smcginnisThat would be my preference. If py37 is our high water mark, then I'd like to just shoot for that.12:13
fungiand devs running centos/rhel 8 which comes with python3.6 will be faced with a confusing error which indicates they need to get python3.7 from somewhere12:14
fungi(i'm not disagreeing, just pointing out the down side to that choice)12:14
smcginnisOr Bionic, or....12:15
smcginnisAt least we can be consistent with a clear statement of "You need to install py37" rather than "you might have the right versions you need but you might not so check this and check that" ;)12:15
fungiwell, bionic has packages for python 3.7 so that's at least easier to solve. i don't know whether rhel/centos 8 will have an easy way to get python3.7 installed without resorting to some separate environment management tooling12:15
fungibut sure, i can get behind that level of clarity if we're agreed that's what projects want12:16
jrolliirc it's pretty clear what's going on if the python version isn't installed12:17
fungibut at that point, why not say you need both 3.6 and 3.7 installed?12:17
* jroll runs tox on a local env real quick12:17
smcginnisfungi: I'm thinking wasted time. If it passes on py37, it more than likely will pass on py36. Can't really say the inverse.12:17
fungithat makes sense, sure12:18
jrollthis is how the tox run ends if something is missing: http://paste.openstack.org/show/753356/12:18
jrollthat seems fairly clear to anyone who has a clue about python12:18
fungisure12:18
gmanni am not clear why we are saying do not run py36 and py37 is enough and on other side gate test both version as mandatory12:18
gmannjroll: exactly12:19
jrollgiven how long some projects' unit tests take to run, I'd prefer to run *either* 3.6 or 3.7, but not both, locally12:19
jrolland trust the check jobs to find anything I missed12:19
smcginnisjroll: Exactly!12:19
gmannif i have both py version then 'tox' should run all of them for me if do not have any version then just it skip with error and proceed with next env12:19
*** tdasilva has quit IRC12:20
smcginnisThey already barely have enough patience to run it once. Now if we make them run it twice, it's even less likely that local tests will be run and they'll just push up patches and leave it to zuul.12:21
fungii think the point is that the ci system will run them both anyway, and the majority of problems for either will be caught by only running the newer one locally12:21
gmannin that case we can trust on jobs in all version. i find it useful when i need to debug the things which are failing on gate12:21
smcginnisIf they really care about one or the other, then they can run that specific target.12:21
fungiyeah, keep in mind that the default envlist is only relevant for people who run `tox` without specifying any testenv names at all12:22
gmannsure but looking at the tox default env list it make the impression that "py36 is not in list do not supported? or not needed?"12:22
gmannyeah.12:22
fungisupported versions ought to be reflected in the trove classifiers12:23
fungi(in setup.cfg or wherever)12:24
smcginnisYeah, if someone is looking at default targets in tox instead of setup.cfg to determine that, then there's going to be other issues with them. ;)12:24
*** tdasilva has joined #openstack-tc12:25
gmanntrue, i mean for local run. when we do not have py37 env 'tox' can run py36 instead otherwise it miss to test py3 .12:29
gmannas per goal doc also, proposal was to add the py37 in place of py34,py35. it does not say remove the py36 from default env list- https://governance.openstack.org/tc/goals/train/python3-updates.html12:30
openstackgerritIury Gregory Melo Ferreira proposed openstack/governance master: Add ironic-prometheus-exporter  https://review.opendev.org/66541412:31
smcginnisWell, we never had anything *add* py36 in the first place.12:32
*** ijolliffe has joined #openstack-tc12:34
*** mriedem has joined #openstack-tc12:50
asettletc-members - I know I'm the champ for the PDF goal but stephenfin and I are respectively away for the next coming weeks (me until the 17th of July, him until next week). Could someone please help us our and set up the storyboard?12:51
coreycbgmann: smcginnis i do like the idea of just having the latest py3x in the default tox targets. it's much friendlier for local tox runs.12:55
asettleI only ask due to rushing to get stuff done before I go on Thurs12:56
coreycbgmann: smcginnis: also, worth noting that the addition of py37 is a stretch goal. i've been interpreting that as having flexibility around it if a project wants.13:02
gmanncoreycb: make sense. that's what i was typing. if any project want both then we can keep. personally i want to keep both env as default in tempest which is much helpful for me.13:04
ricolinttx I still put project team as part of long-term mission scope, also feel free to rearrange things in graph if you like, I open the edit right to all now13:06
ricolinhttps://docs.google.com/presentation/d/1tQkzFvfrUejQHbrxZavaC-9ma3_sowUXpy2TctzMuB4/edit13:06
gmannasettle: what exactly you need help ? creating the story dashboard and stories for each project ?13:06
asettlegmann, yes please13:06
asettledhellmann, pointed me towards https://github.com/openstack/goal-tools13:06
gmannasettle: i have not used this tool but i can check. by when you  want to setup this ? I am planing to setup the same for my goal by this weekend.13:11
asettleHonestly, whenever you can. I really appreciate the help gmann !13:12
asettleI was naively floating along and not setting anything up for tracking13:13
asettleLike a derp13:13
fungii do think guidance on and strategies around which testenvs projects should name in their tox default envlist is likely a larger discussion which we shouldn't let creep into the python testing goal (also probably an easier discussion to have with the community next year after python 2.7 is eol)13:13
gmannasettle: ok. I will set it up by this weekend.13:13
asettleYou're the best! Thank you. I owe you one.13:14
gmannnp! :)13:14
gmannfungi: +1.13:15
gmannin that case, we can add py37 env. not explicitly adding py36 if not present but not removing also if it exit ?13:16
*** whoami-rajat has quit IRC13:16
fungii think it ought to be whatever's easiest on the goal champions, personally13:21
fungiand post-2.7 seems like a great opportunity to push some new standards around things like better standardization around tox.ini settings across projects, choice of bindep profiles in their bindep.txt files, trove classifiers in their setup.cfg and so on13:23
fungifocused on improving consistency and cross-project contributor experience13:24
fungihaving one simple workflow which will consistently get you the ability to run unit tests for a vast majority of our python-based projects13:25
smcginnisasettle: Would doing something like this simplify the PDF generation issues? https://wkhtmltopdf.org/13:32
toskysmcginnis: (sorry to jump in) it uses webkit, I wouldn't call it a simplification :)13:35
toskyfor jumping in*13:35
smcginnisHaha, fair enough. :)13:35
smcginnisI don't have any experience with that tool, but just with some of the issues brought up on the ML I thought maybe there might be an alternative way to accomplish this.13:35
toskythe current toolchain (which I started checking for sahara) is still sphinx based (ok, and latex-based), I suspect it would be easier to fix stuff there then introducing a new toolchain13:36
smcginnisOK, I didn't dig in too much. I just saw that there were some formatting challenges with using latex, but that's likely still the better place to be putting efforts rather than adding more moving parts. Thanks tosky!13:37
*** mriedem is now known as mriedem_afk13:38
*** openstackgerrit has quit IRC13:48
asettlesmcginnis, literally what tosky said :D13:57
fungialso if we get to pdf by way of tex, we get print typesetting for free along the way14:05
*** zbitter is now known as zaneb14:06
asettlefungi, two for the price of one!14:08
asettleI sense a budget TV commercial coming along14:08
asettleCan I get a set of steak knives with that?14:08
fungiit's a dessert topping! no it's a floor wax!14:08
asettleHi, Billy Mays here...14:09
asettleDo you ever wake up tired in the morning?14:09
fungii don't wake up in the morning. too much trouble14:18
*** mriedem_afk is now known as mriedem14:20
*** Luzi has quit IRC14:35
*** lpetrut has quit IRC14:38
*** lpetrut has joined #openstack-tc15:17
*** tdasilva has quit IRC15:21
*** lpetrut has quit IRC15:23
*** e0ne has quit IRC15:26
*** iurygregory has quit IRC15:33
*** jaosorior has quit IRC15:38
*** jaosorior has joined #openstack-tc15:38
*** diablo_rojo has joined #openstack-tc16:07
*** tdasilva has joined #openstack-tc16:19
*** tdasilva has quit IRC16:22
*** ricolin has quit IRC16:33
*** tdasilva has joined #openstack-tc16:37
*** jpich has quit IRC16:56
*** openstackgerrit has joined #openstack-tc17:10
openstackgerritKevin Carter (cloudnull) proposed openstack/governance master: Remove tripleo-ansible-roles from governance  https://review.opendev.org/66741617:10
openstackgerritKevin Carter (cloudnull) proposed openstack/governance master: Remove tripleo-ansible-roles from governance  https://review.opendev.org/66741617:17
*** ianychoi_ has quit IRC18:49
*** ianychoi_ has joined #openstack-tc18:50
*** e0ne has joined #openstack-tc19:07
*** mriedem has quit IRC19:15
*** mriedem has joined #openstack-tc19:16
*** lpetrut has joined #openstack-tc19:18
*** lpetrut has quit IRC19:23
*** tdasilva has quit IRC19:31
*** e0ne has quit IRC19:31
mnaserso19:36
mnaserthis is maybe getting technical but19:36
mnaseris a commit message considered part of governance?19:36
mnaserhttps://review.opendev.org/#/c/666974/1 --  the commit message here includes a lot of details regarding the spelling/etc19:36
fungiit's part of the content of the repository, but it's not an easily discoverable publication19:37
mnaserright, i wanted to ask more reviews from some of our chinese contributors across channels19:37
fungimight be a good idea to get that moved into the rst document then19:38
mnaserspecifically because the change is quite simple in terms of repo change, but the commit really includes the *reviewable* stuff and decisions19:38
mnaseri.e. the accepted romanizations19:39
smcginnisI would assume that information is going to be captured somewhere else and this is just additional context to spread awareness.19:39
*** tosky has quit IRC19:40
mnaserright, i think that's a bit of an important detail in this context so it should ideally be either part of the change or we agree that when we're voting on it, we're voting on the 'rules' to be in the commit message19:40
fungiwell, also the document is going to be translated... but the rationale being in the commit message means it won't be?19:41
mnaserright, these seem like details which we should capture (ideally)19:42
mnaserhttps://review.opendev.org/#/c/611511/19:44
mnaserperhaps something like this?19:44
fungiperhaps, though not sure it needs to be a resolution19:47
mnaserto be honest, i just want to make sure that we aren't limiting choices without being aware of the cultural implications of doing that19:48
mnaserso: are we voting on it being from shanghai, or are we voting on that + the romanization/etc19:48
* mnaser will review and send email to ML19:48
fungii think we're voting on the rationale presented in the commit message too, but i think having the rationale translated would help explain this choice to a broader interested cross-section of the community19:49
mnaser++19:49
fungiso embedding the rationale in the document may make sense19:51
smcginnisHaven't we always just included this stuff in the ML announcement when it went out in the past?19:51
smcginnisI don't recall things ever being formal needing TC voting on documenting our documented process of choosing a name from the locality of the Summit.19:52
mnasersmcginnis: well thats why i think the change is ok if it's just the commit change19:54
mnaserbut the commit message has a lot of implication on why/where/what/how19:54
fungiyeah, i'm not clear on where/how the translation is being published anyway, so maybe it's fine to have whoever's doing the translation work also translate the commit message19:59
*** e0ne has joined #openstack-tc20:18
*** e0ne has quit IRC20:32
*** ianychoi_ has quit IRC20:59
*** ianychoi_ has joined #openstack-tc21:00
*** ianychoi_ has quit IRC21:05
*** ianychoi_ has joined #openstack-tc21:09
*** openstackgerrit has quit IRC21:18
*** ianychoi_ is now known as ianychoi21:18
*** ijolliffe has quit IRC21:38
*** jaypipes has quit IRC21:46
*** tobberydberg has quit IRC21:49
*** tobberydberg has joined #openstack-tc21:51
*** mriedem has quit IRC21:52
*** tdasilva has joined #openstack-tc22:02
*** tdasilva_ has joined #openstack-tc22:02
*** tdasilva_ has quit IRC22:02
*** diablo_rojo has quit IRC22:54
*** diablo_rojo has joined #openstack-tc23:31

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