Wednesday, 2018-05-23

*** zaneb has joined #openstack-tc00:02
*** zaneb has quit IRC00:30
*** spsurya has quit IRC00:41
*** edmondsw has joined #openstack-tc01:03
*** edmondsw has quit IRC01:08
*** zaneb has joined #openstack-tc01:15
*** edmondsw has joined #openstack-tc01:21
openstackgerritTuan Luong-Anh proposed openstack/governance master: Replace deprecated library function os.popen() with subprocess  https://review.openstack.org/57009302:08
openstackgerritTuan Luong-Anh proposed openstack/governance master: Replace deprecated library function os.popen() with subprocess  https://review.openstack.org/57009302:30
*** gagehugo has quit IRC02:52
*** gagehugo has joined #openstack-tc02:58
*** gagehugo has quit IRC03:12
*** gagehugo has joined #openstack-tc03:14
*** kumarmn has joined #openstack-tc04:14
*** kumarmn has quit IRC04:31
*** kumarmn has joined #openstack-tc04:32
*** kumarmn has quit IRC04:36
*** kumarmn has joined #openstack-tc04:42
*** kumarmn has quit IRC04:47
*** tdasilva has quit IRC04:58
*** cdent has joined #openstack-tc05:03
*** cdent has quit IRC05:03
*** kumarmn has joined #openstack-tc05:27
*** tdasilva has joined #openstack-tc05:27
*** kumarmn has quit IRC05:31
*** jaosorior has quit IRC07:18
*** jaosorior has joined #openstack-tc07:19
*** edmondsw has quit IRC07:48
*** dtantsur has joined #openstack-tc11:18
*** dtantsur has quit IRC11:18
*** dtantsur has joined #openstack-tc11:19
*** dklyle has quit IRC13:33
*** edmondsw has joined #openstack-tc13:39
*** annabelleB has joined #openstack-tc13:51
*** annabelleB has quit IRC14:05
*** annabelleB has joined #openstack-tc14:21
*** dklyle has joined #openstack-tc14:49
*** annabelleB has quit IRC14:59
*** annabelleB has joined #openstack-tc15:07
*** zaneb has quit IRC15:07
*** edmondsw has quit IRC15:24
*** edmondsw has joined #openstack-tc15:25
*** edmondsw has quit IRC15:25
*** annabelleB has quit IRC15:42
*** mriedem has joined #openstack-tc15:44
openstackgerritmelissaml proposed openstack/governance master: fix a typo in projects.yaml  https://review.openstack.org/56946515:47
*** mriedem has quit IRC16:14
*** mriedem1 has joined #openstack-tc16:14
*** cdent has joined #openstack-tc16:28
*** edmondsw has joined #openstack-tc16:28
*** edmondsw has quit IRC16:34
*** edmondsw has joined #openstack-tc16:35
*** edmondsw has quit IRC16:40
*** mriedem1 is now known as mriedem16:43
*** dtruong has joined #openstack-tc16:53
*** edmondsw has joined #openstack-tc16:57
*** dklyle has quit IRC16:57
*** dtantsur is now known as dtantsur|afk16:59
*** diablo_rojo has joined #openstack-tc17:00
*** dklyle has joined #openstack-tc17:02
*** david-lyle has joined #openstack-tc17:05
*** dklyle has quit IRC17:06
*** david-lyle has quit IRC17:10
*** dklyle has joined #openstack-tc17:10
*** zaneb has joined #openstack-tc17:12
*** lbragstad has joined #openstack-tc17:26
*** edmondsw_ has joined #openstack-tc17:27
*** edmondsw has quit IRC17:30
* fungi thinks using "tc" to mean "titanium cloud" in this channel is confusing17:39
cmurphyoh wow, I was wondering why the puppet was highly specific to the technical committee environment and didn't even make that connection17:40
*** cdent has quit IRC17:40
*** mriedem has quit IRC17:40
fungithat was me too, at least for a couple minutes17:41
zaneblol17:41
*** zaneb has quit IRC17:46
*** dklyle has quit IRC17:50
*** david-lyle has joined #openstack-tc17:50
*** edmondsw_ has quit IRC17:50
*** edmondsw has joined #openstack-tc17:53
*** lbragstad has quit IRC17:53
*** lbragstad has joined #openstack-tc17:54
*** edmondsw_ has joined #openstack-tc17:58
* dtroyer slaps /me with a wet noodle17:58
dtroyerI had that problem going the other way for a while17:59
*** cdent has joined #openstack-tc18:00
*** david-lyle has quit IRC18:01
*** edmondsw has quit IRC18:02
*** lbragstad has quit IRC18:02
*** mriedem has joined #openstack-tc18:11
*** dklyle has joined #openstack-tc18:16
*** edmondsw has joined #openstack-tc18:28
cdentMy ongoing frustration with the starlingx stuff has little to do with the code (having code, any code, to farm for improvements is a net win). What is really getting to me is the way in which companies are now able to exercise the foundation for loads of "free" publicity that they wouldn't get if they were joining openstack (the project) itself18:30
cdentsimilarly, a small project from a smallish company, like adjutant, doesn't get starlingX level of marketing, because it _looks_ like if you are intel you can play whatever games you like18:32
*** edmondsw_ has quit IRC18:32
cdentbut not if you are small (and wanting to play by some form of rules)18:33
cdentSo, essentially, the foundation executive's power to incubate projects has created a complex, and fairly undefined, playing field18:33
mugsiehonestly, I have no issue with stuff around openstack, the patch management / infra management etc. it is the forks that i have the issue with.18:33
mugsieI would say the tooling should go up, and be made to work with the openstack/(nova|cinder|glance|..) repos18:34
*** mriedem has quit IRC18:34
cdentI'm semi-shruggy about forking. the larger openstack projects are sometimes pretty bad about velocity. I'm not sure that competition is a bad thing. That's not to say that the way this has been done is correct, but I do think it was inevitable18:35
*** lbragstad has joined #openstack-tc18:42
*** cdent has quit IRC18:43
dtroyermugsie: I did update https://review.openstack.org/#/c/569562/ last night to only include the non-forking repos (all of them, not just OpenStack) while we sort out what the right solution is18:44
*** zaneb has joined #openstack-tc18:47
*** edmondsw has quit IRC18:47
*** diablo_rojo has quit IRC18:48
*** cdent has joined #openstack-tc18:48
*** lbragstad has quit IRC18:54
*** zaneb has quit IRC18:58
*** edmondsw has joined #openstack-tc19:03
*** lbragstad has joined #openstack-tc19:03
*** edmondsw_ has joined #openstack-tc19:14
*** cdent has quit IRC19:16
*** edmondsw has quit IRC19:16
*** lbragstad has quit IRC19:22
mugsiedtroyer: OK, that sounds like a good way forward. Thanks for the paitence on this19:24
jbrycecdent: we've given starlingx basically no marketing from the foundation (no logo, no press release, no interviews, no mention in our speaking) and my input to dtroyer and crew was to make code available asap and start discussions from there to figure out the right approach with it19:28
jbrycei personally have no interest in paper/marketing launches, but companies will talk about it on their own in ways that we don't always control19:31
*** edmondsw_ has quit IRC19:31
*** edmondsw has joined #openstack-tc19:32
*** edmondsw_ has joined #openstack-tc19:36
*** edmondsw has quit IRC19:36
*** edmondsw_ has quit IRC19:41
jbrycei also think we're still trying to figure out how to handle the chicken and egg thing of first steps for these things. in my view, i'd love to have something similar to the old stackforge space where we could put code to start with and then discuss if/where/how it fits in overall without implying a level off officialness or completeness that probably isn't accurate19:49
*** diablo_rojo has joined #openstack-tc20:12
dtroyerone of the knocks on stackforge was the pain in moving repos between namespaces.  The upstream group of repos in STX would be a good fit for a temporary place to hold things until the final disposition is complete.  By definition, nothing moves out, it is only retired.  Of course there is the risk of a permanent temporary status (see Google's definition of 'beta'), I wouldn't mind having a lease-type of arrangement where after some period the continue20:33
*** edmondsw has joined #openstack-tc20:49
*** lbragstad has joined #openstack-tc20:52
*** edmondsw has quit IRC20:53
*** mriedem has joined #openstack-tc20:57
*** diablo_rojo has quit IRC21:01
*** edmondsw has joined #openstack-tc21:09
jbryceyeah i get the technical challenges around it. just talking more conceptually. with airship we actually set up the git vhost ( https://git.airshipit.org ) to use publicly to try to get a little separation from the openstack namespace at the start21:14
*** mriedem has quit IRC21:29
*** edmondsw has quit IRC21:33
*** lbragstad has quit IRC21:37
*** lbragstad has joined #openstack-tc21:38
*** zaneb has joined #openstack-tc21:41
*** cdent has joined #openstack-tc21:44
*** zaneb has quit IRC21:47
*** zaneb has joined #openstack-tc21:53
cdentjbryce: yeah, I don't think there's bad intent by the foundation, but rather than companies are able to take advantage of the not fully formed situation to get a benefit that isn't ideal: at least some people are equating starlingx with kata or zuul as "top level project". That may be incorrect, but being able to say it so easily is problematic.22:14
jbryceyep22:16
cdentwe've seen similar things enough times now it seems like we need to come up with some kind of "hey, you're at level 1 of whatever this multi-level process is you may not say $something"22:17
*** cdent has quit IRC22:22
zanebdtroyer: question: is the StarlingX project planning to accept more patches on top of the forks, or is it just a case of publishing the existing code in advance of trying to get it upstreamed?22:23
dtroyerzaneb: I am assuming that additional patches may be required, but I think a really strong case needs to be made if that is the case.  We need them to build and that is how adjustments, like a security backport, would be done.22:28
dtroyerBTW, we do need to fix the recent Nova CVE, that will be one of the first things we add.22:29
zanebdtroyer: I think it's completely reasonable to continue to import stuff from upstream stable/pike22:30
zaneband adjusting build stuff22:31
zanebif more development was happening on that branch I'd be concerned22:31
dtroyermee too22:32
*** cdent has joined #openstack-tc22:32
*** lbragstad has quit IRC22:33
zanebdtroyer: I do wonder if maintaining it as a repo containing patches to be applied to upstream stable/pike, like a distro might do (although in this case one that contains new features, which a distro generally wouldn't do) might help with the perception problem22:33
zanebbecause that's really not a tempting way to do new feature development ;)22:34
*** edmondsw has joined #openstack-tc22:37
dtroyerthe repo is going to exist, either in a visible shared place or privately in multiple developer places.  I am not sure if the extra steps involved will have the intended effect.  I do know, after this process, that reviewing patches of patch files is really painful and you need to unroll them to make proper sense of them.  At least I do.22:37
zaneb:)22:38
zanebdtroyer: fyi this is what we use: https://github.com/softwarefactory-project/rdopkg#rdopkg22:39
dtroyerthanks, added to our list…   we need to re-visit much of the build process around StarlingX.  The thing we have now has 5 years of tuning in a single static environment to un-do.22:41
*** edmondsw has quit IRC22:41
*** mriedem has joined #openstack-tc22:52
*** zaneb has quit IRC23:02
*** cdent has quit IRC23:05
*** mriedem has quit IRC23:15
*** mriedem has joined #openstack-tc23:21
*** diablo_rojo has joined #openstack-tc23:25
*** cdent has joined #openstack-tc23:33
*** mriedem has quit IRC23:34
*** edmondsw has joined #openstack-tc23:37
*** lbragstad has joined #openstack-tc23:42

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