| fungi | tc-members: commence office hour | 01:00 |
|---|---|---|
| thingee | fungi: o/ | 01:11 |
| thingee | I would like to point out to the TC that the simplification ptg recap is available http://lists.openstack.org/pipermail/openstack-dev/2017-October/123086.html | 01:11 |
| fungi | excellent | 01:11 |
| thingee | My thought is to abandon the old thread http://lists.openstack.org/pipermail/openstack-dev/2017-September/thread.html#122075 and instead focus on those three (still broad) areas. | 01:15 |
| thingee | I can at least summarize the old thread. | 01:16 |
| flwang1 | thingee: did you get an answer for question "what's the current progress of the constellations effort? Was just noticing it in the tc activity email." ? | 01:16 |
| fungi | flwang1: there was some discussion of it during yesterday's office hour in here | 01:19 |
| flwang1 | fungi: cool, i will scroll up to read the log | 01:20 |
| thingee | flwang1: http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-03.log.html#t2017-10-03T07:22:58 | 01:21 |
| fungi | yeah, i guess it was before the office hour | 01:22 |
| dims | o/ | 01:24 |
| flwang1 | thingee: thanks a lot | 01:24 |
| flwang1 | I'm really interested in where the 'constellations‘ is going to as the PTL of Zaqar | 01:25 |
| flwang1 | I'm really keen to know the roadmap from TC against services out of the core | 01:26 |
| dtroyer | I have proposed a forum session for Sydney on this, hopefully we will have a good summary of where things stand for that | 01:27 |
| dtroyer | flwang1: I do not think the TC members see this as an activity that we are pushing down to the projects or community, it is a community effort to provide some clarity to common use cases for OpenStack | 01:27 |
| dims | dtroyer : fungi : thingee : i went to see the workshop by the Massachusetts open cloud folks - https://massopen.cloud/2017-moc-annual-workshop/ - some really enthusiastic people and projects. will forward links to slides when they make it available. lot of the stuff is using OpenStack projects | 01:28 |
| dims | fungi : initiated an email to those folks for getting some cloud resources for our infra | 01:28 |
| fungi | dims: also thanks for the infra intro to the moc folk! | 01:28 |
| fungi | yeah, that | 01:28 |
| flwang1 | dtroyer: great, I'm happy to see we have a session about this | 01:29 |
| dtroyer | flwang1: for a project like zaqar, I think you have to get together that sort of thing highlighting use cases for your project. I think there are a number of projects that lack common knowledge of where they fit in toreal world applications | 01:29 |
| dims | found someone doing horizon and another one doing os-profiler, so setting up intros etc to get more folks into the fold | 01:29 |
| flwang1 | dtroyer: yep, that's why I'm trying to resolve/figure out, for those projects, how can we help them | 01:32 |
| flwang1 | projects like nova, neutron, glance have got a lot adoption, but the others are not, so what i'm trying to figure out is, from the project side, what help we need? from the TC/community side, what help they can provide. | 01:33 |
| flwang1 | and unfortunately, this may be related to the questions: what's openstack and whom we're building software/service for? only ops or we do also want to serve services for developers | 01:34 |
| dims | good points | 01:41 |
| flwang1 | though I agree TC is most like a governance group, not a real technical committee like its name | 01:44 |
| flwang1 | however, from the community side, there are expections related to those "technical" problems | 01:45 |
| fungi | to compare to other communities i'm familiar with, our technical committee does provide a lot more proactive guidance rather than merely acting as an arbitrating body | 01:45 |
| flwang1 | just like cdent said "I’ve had a few people, when approached about their thoughts about the pending elections, express that they don’t think the TC does anything useful" | 01:45 |
| flwang1 | fungi: yes | 01:45 |
| flwang1 | back to the ages we have incubating process and stackforge, Zaqar was reviewed 3 times to be an 'integrated' projects | 01:47 |
| flwang1 | at that stage, we can see some active support for projects like Zaqar, but now, TBH, I can't get any sunshine from TC, so I have to expose myself here to get some light ;) | 01:48 |
| dtroyer | flwang1: What kind of support do you mean from the incubation stage? What kind of support are you expecting from the TC? | 01:49 |
| fungi | well, the technical committee isn't a marketing team... what sort of sunshine are you looking for? | 01:49 |
| flwang1 | something i said could be wrong because that's only from my narrow angle | 01:49 |
| flwang1 | I can't give a detailed list, but basically, something like I mentioned above, if openstack is still caring about the projects/services outside the core | 01:51 |
| flwang1 | because we have seen many discussion in community to ask openstack only focus on IaaS, but unfortunately, I didn't see conclusion | 01:52 |
| fungi | we have added a bunch of those, so i would say we care enough not to turn away people who want to collaborate on relevant use cases | 01:53 |
| flwang1 | fungi: yep, i can see that | 01:54 |
| fungi | the project map that ttx has been working on attempts to classify lots of kinds of projects in openstack outside the central iaas sphere | 01:55 |
| fungi | and show how the relate to each other | 01:55 |
| fungi | er, how they relate to each other | 01:56 |
| flwang1 | yep, that's the area I'm really interested in | 01:56 |
| dtroyer | flwang1: I think part of the differences in understanding that you have may be that being an official project opens the door to services being provided from (somewhere) that in actuality do not exist. like fungi said, we do not do marketing things. Projects need to be in charge of their own 'marketing' and 'promotion' for educating the community and potential deployers and consumers about the project. | 01:56 |
| fungi | though it sounds like maybe one concern is that the community/ecosystem at large is suggesting openstack should just focus on iaas use cases, and that it doesn't seem the tc as a collective body has done much to "defend" non-iaas projects from that? | 01:57 |
| flwang1 | I totally understand that, but another typical chicken-egg problem in OpenStack community is the soft/hard dependency issue | 01:57 |
| dtroyer | There are things like that map, the constellations, etc. that are part of that, but if an app dev does not now how or why she might use Zaqar then they will not consider it. There are tools that can help, such as the various openstack.org sites, but in the end the projects need to ensure that they know what use cases they are solving, and to make sure everyone else knows that too | 01:57 |
| flwang1 | generally, i agree what you said. TC is not a marketing team, but I do still think TC can play an active role to integrate the projects/services with in openstack world | 02:00 |
| flwang1 | e.g. the Barbican case, which is a good services for sure, and it's dying because losing contributor and adoption. | 02:01 |
| dtroyer | flwang1: are you saying that the TC has the ability to make any project core if it were to decide to do so? Since 'core' keeps coming up it seems like that distinction is part of the issue | 02:02 |
| dtroyer | yes, Barbican is one instance where that is possible, due to the technical nature of the project implementation | 02:02 |
| flwang1 | dtroyer: no, i mean, TC could help integration | 02:02 |
| dtroyer | can you give me an example? technical integration? or social integration? | 02:03 |
| flwang1 | technical integration | 02:03 |
| fungi | the only way the tc has really been able to "help integration" in the past is when tc members as individual developers submit patches to implement that sort of integration | 02:03 |
| fungi | it's not generally something we can legislate into existence | 02:03 |
| dtroyer | and in fungi's example there, that is not because of them happening to hold a TC seat at the time | 02:04 |
| flwang1 | fungi: yep, agree, because we're open source, so we can't force a project to integrate with another project, is it? | 02:04 |
| *** kumarmn has joined #openstack-tc | 02:04 | |
| dtroyer | not because of open source, but because of the degree of autonomy that projects do have. it is a balance | 02:04 |
| fungi | flwang1: pretty much, the only significant power we wield as a governing body is to be able to declare a project "not openstack" if they don't do something we think they should | 02:05 |
| dtroyer | between the needs of the project and the needs of the community as a whole | 02:05 |
| flwang1 | sorry, I mean "open source", you got my point | 02:05 |
| fungi | real power to bring about change like that comes from individuals, not from "the tc" per se | 02:06 |
| dtroyer | it does happen that the TC is usually made up of individuals who already have some amount of that power | 02:07 |
| fungi | it's one of the things i struggle with writing my platform for technical elections like the upcoming tc election... the things i've accomplished have been as an individual and i would have done them whether i had been a tc member or not | 02:08 |
| flwang1 | fungi: dtroyer: thanks for all the comments, sorry to make so much noise here because I'm trying to get a better understanding about TC | 02:08 |
| flwang1 | though I have been working for openstack for more than 5 years :D | 02:09 |
| fungi | flwang1: please don't apologize! you bring up very good points and it's all helpful feedback | 02:09 |
| dtroyer | flwang1: my pleasure, this helps me (us) also understand the concerns and thoughts of those in the community that we do not talk to regularly otherwise | 02:10 |
| fungi | and i value every opportunity i have to engage with others in the community on governance topics. there aren't enough people who have strong enough feelings about such things | 02:10 |
| flwang1 | I may run for TC for Queens so I need some ideas ;) | 02:10 |
| fungi | flwang1: please do run! and if you don't get elected run again | 02:10 |
| dtroyer | flwang1: please seriously consider it | 02:11 |
| flwang1 | I'm Chinese and now live in NZ, maybe you folks need some geek from a different timzone | 02:11 |
| fungi | we absolutely do | 02:11 |
| fungi | people in timezones like yours are why we added an office hour at this time | 02:12 |
| flwang1 | yep, I love the office hour :) | 02:12 |
| dtroyer | we do, we have had members from the southern hemisphere before, hopefully now wihtout the meeting schedule it will be easier on those of you who work while we sleep :) | 02:12 |
| *** kumarmn has quit IRC | 02:12 | |
| fungi | we need more participation from more parts of the world and a greater variety of cultures and technical backgrounds | 02:12 |
| flwang1 | besides, I work for a public cloud, which miss some love recently in openstack world | 02:12 |
| flwang1 | though you can argue that point | 02:12 |
| fungi | yes, more representatives from public clouds would be great too | 02:13 |
| dtroyer | to me that is also an important perspective to bring | 02:13 |
| fungi | openstack is actually well-represented in the public cloud space, just not in the usa so a lot of the people living there don't realize that | 02:14 |
| flwang1 | another well known thing is there are more investment for openstack from China companies, I think this is the area I can help | 02:14 |
| flwang1 | to bridge China/APAC user community and the openstack community | 02:15 |
| fungi | agreed, we've been asking all our more recent chinese member companies to encourage their employees to consider leadership roles within the community | 02:15 |
| dtroyer | agreed. and if you run or not, or are elected or not, please continue to work in that area | 02:15 |
| flwang1 | dtroyer: sure thing | 02:16 |
| dtroyer | as we have said before, the TC is really just those who get an official vote, much of the work and discussion happens with folk who make the effort to be a part of it directly | 02:16 |
| dtroyer | and with that, I must sign off for the night, some things to do upstairs before bed | 02:17 |
| fungi | have a good night dtroyer, thanks! | 02:17 |
| flwang1 | dtroyer: good night, thanks for all the comments/suggestions | 02:17 |
| *** flwang1 has quit IRC | 03:59 | |
| *** pabelanger has quit IRC | 05:56 | |
| *** flwang1 has joined #openstack-tc | 06:08 | |
| *** pabelanger has joined #openstack-tc | 06:21 | |
| *** jpich has joined #openstack-tc | 07:55 | |
| *** lukebrowning_ has joined #openstack-tc | 09:00 | |
| *** lukebrowning has quit IRC | 09:02 | |
| *** sdague has joined #openstack-tc | 09:38 | |
| *** cdent has joined #openstack-tc | 10:54 | |
| cdent | ttx: do you know if the survey data from the ptg has been assembled yet? | 10:57 |
| *** dtantsur|afk is now known as dtantsur | 11:22 | |
| ttx | it's been assembled yes, pretty good support for the event overall | 11:40 |
| ttx | Attendees rated the event essential to the success of the OpenStack open source project at an average of 4.28 stars | 11:41 |
| ttx | we are working on getting the contract signed for the PTG3 venue this week, ideally will be able to announce early next week | 11:42 |
| ttx | Toying with the idea of placing the TC+Board+UC thing on the Friday rather than on the Sunday | 11:43 |
| ttx | cdent: ^ | 11:43 |
| cdent | ttx: the particular data I’m after are the questions we decided to add about developer satisfaction while at the board meeting | 11:44 |
| cdent | I think having the board thing on friday is not a great idea, at least not for me: nova stuff takes up all three days | 11:44 |
| ttx | ah, good point, I'll try to get raw data for you on that | 11:44 |
| smcginnis | I think I prefer the TC+Board+UC before the PTG to have those discussions in mind for the rest of the week. | 12:05 |
| smcginnis | But that could also go the other way of having the weeks topics in mind for the board. | 12:05 |
| smcginnis | Two meetings. :) | 12:05 |
| cdent | with meetings at the start and end of each day to discuss those meetings | 12:05 |
| cdent | and required overnight reading | 12:05 |
| persia | I believe having the board meeting before the PTG gives the board more influence over the developer community, whice is probably a good thing in terms of continued funding. Having it afterwards feels like a report, and it is more difficult to influence direction remotely (especially when everyone is exhausted). | 12:09 |
| cdent | in theory that ought to be true, but the connections this last time felt quite tenuous | 12:11 |
| smcginnis | persia: I think you're right that it has the risk of ending up being just an end-of-week report of activities vs actually thinking how we would want to influence things. | 12:14 |
| persia | cdent: Yes. Those of us attending the board meeting should perhaps have put together a plan early on the Monday to make the connections less tenuous. | 12:15 |
| *** rosmaita has joined #openstack-tc | 12:47 | |
| *** lbragstad has joined #openstack-tc | 13:05 | |
| *** kumarmn has joined #openstack-tc | 13:07 | |
| *** hongbin has joined #openstack-tc | 14:03 | |
| cdent | thingee: did you get a chance to send the planned email on the neutron driver sitaution, and if so did I miss it? If not, would you like me to get it (later today)? | 14:28 |
| *** sdague has quit IRC | 14:50 | |
| thingee | cdent: I was hoping to send something out yesterday but the simplification wrap up and some contributor portal work got in the way. Please send something today please. | 15:12 |
| cdent | ✔ | 15:12 |
| *** sdague has joined #openstack-tc | 15:14 | |
| *** rosmaita has quit IRC | 15:38 | |
| *** rosmaita has joined #openstack-tc | 15:41 | |
| openstackgerrit | Hongbin Lu proposed openstack/governance master: Change email address of Zun PTL https://review.openstack.org/509523 | 15:57 |
| *** Rockyg has joined #openstack-tc | 16:22 | |
| *** jpich has quit IRC | 16:32 | |
| *** dtantsur is now known as dtantsur|afk | 16:47 | |
| *** lbragstad has quit IRC | 17:34 | |
| cdent | thingee: done | 17:44 |
| thingee | cdent: thank you | 17:56 |
| *** lbragstad has joined #openstack-tc | 17:57 | |
| *** rosmaita has quit IRC | 18:11 | |
| *** cdent has quit IRC | 18:55 | |
| *** flwang1 has quit IRC | 19:00 | |
| *** flwang1 has joined #openstack-tc | 19:20 | |
| *** Rockyg has quit IRC | 19:21 | |
| *** flwang1 has quit IRC | 19:23 | |
| *** lbragstad has quit IRC | 19:35 | |
| *** ianw is now known as ianw|pto | 20:04 | |
| *** lbragstad has joined #openstack-tc | 20:27 | |
| *** flwang1 has joined #openstack-tc | 20:41 | |
| *** kumarmn has quit IRC | 22:19 | |
| *** lbragstad has quit IRC | 22:38 | |
| *** sdague has quit IRC | 23:00 | |
| *** hongbin has quit IRC | 23:18 | |
| *** kumarmn has joined #openstack-tc | 23:49 | |
| *** kumarmn has quit IRC | 23:58 | |
| *** kumarmn has joined #openstack-tc | 23:59 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!