| *** gcb has joined #openstack-tc | 02:15 | |
| *** kumarmn has joined #openstack-tc | 03:39 | |
| *** kumarmn has quit IRC | 03:44 | |
| *** kumarmn has joined #openstack-tc | 07:40 | |
| *** kumarmn has quit IRC | 07:44 | |
| openstackgerrit | Merged openstack/governance master: Add policy artifacts for magnum https://review.openstack.org/510920 | 08:25 |
|---|---|---|
| *** dtantsur|afk is now known as dtantsur | 08:45 | |
| *** sdague has joined #openstack-tc | 09:44 | |
| *** gcb has quit IRC | 09:56 | |
| *** gcb has joined #openstack-tc | 10:00 | |
| *** Qiming has quit IRC | 10:50 | |
| *** Qiming has joined #openstack-tc | 10:54 | |
| *** cdent has joined #openstack-tc | 10:57 | |
| *** gcb has quit IRC | 10:58 | |
| *** Qiming has quit IRC | 10:58 | |
| *** Qiming has joined #openstack-tc | 11:01 | |
| *** cdent has quit IRC | 11:16 | |
| *** cdent has joined #openstack-tc | 11:16 | |
| *** dtantsur is now known as dtantsur|brb | 11:42 | |
| *** rosmaita has joined #openstack-tc | 11:52 | |
| *** dhellmann has quit IRC | 12:15 | |
| *** jpich has joined #openstack-tc | 12:15 | |
| *** dhellmann has joined #openstack-tc | 12:16 | |
| *** mriedem has joined #openstack-tc | 13:07 | |
| *** gcb has joined #openstack-tc | 13:25 | |
| *** cdent has quit IRC | 13:37 | |
| *** cdent_ has joined #openstack-tc | 13:37 | |
| *** kumarmn has joined #openstack-tc | 13:48 | |
| *** kumarmn has quit IRC | 13:54 | |
| *** hongbin has joined #openstack-tc | 13:56 | |
| *** gcb has quit IRC | 13:58 | |
| *** gcb has joined #openstack-tc | 13:58 | |
| *** cdent_ is now known as cdent | 14:05 | |
| *** dtantsur|brb is now known as dtantsur | 14:05 | |
| TheJulia | fungi, EmilienM, smcginnis: Thanks! | 14:16 |
| cdent | congrats TheJulia, glad to have you | 14:17 |
| EmilienM | ++ | 14:17 |
| cdent | and welcome back EmilienM, wouldn’t be the same without you | 14:17 |
| EmilienM | cdent: the french/canadian touch? :P | 14:19 |
| TheJulia | Thanks! Glad to be here! | 14:19 |
| cdent | It’s all about _you_, EmilienM, now where you are from or live. | 14:19 |
| *** david-lyle has joined #openstack-tc | 14:21 | |
| EmilienM | cdent: right :-) thanks | 14:25 |
| cdent | s/now/not/ | 14:25 |
| *** gcb has quit IRC | 14:29 | |
| pabelanger | is there onboarding docs new people should be reading? | 14:47 |
| cdent | welcome pabelanger, congrats. If there are, I don’t remember them. ttx? | 14:48 |
| fungi | pabelanger: in the past the tc chair generally covered that in the first meeting following the election, but now that we no longer have regular weekly meetings i expect that to find its way into ttx's next weekly status update or maybe as a separate post to the openstack-tc ml | 14:50 |
| mtreinish | there is: https://governance.openstack.org/tc/reference/house-rules.html but it's hardly exhaustive | 14:51 |
| fungi | yep, that's one of the things he linked to after the last election... in general just about everything under https://governance.openstack.org/tc/reference/index.html is at least worth a skim | 14:52 |
| pabelanger | okay, that is what I expected. But yah, will start skimming | 14:52 |
| fungi | also this is the tracker ttx has been updating: https://wiki.openstack.org/wiki/Technical_Committee_Tracker | 14:53 |
| fungi | and for those who are unaware, we have three (entirely optional but encouraged) office hour blocks as well as a reserved weekly slot for a more formal meeting we sometimes exercise after some discussion and advance notice: http://eavesdrop.openstack.org/#Technical_Committee_Meeting | 14:55 |
| fungi | i generally attend the wednesday and thursday office hour since the tuesday one is pretty early in the morning for me (but is far more convenient to apac and emea members/contributors) | 14:57 |
| *** kumarmn has joined #openstack-tc | 15:12 | |
| * TheJulia opens all the links for reading a little later today | 15:12 | |
| cdent | TheJulia, pabelanger: the stuff that confused me the most is that there are different rules for different types of things on how many votes are required to pass. That’s covered in the links but it takes a while to set it, and I’ve not memorized it: more just accepted it. | 15:16 |
| TheJulia | That is a good strategy :) | 15:19 |
| *** cdent has quit IRC | 15:20 | |
| sdague | congrats: TheJulia, pabelanger, and cmurphy for coming on board | 15:21 |
| *** kumarmn has quit IRC | 15:26 | |
| * cmurphy waves | 15:29 | |
| pabelanger | thanks! | 15:30 |
| *** kumarmn has joined #openstack-tc | 15:36 | |
| *** kumarmn_ has joined #openstack-tc | 15:37 | |
| *** kumarmn has quit IRC | 15:41 | |
| *** kumarmn_ has quit IRC | 15:42 | |
| fungi | sdague, mordred and stevemar left some big shoes to fill, but i'm confident we're all up to the task ;) | 15:47 |
| zaneb | dhellmann: I only just saw your conversation with cdent above^ from Tuesday... did my last reply on the ML clarify anything for you? | 15:47 |
| *** cdent has joined #openstack-tc | 15:52 | |
| *** jpich has quit IRC | 17:13 | |
| dims | TheJulia : pabelanger : cmurphy : will you make it to sydney? | 17:47 |
| dims | there's a sunday joint meeting with the board and IC - https://wiki.openstack.org/wiki/Governance/Foundation/5Nov2017BoardMeeting | 17:48 |
| dims | s/IC/UC/ | 17:48 |
| pabelanger | dims: yes, I land 1800UTC Satuday. | 17:53 |
| TheJulia | dims: I'll be there. I land on Thursday because I adjust to that timezone kind of badly. | 18:01 |
| cdent | I was hoping to get there on thursday too, for the same reason, but couldn’t get flights to work out, so am arriving late friday | 18:04 |
| *** dtantsur is now known as dtantsur|afk | 18:04 | |
| dims | ack. please see the older discussion from the previous meeting (especially the last etherpad) on https://wiki.openstack.org/wiki/Governance/Foundation/7May2017BoardMeeting | 18:04 |
| dims | pabelanger : TheJulia : cmurphy : ^ | 18:04 |
| TheJulia | dims: thanks! | 18:06 |
| pabelanger | dims: will do | 18:10 |
| openstackgerrit | Telles Mota Vidal Nóbrega proposed openstack/governance master: Marking Sahara policy in code goal as done https://review.openstack.org/514422 | 18:24 |
| openstackgerrit | Telles Mota Vidal Nóbrega proposed openstack/governance master: Marking Sahara policy in code goal as done https://review.openstack.org/514422 | 18:25 |
| *** cdent has quit IRC | 18:50 | |
| *** harlowja has joined #openstack-tc | 18:53 | |
| openstackgerrit | Ruby Loo proposed openstack/governance master: Add the supports-rolling-upgrade tag to Ironic https://review.openstack.org/514448 | 20:09 |
| EmilienM | pabelanger: don't we land on Sunday morning 9.30 am local time? | 20:13 |
| EmilienM | pabelanger: if you leave Canada on Friday, you'll likely arrive on Sunday | 20:14 |
| openstackgerrit | Brian Rosmaita proposed openstack/governance master: Add Glance planning artifact for community goal https://review.openstack.org/514449 | 20:18 |
| pabelanger | EmilienM: my mail client said 1800UTC, but could be wrong. But ya, land and run to meeting is likey the path | 20:18 |
| EmilienM | pabelanger: sorry, 8:25 AM local time on Sunday. | 20:22 |
| EmilienM | or 9.25? I don't know | 20:22 |
| cmurphy | dims: yes i will be in sydney and in time to make the meeting | 20:25 |
| dims | cool thanks cmurphy | 20:25 |
| cmurphy | less time than i planned on for jetlag recovery :) | 20:26 |
| dhellmann | is anyone going to be around on saturday before the board meeting? | 20:52 |
| dtroyer | I will… actually landing on Tuesday & staying with friends for a few days | 20:53 |
| * dtroyer will have no jet-lag excuses | 20:53 | |
| dhellmann | ah, nice. | 20:54 |
| dhellmann | I'm looking at things to do for the day. The zoo looks appealing. | 20:54 |
| dtroyer | We're going to Taronga Zoo on wed or thurs | 20:57 |
| fungi | i get in around 8am friday, so not a lot of opportunity to resume sentience by the time sunday rolls around, but should still be enough | 21:02 |
| * fungi had originally volunteered to pitch in on the now-cancelled hackathon | 21:03 | |
| dtroyer | I had not heard it was cancelled… but didn't know about it until PTG... | 21:03 |
| fungi | some sponsors pulled out at the last possible moment | 21:04 |
| fungi | i think we didn't hear about the cancellation until the weekend, or thereabouts | 21:05 |
| dhellmann | bummer | 21:09 |
| SamYaple | hello peoples. i have been piecing together how to submit a project to be official from various places (havent done it for a couple years). i have a PR up in governance, but im wondering if there is more i need to do now? | 21:11 |
| dhellmann | SamYaple : I think that's it at this point. ttx will include it in the tc status update and in the mean time the rest of us will look at it and post questions on the review. | 21:18 |
| dhellmann | as long as you've answered the questions in the requirements for new projects, you should be all set | 21:19 |
| SamYaple | dhellmann: awesome. thanks | 21:19 |
| SamYaple | i remember last time i had to put in on the tc meeting agenda, but thats not a thing anymore | 21:19 |
| dhellmann | yeah, it's already set to have a topic of formal-vote so it should show up in everyone's review list | 21:21 |
| SamYaple | b-e-a-utiful! thanks again | 21:25 |
| flwang | sorry, speaking of chiming in, is the board meeting open for non-TC? | 21:40 |
| zaneb | flwang: the joint part of the meeting usually is, yes. but only to listen aiui | 21:45 |
| flwang | zaneb: ok, i see. thx | 21:47 |
| *** mriedem is now known as mriedem_away | 21:48 | |
| flwang | zaneb: may be instead of trying to join the meeting at Sydney, I should try to run for next TC election | 21:49 |
| dtroyer | The entire board meeting is open, except for executive sessions | 21:49 |
| zaneb | flwang: why not do both? :) | 21:49 |
| dtroyer | open to attend | 21:49 |
| flwang | dtroyer: cool, may I know the time and location? | 21:50 |
| flwang | I'm not sure if there are people like me working for openstack years but still not familiar with the process of TC | 21:51 |
| dtroyer | hmmm… I haven't received the online meeting invite for it yet, that's usually where I get the timing. Here is the wiki page for it: https://wiki.openstack.org/wiki/Governance/Foundation/5Nov2017BoardMeeting | 21:52 |
| dtroyer | flwang: I am sure you are not alone there | 21:52 |
| flwang | dtroyer: thanks | 21:54 |
| flwang | dtroyer: if i have some proposals I'd like to get a help from TC level, what's the process I should follow? | 21:55 |
| dtroyer | It depends on the nature of the proposals. Some things can go straight to a governance review, I think it is usually a good idea to talk about them beforehand, on the ML or in a TC office hours. | 21:56 |
| flwang | TBH, sometimes I'm a little bit afraid to send a proposal, especially related to process, to mailing list, because typically the result is nothing, since it's too open and you always get yes and no, and then no result | 21:58 |
| dtroyer | that is understanable. The current easy way to talk directly with the TC is the office hours times, the second easy way is in this IRC channel whenever you can catch someone, like right now :) | 21:59 |
| flwang | dtroyer: cool, thanks for the offering | 22:00 |
| flwang | I'm selling my first idea | 22:00 |
| dtroyer | looks like the next office hours is about 11 hours from now | 22:00 |
| flwang | how to manage the new contributors power | 22:01 |
| dtroyer | I'm not sure exactly what that means | 22:03 |
| flwang | dtroyer: we can see many commits about the typo | 22:06 |
| dtroyer | ah yes, that sort of thing, ok | 22:06 |
| flwang | so a straightforward way is reduce the weight of those kind of commit, because I know commits is a KPI for some companies | 22:06 |
| flwang | and another thing I'd like to suggest also related to this is create another new index/metric based on value instead of number | 22:07 |
| dtroyer | one thing to consider is that the existing metrics (primarily Stackalytics) are not actually controlled by us. I'm not sure that the foundation even controls the existing site yet, it might still be the Mirantis one (there was an effort begun to change that a long time ago that I think stalled) | 22:11 |
| dtroyer | we have long had the issue where companies (and individuals for that matter) make up their own ways of counting things that we can not control. | 22:11 |
| flwang | because some companies in China, say government, when they ask for tender, they may make the a condition like this, as a tender, you must be the top 10 openstack contributors as for commits | 22:11 |
| dtroyer | one argument is to give them something that we do control that hopefully is hard to abuse, that is much easier said than done | 22:12 |
| flwang | dtroyer: that's what i talking about basically | 22:12 |
| dtroyer | that sort of thing was very common in our community back when it was mostly startups and we have (finally) gotten most of the long-time contributing/sponsoring companies out of that mindset | 22:13 |
| flwang | mitigate the importance of commit number, add a new metric based on 'VALUE' | 22:13 |
| flwang | and the core team and decide the value of the commit/patch | 22:13 |
| dtroyer | I think that is really the only good solution, because anything else can, and will be, be gamed | 22:13 |
| flwang | for example, if you're contributing a top 5 wanted projects, you get higher weight/value than normal | 22:13 |
| dtroyer | the effort in making the value determination has a time factor that gets added onto someones workload? | 22:14 |
| flwang | if you're fixing a critical bug, even though the fix is only one line, it gets much value than a 1000 lines typo fixing | 22:14 |
| dtroyer | another issue I see with that is now it is much more subjective, and controlling the people who make those determinations becomes one way to game that (IE, hire all of the PTLs) | 22:15 |
| flwang | it could take time, but better than doing nothing | 22:15 |
| dtroyer | I think our experience with the early companies here is that education is really the best long-term approach | 22:15 |
| flwang | dtroyer: i don't think hiring more PTL is a bad thing, if a company has many PTL, they know openstack a lot | 22:16 |
| dtroyer | although some never caught on, they also did not last so long either | 22:16 |
| dtroyer | you are right, someone needs to hire PTLs :) the issue though is hiring for the wrong reason also leads to un-hiring them for similar reasons, and that is not always healthy for projects or OpenStack as a whole | 22:17 |
| flwang | again, the value is not only managed by the PTL, is decided by the core team | 22:17 |
| flwang | so that to encourage people to contribute to the hard but valuable things | 22:18 |
| dtroyer | then s/PTL/core/ above | 22:18 |
| flwang | things are changed as i mentioned before, do we still think there are many contributors around for each project? | 22:19 |
| dtroyer | my feeling is that encouragement needs to go to the people who allocate resouces, usually the same people who look at numbers without really wanting to understand them | 22:19 |
| dtroyer | we do still have a large number of contributors, but their 'type' has changed maybe | 22:19 |
| flwang | that's the another thing we should do, but I'm trying to figure out if there is anything TC can help to lead the community | 22:20 |
| dtroyer | we will go around-and-around on this for a long time staying in generalities | 22:20 |
| dtroyer | the tings we have already determined are things like the top 5 (or3 or whatever) list to help everyone understand some things that we think are a priority | 22:20 |
| flwang | dtroyer: ok, i won't argue the number of contributors, as a developer working openstack for years, I know what's the happening | 22:21 |
| dtroyer | that is the sort of thing the TC can do directly. we have no actual resources to direct | 22:21 |
| dtroyer | ecept ourselves | 22:21 |
| flwang | then TC may need to think about how to leverage some resources | 22:21 |
| dtroyer | I'm not saying there are not other things we could do, I don't think it is clear yet which ones of those will pay off | 22:22 |
| *** kumarmn has joined #openstack-tc | 22:22 | |
| dtroyer | leverage resources from where? | 22:22 |
| flwang | dtroyer: at least, PTL | 22:22 |
| flwang | may be I'm the only person/PTL, i don't think TC has enough communication with PTL who maybe one of several contributors for the project | 22:23 |
| dtroyer | the TC doesn't control anything that PTLs actually spend time on, outside of setting policies that they will need to follow. have a look at the goals efforts and see how well even that level of priority setting goes for many projects | 22:23 |
| flwang | dtroyer: that's the thing cdent and i discussed days ago | 22:24 |
| dtroyer | what does work is for someone, not necessarily a TC person even, to take charge of a 'thing' and do the leg work to get everyone on board | 22:24 |
| flwang | the things TC are doing are a slights different from the contributors expect | 22:24 |
| dtroyer | that says we may have not been effective at setting expectations | 22:25 |
| flwang | dtroyer: could be, so maybe TC can send a survey to community | 22:25 |
| dtroyer | a survey that would do/ask what? | 22:26 |
| flwang | the expection gap | 22:28 |
| flwang | then we can think about how to fill the gap | 22:28 |
| flwang | so the things like, TC think the TC's scope is {1,2,3} , community think the scope of TC is {3,4,,5} | 22:29 |
| flwang | is it a bad idea to figure out the 4 and 5 and see how to improve it? | 22:29 |
| dtroyer | is that the most important thing we should be doing next? ie, are the scope things [4,5] in your example more important than [1,2]? | 22:30 |
| flwang | dtroyer: until we figure out, we don't know | 22:30 |
| flwang | at least for me, I don't think my 5 is under covered | 22:31 |
| *** diablo_rojo has joined #openstack-tc | 22:32 | |
| flwang | and the thing I'd like to clarify is, I'm not saying TC should also take care the gap 4 and 5, they could be done by other people/group | 22:32 |
| dtroyer | one problem here is that you will not get a majority of anyone to agree on this. OpenStack tires to be all things to all people, which I think is a mistake. We are not doing many of the areas we try to serve at the best of our abilities. | 22:32 |
| flwang | that's true, it's back to the atomic issue, what's the openstack? :D | 22:33 |
| dtroyer | if your thing 5 is really important to you, ultimately it is up to you to see that it gets done. it may require TC blessing, it may not, but either way that's all it is is a blessing, or a suggestion that others do not value it as much as you do | 22:34 |
| flwang | dtroyer: ok, fair enough, thanks for listening my noise | 22:35 |
| dtroyer | we know what openstack is, the problem there is those who do not like the answer keep re-phrasing that question in hopes of changing it, without just addressing that head-on. | 22:35 |
| dtroyer | flwang: it isn't noise. I hope this helps you clarify what you want to do, it helps me understand things going on that I do not see directly | 22:36 |
| dtroyer | and I hope that my sharing some of our histroy is not percieved as me trying to say no, it is meant to help understand how we got where we are | 22:36 |
| flwang | dtroyer: i know there are still people think openstack should be like blocks, it's fine, but my point is if we want to grow, we need to be integrated | 22:37 |
| flwang | the only way I can see to help the integration is the "blessing" from TC | 22:37 |
| dtroyer | I do not think that blessing would change much at all. to do the integration that I think you are looking for requires the projects to come under direction from a central authority in a manner that they do not do today. that is a pretty fundamental change, and that is the part that I think we keep sidestepping | 22:38 |
| flwang | and if that's the not the work TC should do, we need a power from another group to push it though the group could be not existed now. Before that, we need to create the group and empower it | 22:38 |
| flwang | interesting "sidestepping" | 22:39 |
| dtroyer | this new group would 'take over' the set of projects they want to integrate? | 22:39 |
| SamYaple | i/win 32 | 22:40 |
| dtroyer | ie, tell them how they need to proceed in order for everyone to be on the same page? | 22:40 |
| flwang | we got integration within those "core" projects (nova, neutron, glance...), so we got a success (somebody could argue) IaaS | 22:40 |
| * dtroyer has win32 flashbacks to NT, thanks Sam :) | 22:40 | |
| flwang | and then somebody say, OK, stop, we have a good IaaS, let's say OpenStack is a IaaS platform | 22:41 |
| flwang | if we're happy at current status, we don't have to push any integration more and just let projects born and dead | 22:41 |
| flwang | dtroyer: is that a bad world? | 22:42 |
| flwang | re " ie, tell them how they need to proceed in order for everyone to be on the same page?" | 22:42 |
| dtroyer | maybe not, but it isn't the world that we explicitly set up in 2010. that is a major change | 22:44 |
| flwang | open is double-edged | 22:44 |
| dtroyer | yup, and for some business goals, the fuzziness of control is very disconcerting | 22:44 |
| flwang | we should grow and embrace the change | 22:45 |
| dtroyer | maybe? it goes against my instincts, but then I'm not in charge of the buisness needs of any of our corporate sponsors | 22:45 |
| flwang | i believe TC has a higher level and me, but I just want to dump my mind in case it's listened carefully | 22:46 |
| dtroyer | thank you for sharing, it is very informative for me at least | 22:46 |
| dtroyer | even if we do not agree. I'll still buy you a $COLD_BEVERAGE when we next meet :) | 22:46 |
| * flwang just take a screen-shot and will show dtroyer this at Sydney summit to get free cold drink | 22:47 | |
| dtroyer | deal :) | 22:48 |
| dtroyer | also, thank you for running for the TC, we have a great slate of candidates, please do not let it stop you from trying again in the future | 22:48 |
| *** kumarmn has quit IRC | 22:48 | |
| flwang | as a diplomatic answer, I would say, no, i will definitely run for next one | 22:49 |
| flwang | but TBH, I'm not too sure | 22:49 |
| flwang | as a developer working on openstack more 6 years, I deeply care about openstack, but after discussed with you guys (you, cdent, zaneb, flaper...), I'm not sure if there is a space I can help on the higher level to help openstack at this stage. will see. hopefully i won't be layoff before next election :D | 22:52 |
| dtroyer | I am being called to dinner… remember, you don't have to actually be a TC member to have an effect and get things done | 22:53 |
| flwang | dtroyer: have a great dinner | 22:54 |
| flwang | enjoy your night | 22:54 |
| *** sdague has quit IRC | 22:58 | |
| *** hongbin has quit IRC | 23:39 | |
| *** kumarmn has joined #openstack-tc | 23:45 | |
| *** kumarmn has quit IRC | 23:55 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!