| *** eglute_s has quit IRC | 04:00 | |
| *** eglute has joined #refstack | 04:04 | |
| *** eglute has quit IRC | 04:05 | |
| *** eglute has joined #refstack | 04:06 | |
| *** chandankumar has joined #refstack | 06:31 | |
| *** jhesketh_ has joined #refstack | 07:10 | |
| *** jhesketh has quit IRC | 07:11 | |
| *** rmart04 has joined #refstack | 07:14 | |
| *** kopecmartin has joined #refstack | 07:28 | |
| *** tosky has joined #refstack | 07:39 | |
| *** openstackgerrit has joined #refstack | 08:36 | |
| openstackgerrit | Arx Cruz proposed openstack/python-tempestconf master: Removing dependence from SERVICE_VERSIONS https://review.openstack.org/587816 | 08:36 |
|---|---|---|
| tosky | while waiting kopecmartin's answer on ^^ (welcome back!), you have some time (maybe) to check my small fixes | 09:42 |
| tosky | the "Document CLI option" is going to fail in the tripleo job thanks to a timeout on the local pypi mirror :/ | 09:44 |
| openstackgerrit | Chandan Kumar proposed openstack/python-tempestconf master: add jobs for python-tempestconf only https://review.openstack.org/581084 | 10:07 |
| openstackgerrit | Arx Cruz proposed openstack/python-tempestconf master: Removing dependence from SERVICE_VERSIONS https://review.openstack.org/587816 | 12:55 |
| kopecmartin | arxcruz, chandankumar tosky hi, when you open this link https://docs.openstack.org/python-tempestconf/latest/user/usage.html#override-values what color have the three highlighted lines in the first example? | 13:03 |
| arxcruz | kopecmartin: jesus, can't see anything | 13:04 |
| chandankumar | kopecmartin: it is too much milky :-) | 13:04 |
| kopecmartin | me neither, i wanted to exclude my browser settings | 13:05 |
| tosky | milky | 13:05 |
| kopecmartin | hmm, when i tested it, it was nice, what happened? :D | 13:05 |
| kopecmartin | here it's nice http://logs.openstack.org/16/583516/2/check/build-openstack-sphinx-docs/8294274/html/user/usage.html | 13:06 |
| kopecmartin | it's the build from the gates | 13:06 |
| kopecmartin | it's funny because openstack guides recommend usage of the parameter: :emphasize-lines: <lines> | 13:07 |
| tosky | time for a question on #openstack-doc | 13:08 |
| arxcruz | god, pretty hard to remove a constant in python-tempestconf | 13:17 |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Don't expose credentials https://review.openstack.org/583504 | 13:29 |
| *** szaher has quit IRC | 14:26 | |
| *** eglute has quit IRC | 14:45 | |
| *** eglute has joined #refstack | 14:49 | |
| *** rmart04 has quit IRC | 15:17 | |
| tosky | arxcruz, chandankumar, kopecmartin: I'm asking on #openstack-infra about the failures; from a quick check, they seem to happen only when the node is ovh | 15:46 |
| arxcruz | tosky: ovh or ovb ? | 15:46 |
| arxcruz | oh, i see, got it | 15:46 |
| arxcruz | ovh | 15:46 |
| tosky | ovh.net :) | 15:48 |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Don't expose credentials https://review.openstack.org/583504 | 15:49 |
| *** kopecmartin has quit IRC | 16:02 | |
| *** rmart04 has joined #refstack | 17:11 | |
| openstackgerrit | Merged openstack/python-tempestconf master: horizon: don't error out for certificate issues https://review.openstack.org/588593 | 17:49 |
| openstackgerrit | Luigi Toscano proposed openstack/python-tempestconf master: Fix: return the flavor ID on autodetection https://review.openstack.org/589260 | 18:34 |
| fungi | hogepodge: did you have any thoughts on what to do about the refstack team since we talked about it a month ago? as far as continuing to be ptl for the stein cycle to oversee wind-down of the team, folding the refstack service and client into the interop wg, what happens to python-tempestconf, et cetera? or would you like help getting those discussions rolling sooner? | 18:50 |
| fungi | your friendly neighborhood tc liaison is here to assist however you need ;) | 18:50 |
| *** rmart04 has quit IRC | 18:59 | |
| hogepodge | fungi: we should fold it into interop wg | 20:13 |
| fungi | hogepodge: seems when we talked about it before, python-tempestconf was the main sticking point. should it also go to the interop wg or somewhere else? | 20:14 |
| hogepodge | I think that's a decision that's best left to the core developers, tosky and chandankumar have been leading those efforts | 20:17 |
| tosky | and arxcruz and kopecmartin :) | 20:19 |
| tosky | I think we need to discuss it; the interop wg is probably the closest project | 20:19 |
| tosky | out of curiosity, historically, what was the reason for having both refstack and interop as separate projects? | 20:21 |
| tosky | or was the interop wg be created later? | 20:21 |
| fungi | i think it was mostly around board working groups not being responsible for source code repositories, once upon a time | 20:24 |
| fungi | so the only repo the interop wg had was the one containing the interoperability specifications | 20:25 |
| fungi | essentially metadata | 20:25 |
| fungi | anyway, from the tc's standpoint if we hand off repos to the interop wg then all we really need is a governance change to dissolve the refstack team since we don't track repos controlled by board working groups | 20:27 |
| tosky | uh, then what does it mean exactly for us? | 20:29 |
| tosky | us as python-tempestconf? | 20:29 |
| tosky | I thought I've got the implications, but apparently I didn't | 20:29 |
| fungi | i think it means you just continue working on what you're working on, but if you _only_ work on python-tempestconf then you don't get to vote in tc elections | 20:30 |
| fungi | however, you could also apply to be a separate tempestconf team (as the remaining ember of the old refstack team essentially) | 20:31 |
| fungi | in which case you'd need a ptl for tempestconf | 20:31 |
| fungi | there's also a related question as to whether the interop wg wants to remain a working group under remit of the board of directors or transition to being a special interest group (sig) | 20:32 |
| tosky | weren't SIG supposed to replace WG? | 20:33 |
| fungi | though that's not really an urgent discussion | 20:33 |
| tosky | but would it be different from our point of view? | 20:33 |
| fungi | they were supposed to replace much of the need for wgs | 20:33 |
| fungi | there are some basic documents on what is expected of a sig, i'll grab them now | 20:34 |
| fungi | it's pretty much all on this one page: https://governance.openstack.org/sigs/ | 20:34 |
| tosky | a quick check does not show much differences regarding projects | 20:36 |
| fungi | the expectations of a sig are a bit lower than for a project team | 20:36 |
| tosky | so basically, if we don't go with a project on our own and we stay under a WG or a SIG, will we be more or less like a stackforge project? | 20:36 |
| fungi | those are separate options really: project team under tc, wg under bod, sig, or just a hosted project in the community infrastructure | 20:38 |
| fungi | though most of the remaining wgs that didn't become sigs are actually under the uc | 20:38 |
| fungi | https://governance.openstack.org/uc/#working-groups lists three wgs under the uc formally at the moment | 20:39 |
| fungi | (the uc also has some "teams" and the tc also has some "working groups" too, just to make things as confusing as possible) | 20:40 |
| tosky | did you list 3 or 4 options? I think I didn't get "wg under bod" | 20:41 |
| fungi | the biggest difference is that sigs are effectively self-organized but for formality's sake their creation gets approved jointly by representatives from the tc and uc | 20:41 |
| fungi | the interop working group is, at the moment, chartered by the openstack foundation board of directors | 20:41 |
| fungi | the user committee also has "teams" and "working groups" and the technical committee has "teams" and "working groups" | 20:42 |
| fungi | so, yes, i guess that's 6 options (plus unofficial makes 7) | 20:43 |
| tosky | and I thought I understood a bit how the community worked | 20:43 |
| tosky | so 7 options, 1 as unofficial projects, 6 still being an official project, but voting for the TC only in one case == independent project | 20:44 |
| tosky | is that correct? | 20:46 |
| fungi | yep | 20:46 |
| fungi | there was a time when there were working groups chartered by the board of directors and project teams approved by the technical committee, but then the user committee asked to be responsible for a number of the previous board working groups, and they also added some user committee teams which weren't working groups, and the tc added a concept of appointed working groups (which presently are just the set of | 20:47 |
| fungi | technical election officials), and then to attempt to dissolve some of the siloing between developers and users/operators the sigs idea was born in an attempt to encapsulate topics of joint interest under no seeming bias from being within the jurisdiction of any one existing governing body | 20:47 |
| fungi | as to which of those make sense for python-tempestconf, probably remaining in the interop wg (which might also become the interop sig) or being in its own project team (whether that's a renaming/rescoping of the refstack team or something wholly new) or going about it as an unofficial project are the 3 that seem likely | 20:49 |
| fungi | and you can also change your mind and switch between those pretty much at any time | 20:49 |
| tosky | I see, thanks | 20:50 |
| tosky | I will point out those logs to the rest of the team | 20:50 |
| hogepodge | tosky: interop wg is a board governed working group | 21:08 |
| fungi | oh, and for completeness of reference, the current board-chartered committees and working groups are tracked at https://wiki.openstack.org/wiki/Governance/Foundation#Committees_.26_Working_Groups | 21:08 |
| hogepodge | which is why it's not a sig | 21:08 |
| fungi | yeah, in my mind the one thing that makes it hard to turn the interop wg into a sig is that it sets requirements for trademark programs (though ultimately the board has to approve those anyway, so maybe that's not actually an issue) | 21:09 |
| hogepodge | fungi: interop wg also decided collectively to not be a sig | 21:10 |
| tosky | if we stay in the interop wg, do we need an approval from someone? Would we need to do something special apart from taking part to the meetings as we did so far here? | 21:10 |
| fungi | ahh, cool. the story i'd heard (i forget where now) was just that you didn't want to become a sig at that time because you'd just gone through a rename and didn't want to rename again | 21:10 |
| hogepodge | fungi: we also felt being a sig would take us too far away from our board mandated activities | 21:11 |
| fungi | makes complete sense | 21:11 |
| hogepodge | but people were also tired of renaming things :-) | 21:11 |
| fungi | tosky: presumably the interop wg needs to approve taking ownership of the (former) refstack deliverable repos | 21:11 |
| fungi | i don't know what form that approval has to take though | 21:12 |
| hogepodge | probably just approval by markvoelker_ and eglute at a meeting | 21:12 |
| fungi | nor do i know where they keep track of repositories for which they deem themselves responsible | 21:13 |
| fungi | but presumably they'll still delegate the maintenance of those repositories to whoever is working on/wants to work on them | 21:14 |
| *** tosky has quit IRC | 23:02 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!