| *** annabelleB has quit IRC | 00:02 | |
| fungi | time to start campaigning and debating! | 00:02 |
|---|---|---|
| fungi | welcome mugsie, mnaser, ricolin, gongysh, zaneb and zhipeng! (and welcome back cdent, dims, smcginnis and ttx) | 00:04 |
| zaneb | let the grilling begin :) | 00:05 |
| fungi | not a huge ballot, but plenty of great candidates nonetheless | 00:05 |
| fungi | tc-members and candidates and anyone else who's around... it's time for another office hour if you have anything you' want to bring up | 01:00 |
| EmilienM | hellow | 01:00 |
| fungi | not sure why you' needed an apostrophe, but there's no taking it back now | 01:00 |
| mnaser | (maybe if we used slack we'd be able to edit our messages, hah.) | 01:01 |
| fungi | if you used slack you wouldn't have to see my typos anyway ;) | 01:02 |
| pabelanger | o/ | 01:04 |
| *** dmsimard is now known as dmsimard|off | 01:06 | |
| TheJulia | The idea of slack seems... Disturbing. | 01:09 |
| persia | I like the idea of automatic pastebins, infinite scrollback, wide character support, broad platform support, etc. Less ideal is lack of federation and housing of all logs in a single jurisdiction. | 01:13 |
| fungi | and... lack of free software | 01:15 |
| *** harlowja has quit IRC | 01:16 | |
| zaneb | I once created a slack account (reluctantly) to help with a customer issue. then I realised that if you don't respond to pings fast enough, it emails you to make sure. Nnnnnnnope. Deleted the account the same day. | 01:16 |
| persia | On the campaign period: I wonder if it makes sense for those TC members whose term is not expiring to lead the candidates in debate: given that some of the candidate platforms describe specific agendas: this might be an excellent time to start discussion on those issues. | 01:17 |
| TheJulia | zaneb: impressive! :) | 01:19 |
| TheJulia | persia: that is a good point, although sadly I've not had a chance to read all of the announcements. :( | 01:19 |
| fungi | conveniently, we've got them all aggregated in one location for your reading pleasure | 01:20 |
| TheJulia | One thing has been in the back of my head this past week, but I'm fairly sure that unless there is willingness for regular TC turnover, that it wouldn't really be accepted | 01:20 |
| TheJulia | fungi: \o/ | 01:20 |
| persia | https://governance.openstack.org/election/ | 01:21 |
| persia | What's the thing in the back of your head? | 01:21 |
| TheJulia | term limits | 01:22 |
| TheJulia | From the standpoint of spreading knowledge and community, it could be a tool to do just that | 01:23 |
| fungi | lately we've been turning over ~50% of available seats at each election | 01:23 |
| TheJulia | Then again, I regularly state that I am crazy. | 01:23 |
| persia | My impression from each TC nomination period is that many of those who have previously served are reluctant to nominate themselves. I don't think term limits would help yet. | 01:24 |
| TheJulia | I was looking at recent numbers, I seem to be missing a email or two from civs though :\ | 01:24 |
| * TheJulia shrugs | 01:24 | |
| TheJulia | It is just a crazy idea | 01:24 |
| fungi | 50% seems to me like a good balance between continuity and sharing the responsibility with new leaders | 01:24 |
| TheJulia | agreed | 01:25 |
| persia | On the other hand, it may be worth an analysis of past elections, to see how many cases where incubants were nominated new folk were not elected (and the new folk were also not elected in the following election) | 01:25 |
| fungi | i don't think term limits are crazy | 01:25 |
| fungi | but i do worry that we could paint ourselves into a corner with not enough continuity if we had too many people who could serve and had working knowledge of the tc were forced out by policy | 01:26 |
| TheJulia | Which is actually the major source of hesitency in me even raising it | 01:27 |
| persia | I think the staggered election cycle is enough for continuity, especially if folk previously on the TC remained involved in governance to some degree, and were permitted to stand again after some period (e.g. one can onlly serve on the TC for two years, after which one must not stand for election for at least one year or similar). | 01:27 |
| fungi | though at least the fact that we only put half the seats up for election gives us some guaranteed continuity | 01:27 |
| fungi | or, yeah, what persia said | 01:28 |
| persia | My concern is whether there are enough folk who have the freedom to be able to fulfill TC duties if we force-expire some of the folk who have found a niche that allows them to serve. | 01:29 |
| persia | If we regularly had 15-20 candidates, I'd probably be in favour of term limits. With half that many, less so. | 01:29 |
| fungi | so i agree, _if_ people with history on the tc had the leeway to assist even when no longer serving, it could work out | 01:30 |
| persia | How do you mean "leeway"? Do you mean "time to engage in discussion" or do you mean "retain certain structural permissions"? | 01:30 |
| fungi | more like granted the time by their employer/life situation | 01:31 |
| persia | I think it would be valuable to try to cause that to be true independently of whether people had previous engagement with the TC. | 01:32 |
| fungi | absolutely | 01:32 |
| persia | I do not believe we can cause new folk to be able to join the TC unless they can find the time to be involved in governance. This suggests we need to find a way to help funding organisations appreciate the need to spend time involved in governance, independent of activity in an elected position. | 01:33 |
| fungi | i consider myself lucky to have a lifestyle which permits me to seek out these sorts of engagements but i respect that i'm almost certainly in a minority | 01:33 |
| persia | Maybe this is some badge or something we can grant for active reviewers in the governance repos? Maybe something similar for specs repos for project teams? | 01:33 |
| persia | And maybe have some copy that helps funding organsiations appreciate that folk who have such indicators can help them achieve their goals in openstack in ways that others may not be able to do as effectively. | 01:34 |
| zaneb | it's rare to see a current TC member run again and not get re-elected... but of late people seem to be doing a good job of rotating themselves out, so I don't think we need to regulate | 01:36 |
| fungi | we've been asked in the past to highlight people who are in need of recognition, so yes people getting (or staying) involved in governance even when they're not elected/electable would be a great choice | 01:38 |
| TheJulia | Agreed | 01:39 |
| TheJulia | zaneb: so what got me on the whole train of thought was a discussion of recognition and a complete stranger telling me all sorts of things because I looked like his former next door neighbor. | 01:41 |
| *** spsurya has joined #openstack-tc | 01:52 | |
| *** ianychoi_ is now known as ianychoi | 01:57 | |
| fungi | one of our more productive office hours, especially for this timeslot. thanks everyone! | 02:00 |
| TheJulia | :) | 02:01 |
| *** dklyle has joined #openstack-tc | 02:31 | |
| *** ianychoi has quit IRC | 02:44 | |
| *** ianychoi has joined #openstack-tc | 03:20 | |
| *** harlowja has joined #openstack-tc | 03:43 | |
| *** harlowja has quit IRC | 04:12 | |
| *** dklyle has quit IRC | 06:32 | |
| *** dklyle has joined #openstack-tc | 06:32 | |
| *** ildikov has joined #openstack-tc | 06:43 | |
| *** mordred has quit IRC | 06:45 | |
| *** dklyle has quit IRC | 06:47 | |
| *** mordred has joined #openstack-tc | 06:49 | |
| *** jpich has joined #openstack-tc | 07:25 | |
| *** mugsie has quit IRC | 08:09 | |
| *** mugsie has joined #openstack-tc | 08:21 | |
| *** mugsie has quit IRC | 08:21 | |
| *** mugsie has joined #openstack-tc | 08:21 | |
| ttx | On the number of candidates... On one hand 10 candidates for 7 seats is not that much, on the other they are all strong candidates. I'm also kind of happy that we have 3 candidates from China/Taiwan. Given that they had trouble getting elected in the past with the popularity-contest style of our election, I'm actually happy that we don't have 15 candidates -- increases our chances to have representation | 08:55 |
| ttx | frmo that region on the future TC :) | 08:55 |
| cmurphy | ++ that will be really good for the community | 08:56 |
| ttx | Re: term limits -- they are useful to create turnover, but if you do have turnover already, mandatory turnover can be more harmful than helpful. | 08:56 |
| ttx | It feels like we have healthy turnover over the past election cycles, so I'm not sure we really need to add term limits right now... | 08:57 |
| ttx | I guess we could have a rule that states that if we don't have at least 2 open seats (people not running for reelection), we force the oldest person out. | 08:59 |
| ttx | That way it only triggers if you don't already have turnover. | 08:59 |
| ttx | so no term limits, but minimal guaranteed turnover. | 09:00 |
| ttx | but again, not sure there is anything really broken there today that we need to fix. | 09:03 |
| *** cdent has joined #openstack-tc | 09:35 | |
| mugsie | I think in our current situation, term limits may not be needed anymore. They may have helped in the past, when we had a lot more candidates, and less TC turn over, but now we seem to be doing a good job of self management | 10:02 |
| cdent | I think the conversation earlier nailed it: people need to be more able to find and justify time for governance, even when not (yet) elected | 10:13 |
| cdent | in addition to that is: people need to feel like governance is a worthwhile use of time | 10:13 |
| cdent | most of the people I spoke with in the run up to this election cycle did not feel that was the case | 10:13 |
| mugsie | yeah, it is a hard sell. and in the past we did not do a good job of welcoming people with things like governance patches. I think that is improving, and we should hopefully see a pay off in the medium term, where people a - feel empowered to get involved, and b - feel that there is actual result from engaging with the process | 10:19 |
| cdent | b is critical | 10:22 |
| *** zhipeng has joined #openstack-tc | 10:27 | |
| mugsie | we do need to work on b | 10:27 |
| smcginnis | I agree with the idea that if we were not to have any open seats, then we may want to do something like make the longest serving member take a 6-12 month break. | 10:28 |
| smcginnis | But I also agree it could cause more harm than good with the current state of things otherwise. | 10:29 |
| cdent | balancing continuity with freshness is complex | 10:30 |
| mugsie | ++ | 10:30 |
| mugsie | In previous organisations I have worked in or helped re-org, we had term limits, but balanced it with full time staff in the org, who could act as an insitutional memory. That worked, but it required a large amount of full time staff interaction with elected leaders | 10:32 |
| mugsie | (something similar to a civil service in governmental style orgs) | 10:33 |
| cdent | in a sense ttx and fungi are kind of like that | 10:39 |
| * cdent posts a board meeting topic | 10:39 | |
| cdent | I hope it turns into a fire | 10:39 |
| * smcginnis likes a good bonfire | 10:42 | |
| mugsie | CfgMgmtCamp wouldn't let me get one of these for the conference - I wonder would the foundation be OK ? https://www.boringcompany.com/not-a-flamethrower/ | 10:43 |
| mugsie | :D | 10:43 |
| cdent | frequently it's never the things I think matter that become a fire | 10:57 |
| *** zhipeng has quit IRC | 11:08 | |
| *** zhipeng has joined #openstack-tc | 11:27 | |
| *** zhipeng has quit IRC | 11:34 | |
| *** cdent has quit IRC | 11:56 | |
| jroll | cdent: +1000 on your email <3 | 12:29 |
| jroll | interesting plot twist on the kolla-kubernetes topic: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129452.html | 12:31 |
| mugsie | yeah - it is | 12:32 |
| ttx | jroll: yeah, they have been in touch with me and apparently all parties agree on a sensible way forward | 12:35 |
| ttx | The only person from "the kolla-k8s team" that was still active-enough to chime in (Rich) is actually the one who proposed it, so I'm more confident now | 12:37 |
| dhellmann | o/ | 12:39 |
| jroll | I find it odd that this is the response to concerns that changing governance might kill the project, though I'm not quickly finding if that was a tc-people concern or a kolla-people concern | 12:39 |
| jroll | ttx: yeah, that is a good thing, and he +1'd jeffrey's proposal there | 12:40 |
| dhellmann | jroll: I take it as a sign that we discovered the problem too late. | 12:40 |
| jroll | dhellmann: discovered that kolla-k8s is effectively dead too late? | 12:41 |
| dhellmann | I wonder if we had known about the team structural issue earlier if we would have been able to take action that would have allowed kolla-k8s to thrive | 12:42 |
| * dhellmann has to step away | 12:42 | |
| jroll | I wonder what that action would be, without having people to do real work on it | 12:43 |
| jroll | fwiw, it seems to me (by rich's analysis) that openstack-helm covers the use case of kolla images on k8s well, so it seems like a good example of healthy competition, ending with dropping effort where it doesn't make sense | 12:47 |
| jroll | said analysis: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128892.html | 12:47 |
| *** zhipeng has joined #openstack-tc | 12:48 | |
| jroll | he does have concerns about -helm switching away from kolla to loci or something else. I also think that would be fine. if there's an image provider out there that's better than kolla, I don't see why we'd want openstack-helm to stay on kolla images for the sake of kolla. it should be about what's best for openstack as a whole, not a single project. | 12:49 |
| smcginnis | ++ | 12:49 |
| dhellmann | jroll : if kolla-k8s hadn't been under the kolla umbrella, would helm have even been created? | 12:53 |
| dhellmann | but yes, I agree that competition is fine and deciding to end a project is fine, too | 12:54 |
| dhellmann | some of the history with this particular team leads me to think if we had taken different action at the start we might have different outcome now; not necessarily better or worse in terms of the tech but perhaps in terms of the social aspects | 12:54 |
| dhellmann | perhaps *better | 12:54 |
| jroll | dhellmann: I would hope kolla-k8s-but-not-kolla would have used helm instead of reinventing the wheel, but that's a good question :) | 12:55 |
| dhellmann | sorry, I meant openstack-helm, not helm itself :-) | 12:55 |
| jroll | right | 12:56 |
| dhellmann | IIRC, that project was started in part because of social issues dealing with the kolla team. Those issues obviously have 2 sides and I don't know all the details, but I wonder if they would have had the same influence if there were multiple PTLs or teams involved. | 12:56 |
| dhellmann | maybe I'm mixing up openstack-helm and loci, though | 12:56 |
| dims | o/ | 12:56 |
| jroll | I would hope that kolla-k8s, if outside of kolla governance, would have eventually turned into openstack-helm, though | 12:56 |
| dhellmann | quite possibly | 12:57 |
| fungi | well, there's also work to get loci images working with kolla-ansible, so i don't see it as just a scenario for helm... it could be possible for one orchestration solution to support both i suppose, if they want to | 12:57 |
| dhellmann | evolution of a project in place feels less disruptive than disbanding one in favor of another | 12:58 |
| dims | jroll : the design of kolla-kubernetes was heavily influenced by how kolla works ... so doubt it | 12:58 |
| dims | there would still be 2 sides | 12:58 |
| jroll | dhellmann: but yeah, I'd have to look far back in history to really have a good answer to the social question, and I don't have time to do that today | 12:58 |
| * dims has been talking to both openstack-helm and kolla-k8s from the beginning | 12:58 | |
| dhellmann | nor I, so I'm just wistfully pondering | 12:58 |
| mnaser | (and then you have loci) | 12:59 |
| mnaser | which seemed to aim to be the more generic image that would ideally be consumed by everyone afaik | 12:59 |
| dims | mnaser : that was an attempt at reconciliation . so yes | 12:59 |
| * jroll <3 loci | 12:59 | |
| dims | dhellmann : in the end folks don't have time to work on kolla-kubernetes or have moved on to other things ... | 13:00 |
| mnaser | i would have loved to see a 'generic' form of images which then is consumed by different downstream deployment worlds.. in an ideal world | 13:01 |
| mugsie | loci is pretty generic isnt it? | 13:02 |
| mnaser | i think it aimed to be, but there seemed to be push back from the kolla teams to consume them | 13:02 |
| dhellmann | it's not up to the kolla team what sorts of images other teams consume | 13:02 |
| dhellmann | this is specifically an area of "competition" and differentiation we encourage | 13:03 |
| mugsie | well, it doesn't have the kolla JSON API stuff alright, so kolla probably wont use them, but other should | 13:03 |
| dhellmann | it has always rubbed me the wrong way that the kolla team tried to be the only container team | 13:03 |
| dims | mnaser : see thread from about a year ago - http://lists.openstack.org/pipermail/openstack-dev/2017-May/116681.html | 13:03 |
| jroll | mnaser: that's a bummer, I had thought it was fairly generic as well (and lightweight!) | 13:03 |
| mnaser | jroll: they are! but i guess they don't suit kolla's needs | 13:04 |
| mugsie | loci seems to produce more traditional container images, with mounting config etc | 13:04 |
| mnaser | dims: 100% agree with your questions which make it that kolla is "speciality" images | 13:04 |
| fungi | mugsie: there was a thread on the ml a week or so back about extracting the "json api" and associated start scripts so that kolla-ansible could use them with loci images | 13:05 |
| jroll | dhellmann: +1000 | 13:05 |
| mugsie | yeah - but that JSON api isn't even doc'd yet ... | 13:05 |
| mnaser | imho that "json" api should be in the deployment tool, not the images | 13:05 |
| mugsie | mnaser: ++ | 13:05 |
| dims | mnaser : there was at least a couple of folks asking "can i use loci images with swarm or just docker to stand up some standalone services" | 13:08 |
| dims | recently | 13:08 |
| dims | i take that as progress | 13:09 |
| dims | but then there are very few folks working on loci too, which is a bummer | 13:09 |
| dims | for example we can evangelize say cinder with noauth running in a docker container as a thing folks could use for some scenarios | 13:10 |
| mugsie | when I was playing with it recently, it just seemed to work, with no major issues - it is just stable? | 13:10 |
| dims | mugsie : possibly | 13:11 |
| mnaser | dims: i think the problem is that it solves one half of the problem and people want the full solution | 13:12 |
| dims | it's more about getting folks not working on openstack-helm to kick the tires i fues | 13:12 |
| dims | s/fues/guess/ | 13:12 |
| mnaser | no one wants to write their own deployment tool just to consume loci (i guess) | 13:12 |
| dims | +1 mnaser | 13:12 |
| mnaser | it's easier to just use kolla-ansible or $your_favorite_deployment_project | 13:12 |
| dims | yep | 13:13 |
| dhellmann | perhaps we should be encouraging people to use the community deployment tools anyway. That gives us a common place to address issues like upgrade complexity. | 13:13 |
| mnaser | unfortunately i think people don't get so excited about deployment tools and they end up being maintained by one or two organizations (read: evrardjp email about OSA) | 13:14 |
| dims | +1 dhellmann | 13:14 |
| mnaser | tripleo seems to be mostly redhat, i'm not sure about kolla-ansible or openstack-helm | 13:15 |
| dhellmann | mnaser : yes, I think that's a pretty big issue for us now | 13:15 |
| dims | dhellmann : i'd like for example something like openstack-ansible AIO to stitch together a single node (devstack-style) environment | 13:16 |
| mnaser | it can already do this afaik | 13:16 |
| dims | mnaser all our services running as containers in a single docker daemon? | 13:17 |
| dims | (loci containers) | 13:17 |
| mnaser | osa uses lxc containers :X | 13:17 |
| mnaser | so they're more os-like containers | 13:18 |
| dims | right | 13:18 |
| dims | mnaser : it would be easy to write a devstack equivalent using loci, but i'd prefer that we don't go down that path and just start with ansible (or another common deployment tool) | 13:19 |
| mnaser | dims: that would be really cool and would totally speed things up i'd imagine | 13:20 |
| mnaser | my concern would be openstack is really strange in that it requires a lot of bootstrapping for things like adding endpoints etc | 13:20 |
| mnaser | maybe a keystone service catalog plugin that uses consul or some service discovery tool (hint lbragstad :p) | 13:21 |
| mnaser | that'd eliminate a whole lot of bootstrapping | 13:21 |
| lbragstad | yeah - that's been proposed before, but never implemented | 13:22 |
| *** annabelleB has joined #openstack-tc | 13:40 | |
| ttx | lbragstad: maybe we could give it a second life with the edge people pushing for more hands-off operations | 13:43 |
| lbragstad | i wouldn't mind trying to off load stuff to consul | 13:45 |
| zhipeng | mnaser +1 | 13:45 |
| lbragstad | it seems like a way to reduce wheels | 13:46 |
| lbragstad | but i haven't really had the bandwidth to prototype anything yet =/ (despite the fact that i imagine it would be really useful) | 13:46 |
| dhellmann | knowing that it's of interest may encourage someone who has more time to do it | 13:53 |
| lbragstad | sounds like a wishlist bug? | 13:54 |
| lbragstad | i thought bknudson brought this up in the past, but i couldn't find the context | 13:56 |
| *** kumarmn has joined #openstack-tc | 13:58 | |
| dims | lbragstad : dhellmann : found this - https://blueprints.launchpad.net/kolla/+spec/consul-container | 14:05 |
| *** dklyle has joined #openstack-tc | 14:15 | |
| *** kumarmn_ has joined #openstack-tc | 14:30 | |
| *** kumarmn has quit IRC | 14:33 | |
| *** hongbin_ has joined #openstack-tc | 14:40 | |
| zaneb | mnaser: openstack-helm is effectively a single-vendor project: http://stackalytics.com/?module=openstack-helm&metric=marks | 14:57 |
| zhipeng | not looking good for kolla-kubernetes as well: http://stackalytics.com/?metric=marks&module=kolla-kubernetes | 14:59 |
| mnaser | zaneb: most deployment projects are, unfortunately. http://stackalytics.com/?module=tripleo-group&metric=marks and http://stackalytics.com/?module=openstack-ansible&metric=marks (50% of the independent is a rackspace employee afaik) | 14:59 |
| mnaser | looks like kolla has some interesting success -- http://stackalytics.com/?module=kolla-group&metric=marks | 14:59 |
| zaneb | kolla-kubernetes was actually very diverse as well http://stackalytics.com/?module=kolla-kubernetes&metric=marks&release=queens | 15:01 |
| smcginnis | '/win 20 | 15:06 |
| smcginnis | Doh | 15:06 |
| lbragstad | dims: dhellmann apparently we're terrible about persisting discussions we have in IRC | 15:06 |
| lbragstad | there are all the occurances i've been able to find for mentions of consul in keystone | 15:07 |
| lbragstad | http://paste.openstack.org/show/719483/ | 15:07 |
| pabelanger | dims: lbragstad: dhellmann: consul is pretty neat, i wasn't aware anybody in openstack was using it. But, I haven't actively been looking either | 15:15 |
| lbragstad | pabelanger: yeah - we haven't actually prototyped any sort of integration with consul, yet.. but we've talked about it a lot | 15:16 |
| clarkb | out of curiousity, since etcd is already a base service wouldn't it be more appropriate to etcd? | 15:16 |
| pabelanger | clarkb: yah, likely. I haven't really looked myself at consul / etcd in the last 2 years | 15:18 |
| * lbragstad is in the same boat | 15:19 | |
| *** zhipeng has quit IRC | 15:19 | |
| dims | clarkb : not saying consul per se ... just that we need something | 15:30 |
| clarkb | sure, just thinking we shouldn't add a second distributed key value store with support for service discovery and dns :P | 15:31 |
| *** kumarmn_ has quit IRC | 15:37 | |
| lbragstad | clarkb: i think mordred would agree with that point http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2015-10-08.log.html#t2015-10-08T23:35:20 | 15:38 |
| *** dklyle has quit IRC | 15:38 | |
| lbragstad | i don't think any consul discussions have been revisited since the ectd | 15:40 |
| lbragstad | work | 15:40 |
| *** kumarmn has joined #openstack-tc | 15:41 | |
| *** kumarmn has quit IRC | 15:49 | |
| *** annabelleB has quit IRC | 15:55 | |
| *** annabelleB has joined #openstack-tc | 16:02 | |
| *** kumarmn has joined #openstack-tc | 16:02 | |
| *** harlowja has joined #openstack-tc | 16:06 | |
| *** jpich has quit IRC | 16:07 | |
| *** kumarmn has quit IRC | 16:16 | |
| *** kumarmn has joined #openstack-tc | 16:16 | |
| *** cdent has joined #openstack-tc | 16:24 | |
| dhellmann | smcginnis : can I get you to +2a https://review.openstack.org/#/c/561058/ so the rest of the dependency management section patches will merge, please? | 16:30 |
| smcginnis | dhellmann: Sure, I'll take a look. | 16:30 |
| dhellmann | thanks! | 16:30 |
| openstackgerrit | Merged openstack/project-team-guide master: add info about lower-constraints.txt https://review.openstack.org/561058 | 16:35 |
| openstackgerrit | Merged openstack/project-team-guide master: add some process instructions for updating dependencies https://review.openstack.org/562006 | 16:36 |
| *** kumarmn has quit IRC | 16:40 | |
| *** kumarmn has joined #openstack-tc | 16:40 | |
| *** kumarmn has quit IRC | 16:42 | |
| *** kumarmn has joined #openstack-tc | 16:42 | |
| *** kumarmn has quit IRC | 16:45 | |
| *** kumarmn has joined #openstack-tc | 16:46 | |
| *** kumarmn has quit IRC | 16:49 | |
| *** kumarmn has joined #openstack-tc | 16:49 | |
| *** kumarmn has quit IRC | 16:56 | |
| *** kumarmn has joined #openstack-tc | 16:56 | |
| *** kumarmn_ has joined #openstack-tc | 16:58 | |
| *** kumarmn has quit IRC | 17:01 | |
| *** kumarmn_ has quit IRC | 17:09 | |
| *** kumarmn has joined #openstack-tc | 17:10 | |
| *** kumarmn_ has joined #openstack-tc | 17:11 | |
| *** kumarmn_ has quit IRC | 17:12 | |
| *** kumarmn_ has joined #openstack-tc | 17:12 | |
| *** kumarmn has quit IRC | 17:14 | |
| dhellmann | cdent : the article you posted on symmathesy is interesting, thanks for sharing that | 17:21 |
| cdent | flaper87 has suggested that we gather in vancouver to chat about it | 17:22 |
| dhellmann | ++ | 17:22 |
| dhellmann | I would like for us to explore ways the TC can work together more as a team | 17:23 |
| dhellmann | I don't have a good way to express exactly what I mean by that, yet | 17:23 |
| cdent | yes, I have similar feelings, and also don't know exactly what I mean | 17:23 |
| cdent | in my response on the "what we should talk about with the board" thread, the second topic is driven in part by figuring out how to be more symmathesitic (if that's the right form of the word) | 17:24 |
| * dhellmann reads that email again | 17:26 | |
| dhellmann | yeah, it feels like we have some "process debt" to deal with still | 17:27 |
| cdent | the idea being that upstream unicorns need to increase their generativity | 17:28 |
| dhellmann | yes | 17:28 |
| *** harlowja has quit IRC | 17:44 | |
| *** harlowja has joined #openstack-tc | 18:18 | |
| *** harlowja_ has joined #openstack-tc | 18:23 | |
| *** harlowja has quit IRC | 18:24 | |
| *** annabelleB has quit IRC | 19:00 | |
| *** kumarmn_ has quit IRC | 19:00 | |
| *** kumarmn_ has joined #openstack-tc | 19:05 | |
| *** kumarmn_ has quit IRC | 19:10 | |
| *** kumarmn has joined #openstack-tc | 19:11 | |
| *** kumarmn has quit IRC | 19:11 | |
| *** kumarmn has joined #openstack-tc | 19:11 | |
| *** kumarmn has quit IRC | 19:17 | |
| *** kumarmn has joined #openstack-tc | 19:17 | |
| *** kumarmn_ has joined #openstack-tc | 19:20 | |
| *** kumarmn has quit IRC | 19:22 | |
| *** kumarmn_ has quit IRC | 19:37 | |
| *** kumarmn has joined #openstack-tc | 19:39 | |
| *** kumarmn has quit IRC | 19:40 | |
| *** kumarmn has joined #openstack-tc | 19:40 | |
| *** kumarmn has quit IRC | 19:42 | |
| *** kumarmn has joined #openstack-tc | 19:44 | |
| *** kumarmn_ has joined #openstack-tc | 19:45 | |
| *** kumarmn has quit IRC | 19:49 | |
| *** mriedem has joined #openstack-tc | 20:34 | |
| *** eandersson has quit IRC | 21:10 | |
| *** eandersson has joined #openstack-tc | 21:13 | |
| * fungi is lost in buzzwords | 21:18 | |
| smcginnis | fungi: Are you leveraging your synergies to think outside the box? | 21:19 |
| fungi | if i say yes will the bobs let me return to my cubicle? | 21:19 |
| cdent | fungi: if you don't have a reference for it already, and those are the buzzwords that are losing you, this is the article doug and were talking about: https://the-composition.com/the-origins-of-opera-and-the-future-of-programming-bcdaf8fbe960 (and led to many buzzwords) | 21:20 |
| fungi | i do enjoy going to see the opera | 21:20 |
| * dhellmann pictures fungi in a Hawaiian shirt with tails | 21:21 | |
| fungi | the lei and monocle go well together | 21:21 |
| cdent | a good look | 21:22 |
| * cdent waves goodnight | 21:22 | |
| dhellmann | indubitably | 21:22 |
| *** cdent has quit IRC | 21:22 | |
| *** kumarmn_ has quit IRC | 21:28 | |
| *** kumarmn has joined #openstack-tc | 21:30 | |
| *** kumarmn has quit IRC | 21:34 | |
| *** kumarmn has joined #openstack-tc | 21:34 | |
| *** kumarmn has quit IRC | 21:43 | |
| *** kumarmn has joined #openstack-tc | 21:43 | |
| *** kumarmn_ has joined #openstack-tc | 22:04 | |
| *** kumarmn has quit IRC | 22:07 | |
| *** kumarmn_ has quit IRC | 22:12 | |
| *** kumarmn has joined #openstack-tc | 22:12 | |
| *** kumarmn_ has joined #openstack-tc | 22:15 | |
| *** kumarmn_ has quit IRC | 22:15 | |
| *** kumarmn_ has joined #openstack-tc | 22:15 | |
| *** kumarmn has quit IRC | 22:17 | |
| *** kumarmn_ has quit IRC | 22:37 | |
| *** kumarmn has joined #openstack-tc | 22:37 | |
| *** kumarmn has quit IRC | 22:42 | |
| *** kumarmn has joined #openstack-tc | 22:57 | |
| *** kumarmn has quit IRC | 23:01 | |
| *** hongbin_ has quit IRC | 23:18 | |
| *** andreaf has quit IRC | 23:18 | |
| *** andreaf has joined #openstack-tc | 23:18 | |
| *** mriedem has quit IRC | 23:32 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!