| *** ricolin has joined #openstack-tc | 01:00 | |
| *** spotz_ has joined #openstack-tc | 02:14 | |
| *** ricolin_ has joined #openstack-tc | 02:15 | |
| *** corvus_ has joined #openstack-tc | 02:17 | |
| *** ff has joined #openstack-tc | 02:18 | |
| *** corvus has quit IRC | 02:19 | |
| *** flaper87 has quit IRC | 02:19 | |
| *** ricolin has quit IRC | 02:19 | |
| *** spotz has quit IRC | 02:19 | |
| *** mriedem has quit IRC | 02:54 | |
| *** rosmaita has quit IRC | 03:14 | |
| *** ricolin_ has quit IRC | 03:17 | |
| *** ricolin has joined #openstack-tc | 03:17 | |
| *** corvus_ is now known as corvus | 03:36 | |
| *** corvus is now known as Guest78457 | 03:37 | |
| *** Guest78457 is now known as jeblair | 03:38 | |
| *** jeblair is now known as corvus | 03:43 | |
| *** ianychoi_ has quit IRC | 03:54 | |
| *** ianychoi has joined #openstack-tc | 04:08 | |
| *** gagehugo has quit IRC | 05:33 | |
| *** jpich has joined #openstack-tc | 07:01 | |
| *** tosky has joined #openstack-tc | 07:39 | |
| *** e0ne has joined #openstack-tc | 08:49 | |
| *** cdent has joined #openstack-tc | 08:56 | |
| cdent | tc-members it's office hours time, anyone around with tc discussion? | 09:01 |
|---|---|---|
| cmurphy | o/ | 09:02 |
| cdent | mornin' cmurphy | 09:02 |
| cmurphy | mornin' cdent | 09:02 |
| * cdent brings this meeting of the c-nicks to order | 09:02 | |
| cmurphy | ;) | 09:03 |
| cdent | I move that we only accept adjutant if they change their name to cadjutant | 09:03 |
| cmurphy | that sounds completely reasonable | 09:04 |
| cmurphy | i second | 09:04 |
| * cdent finally votes on adjutant | 09:10 | |
| cdent | I'm +1 but not in a way that I'm perfectly happy with | 09:10 |
| cmurphy | understandable | 09:12 |
| cdent | This office hour has lost some of its flair. I wonder if we can put that on the ttx? | 09:23 |
| cmurphy | I think he's at a foundation retreat | 09:25 |
| cmurphy | so we can blame him for anything we want | 09:26 |
| cmurphy | it did seem to be more active not too long ago | 09:27 |
| *** gagehugo has joined #openstack-tc | 09:38 | |
| * cdent arranges ptg flights | 09:53 | |
| *** rosmaita has joined #openstack-tc | 10:49 | |
| *** ff is now known as flaper87 | 11:20 | |
| *** flaper87 is now known as Guest21687 | 11:20 | |
| *** Guest21687 has quit IRC | 11:21 | |
| jroll | cdent: I think you mean catjutant | 11:21 |
| jroll | :) | 11:21 |
| cdent | 🍪 | 11:22 |
| *** ff has joined #openstack-tc | 11:22 | |
| *** edmondsw has joined #openstack-tc | 11:25 | |
| TheJulia | Good morning | 11:37 |
| * cdent waves | 11:39 | |
| cdent | TheJulia: I had a question/thought you might have thoughts on. Came up in conversation with my son about trying to make inroads with the community in China: | 11:45 |
| TheJulia | cdent: I'm all ears... well ears lacking a coffee refill, but you know :) | 11:45 |
| cdent | How do you think individuals (for example you) and organizations (the TC, the foundation, companies like red hat) should balance their desire for inclusion of individuals from china against what might be considered regressive attitudes towards openness held by companies or governments there? How much of an issue is that? | 11:46 |
| cdent | (of course this isn't an issue limited to china, but that was the context it came up in) | 11:47 |
| TheJulia | hmm | 11:48 |
| cdent | my son speculated that it might be necessary to "make closed-ness hurt" | 11:49 |
| cdent | he wasn't asserting that was necessary, more that it was an option | 11:49 |
| TheJulia | I think it is a two part answer | 11:49 |
| *** ricolin has quit IRC | 11:50 | |
| TheJulia | I think we all need to learn to decouple the associations we make that drive perceptions. We need to explicitly state what we know works and how we can interaction, meanwhile be open to operating a little differently. I'm not saying throw out patterns, but if someone emails a diff, perhaps that is viable. Ultimately be more understanding and realize the people on the other end are just like us, the just speak a | 11:52 |
| TheJulia | different language day to day. The governments differ, but the fundamentals of governments and companies all kind of boil down to the same on both sides. In essence, we need to build a bridge and see if they build towards that bridge as well. | 11:52 |
| TheJulia | Ultimately I think people and the companies are just like they are here, they are trying to solve their problem in the most effective low cost way. So in a sense, your son is right in that making closed behaviors hurt might bring people to the table, but they would have to know the table exists, and know that the other parties are not out to take them for everything. | 11:53 |
| TheJulia | Ultimately, it comes down to having mutually common goals. | 11:54 |
| * TheJulia hopes that makes sense | 11:54 | |
| cdent | it does, yeah | 11:57 |
| TheJulia | I do believe there are perception differences, but upfront context into the ways can help soften those issues. | 12:07 |
| cdent | Yeah, I think you've pretty much nailed it with the notion that we need to be foregrounding(?) context more and more often. | 12:13 |
| fungi | cmurphy: if you call several day-long meetings deep in the heart of texas in the middle of summer a "retreat" then sure ;) | 12:17 |
| cmurphy | fungi: maybe s/foundation retreat/foundation hostage situation/ | 12:18 |
| fungi | everything's bigger in texas, including the sun | 12:18 |
| * cdent sings | 12:21 | |
| fungi | on the inclusivity front, i'm in favor of going out of my way to accommodate/facilitate less-efficient modes of contributor interaction, so long as i don't have to compromise my principles in doing so. e-mailed patch diffs are a fine example, as it's basically how our vmt operates on embargoed vulnerability reports | 12:22 |
| fungi | it may not be convenient, but it gets the job done | 12:22 |
| *** mriedem has joined #openstack-tc | 12:59 | |
| scas | back in yesterdecade, freebsd patches were almost exclusively emailed diffs. it wouldn't be unheard of, just old school | 13:26 |
| *** hongbin has joined #openstack-tc | 13:40 | |
| *** ff is now known as flaper87 | 13:47 | |
| *** flaper87 has quit IRC | 13:47 | |
| *** flaper87 has joined #openstack-tc | 13:47 | |
| *** diablo_rojo has joined #openstack-tc | 13:53 | |
| *** diablo_rojo has quit IRC | 13:54 | |
| *** annabelleB has joined #openstack-tc | 13:55 | |
| *** dklyle has quit IRC | 14:01 | |
| *** dklyle has joined #openstack-tc | 14:01 | |
| *** ricolin has joined #openstack-tc | 14:02 | |
| * TheJulia is finally done writing books in replies to emails while she was on PTO... at least downstream emails. | 14:03 | |
| TheJulia | Should we consider "outreach contacts", people who are willing to engage in discussions about various topic areas, and indicate various ways they can be reached? | 14:05 |
| cdent | that seems like a good idea, but how would be publish such a thing? it often seems like if people know how to find that list, it's not much further to knowing what the list is providing | 14:06 |
| TheJulia | That is a super good point | 14:06 |
| TheJulia | I suspect if we publish something, and then using some existing bridges of communication to circulate that information | 14:07 |
| TheJulia | I wonder what Lauren might think about ^^^... | 14:07 |
| cdent | I find that I'm far more able and willing to respond to questions than I am to spontaneously creating info | 14:08 |
| TheJulia | There is definitely a cost to both, and the costs do differ | 14:18 |
| *** annabelleB has quit IRC | 14:19 | |
| tosky | apologize if it's not the proper place to ask, and in case please redirect me to the proper place: | 14:24 |
| tosky | we have few pending changes in python-saharaclient which would lead to a major version bump, breaking compatibility with old users of python-saharaclient | 14:24 |
| tosky | do all the compatibility deprecation/retention rules apply only to the API exposed by services, or also to the Python clients? | 14:25 |
| *** spotz_ is now known as spotz | 14:31 | |
| dhellmann | TheJulia , cdent : regarding "outreach contacts", that's part of what the First Contact SIG is trying to put together | 14:32 |
| dhellmann | tosky : good question | 14:33 |
| dhellmann | tosky : for most of the libraries we rely on some sort of integration testing to ensure that when we do release a breaking change it doesn't break us. So a library such as oslo.messaging has to roll a new API in before it can remove the deprecated API. | 14:34 |
| dhellmann | that said, the governance rules we have are focused mostly on the REST APIs | 14:34 |
| *** annabelleB has joined #openstack-tc | 14:35 | |
| dhellmann | my recommendation, as a consumer of libraries that break their APIs, is please try to support the deprecated API for as long as possible before removing it | 14:35 |
| TheJulia | +1 | 14:35 |
| TheJulia | So if there is a way to make it a minor version bump, and have the actual deprecated interface removed later, then it will be a much easier transition for the API consumers | 14:36 |
| dhellmann | because forcing a hard upgrade from one API to the next is not always as simple as we think it is | 14:36 |
| dhellmann | yep | 14:36 |
| tosky | now I need to convince the others | 14:36 |
| dhellmann | tosky : if you need some help with making the API change in a backwards-compatible way, the oslo team has plenty of experience with that sort of thing and may be able to give some advice | 14:37 |
| dhellmann | sometimes it's obvious, and sometimes it's tricky | 14:37 |
| *** jeremyfreudberg has joined #openstack-tc | 14:39 | |
| TheJulia | tosky: Also, if you need assistance in regards to convincing others not to make a hard breaking api change, I'm sure a number of us have enough experience in the pain that can create. | 14:39 |
| *** tellesnobrega has joined #openstack-tc | 14:39 | |
| tosky | would it be possible to have official guidelines for Python clients too? Maybe (unrelated to the current change) something that also deals with a (future?) change to openstacksdk | 14:39 |
| dhellmann | what do you have in mind? | 14:40 |
| jeremyfreudberg | sorry - don't have the scrollback - can someone summarize what has been said on the tc side so far about the saharaclient issue? | 14:41 |
| dhellmann | jeremyfreudberg : sure, just a sec | 14:42 |
| dhellmann | first, today's logs will be at http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-10.log.html | 14:42 |
| dhellmann | it looks like the bot hasn't caught up with us, yet | 14:42 |
| dhellmann | so in the mean time: | 14:42 |
| dhellmann | tosky asked about what the rules are for clients and API changes | 14:42 |
| *** EmilienM is now known as EvilienM | 14:42 | |
| dhellmann | formally the rules apply to REST APIs | 14:42 |
| dhellmann | however, we do encourage teams to consider that consumers of their libraries will not be happy with API breaks there | 14:43 |
| dhellmann | we run into problems with our upstream dependencies pretty regularly and it causes all sorts of extra work for us | 14:43 |
| dhellmann | in many cases we have integration test jobs that ensure that libraries do not remove old APIs while they are still in use | 14:43 |
| dhellmann | I don't know the situation for the saharaclient library w.r.t. integration tests like that | 14:43 |
| dhellmann | it's possible, if sometimes tricky, to make API changes in a way that is still backwards compatible, and I suggested that the Oslo team may have some good advice about how to do that if you are having trouble with the change in question | 14:44 |
| dhellmann | I don't know the details of the change, yet, or how much you've already discussed various options, so that's just a suggestion of a source of advice if it could be useful | 14:45 |
| dhellmann | TheJulia : does that cover it? ^^ | 14:45 |
| *** AlanClark has joined #openstack-tc | 14:45 | |
| * jroll is not julia but agrees that covers it | 14:45 | |
| dhellmann | thanks, jroll | 14:45 |
| jeremyfreudberg | dhellmann: besides the other sahara deliverables, and cloud users, some other consumers of saharaclient that i know of would be rally and heat | 14:45 |
| jroll | I'd love to see the change | 14:46 |
| jeremyfreudberg | putting aside all that though -- does that mean we can never make a breaking change? | 14:46 |
| dhellmann | jeremyfreudberg : no, not never. it just needs to be done with care. | 14:46 |
| jeremyfreudberg | and semver is not enough care? | 14:46 |
| dhellmann | the approach we have found to work best is to produce a version of the library that works using both API versions, and to support both for some period of time, and then finally drop the old API | 14:46 |
| dhellmann | semver helps signal when the break comes, but it does not make it easier to consume | 14:47 |
| jroll | I'm assuming we're discussing https://review.openstack.org/#/c/580693 , which did seem to properly deprecate things (though I'm not sure how long it was marked deprecated) | 14:47 |
| dhellmann | consider the way we test our own software | 14:47 |
| TheJulia | dhellmann: Covers it very well | 14:47 |
| dhellmann | heat and rally would not be co-installable if they required different versions of sahara client to work | 14:47 |
| tosky | jroll: more thishttps://review.openstack.org/#/c/579680/ | 14:47 |
| tosky | this: https://review.openstack.org/#/c/579680/ | 14:47 |
| jroll | ah | 14:48 |
| jeremyfreudberg | jroll: the one you linked is far less controversial | 14:48 |
| tosky | jeremyfreudberg: right, because it does not break the API - old code will continue to work (if session is provided) | 14:49 |
| jroll | makes sense | 14:49 |
| jroll | does seem like a hard break | 14:49 |
| dhellmann | reordering the arguments in https://review.openstack.org/#/c/579680/2/saharaclient/api/data_sources.py to allow description to be optional and changing the credentials handling look like the main issues there | 14:50 |
| dhellmann | one way to handle that would be to make a new method with the desired new API and deprecate the old one | 14:50 |
| dhellmann | it looks like the old one could potentially even be implemented in terms of the new one | 14:51 |
| dhellmann | so you still only have 1 real implementation | 14:51 |
| dhellmann | by having a second method, you can keep both APIs around for a while to give folks time to adopt the new API | 14:51 |
| dhellmann | if we ignore downstream consumers and look just at our own CI, having a breaking change like that is technically impossible to adopt | 14:52 |
| dhellmann | any code calling that create() method would need to be modified, but the application containing that code couldn't have a new version of the dependency allowed by the constraints system until the unit tests would pass | 14:52 |
| dhellmann | and devstack job, if it's included there | 14:53 |
| dhellmann | those changes are in separate repositories, so you can't land a single change that fixes everything at once | 14:53 |
| dhellmann | and so you either have to force one change through and live with something broken for a while, or you need to stage the API change to give some deprecation time | 14:53 |
| dhellmann | make sense? | 14:54 |
| *** annabelleB has quit IRC | 14:56 | |
| tosky | to be honest, jeremyfreudberg put out a change to cover the compatibility change inside our test repository (https://review.openstack.org/#/c/581372/ ) | 14:57 |
| tosky | still, I would avoid a total sudden breakage | 14:57 |
| jeremyfreudberg | i've been mostly convinced on making the saharaclient change less drastic | 14:59 |
| jeremyfreudberg | doing so with good ux might be another story | 15:00 |
| *** annabelleB has joined #openstack-tc | 15:06 | |
| tosky | about my previous question: I don't have anything specific in mind, apart from having some official guidelines for clients too, in addition to APIs, so that there is no need to ask again | 15:09 |
| tosky | the point about openstacksdk was a partially related question about the only visible big disruptive change that could happen for python clients in the future | 15:11 |
| TheJulia | I feel that is a reasonable ask in terms of guidelines, I guess we will need to ponder that. | 15:15 |
| *** annabelleB has quit IRC | 15:21 | |
| dhellmann | that seems like a good outcome | 15:39 |
| *** zaneb has quit IRC | 15:54 | |
| *** zaneb has joined #openstack-tc | 15:57 | |
| *** jeremyfreudberg has quit IRC | 16:35 | |
| *** annabelleB has joined #openstack-tc | 16:39 | |
| *** e0ne has quit IRC | 16:51 | |
| *** jpich has quit IRC | 17:04 | |
| openstackgerrit | Merged openstack/governance master: Remove team diversity tags https://review.openstack.org/579870 | 17:05 |
| openstackgerrit | Doug Hellmann proposed openstack/governance master: add check_review_status.py https://review.openstack.org/579953 | 17:11 |
| openstackgerrit | Jill Rouleau proposed openstack/governance master: Import ansible-role-tripleo-cookiecutter https://review.openstack.org/581428 | 17:13 |
| *** annabelleB has quit IRC | 17:20 | |
| *** annabelleB has joined #openstack-tc | 17:20 | |
| *** AlanClark has quit IRC | 17:43 | |
| *** annabelleB has quit IRC | 17:43 | |
| *** annabelleB has joined #openstack-tc | 17:45 | |
| *** annabelleB has quit IRC | 17:48 | |
| *** mriedem has quit IRC | 17:53 | |
| *** mriedem1 has joined #openstack-tc | 17:57 | |
| *** mriedem1 is now known as mriedem | 18:00 | |
| *** annabelleB has joined #openstack-tc | 18:15 | |
| *** e0ne has joined #openstack-tc | 18:31 | |
| *** e0ne has quit IRC | 18:47 | |
| *** annabelleB has quit IRC | 18:51 | |
| *** annabelleB has joined #openstack-tc | 19:05 | |
| *** e0ne has joined #openstack-tc | 20:04 | |
| *** annabelleB has quit IRC | 20:14 | |
| openstackgerrit | Zane Bitter proposed openstack/governance master: Clarify new project requirements for community engagement https://review.openstack.org/567944 | 20:19 |
| *** ricolin has quit IRC | 20:19 | |
| *** annabelleB has joined #openstack-tc | 20:21 | |
| *** e0ne has quit IRC | 20:53 | |
| *** e0ne has joined #openstack-tc | 20:53 | |
| *** cdent has quit IRC | 21:10 | |
| *** e0ne has quit IRC | 21:22 | |
| *** rosmaita has quit IRC | 21:34 | |
| *** edmondsw has quit IRC | 22:01 | |
| *** annabelleB has quit IRC | 22:08 | |
| *** annabelleB has joined #openstack-tc | 22:13 | |
| *** annabelleB has quit IRC | 22:47 | |
| *** zaneb has quit IRC | 23:03 | |
| *** hongbin has quit IRC | 23:06 | |
| *** tosky has quit IRC | 23:08 | |
| *** edmondsw has joined #openstack-tc | 23:16 | |
| *** edmondsw has quit IRC | 23:21 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!