14:00:17 <devkulkarni> #startmeeting Solum Team Meeting
14:00:26 <openstack> Meeting started Wed Aug 24 14:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:29 <openstack> The meeting name has been set to 'solum_team_meeting'
14:00:35 <devkulkarni> #topic Roll Call
14:00:40 <pt_15> Hey!
14:00:46 <devkulkarni> hi pt_15
14:00:48 <zhurong> 0/
14:00:52 <devkulkarni> hi zhurong
14:01:01 <pt_15> Hey devkulkarni zhurong :)
14:01:12 <devkulkarni> lets wait for few minutes to see if others join us today
14:01:34 <zhurong> hi devkulkarni pt_15
14:02:08 <devkulkarni> alright, lets get started
14:02:19 <caowei> hi devkulkarni pt_15 zhurong
14:02:24 <devkulkarni> hi caowei
14:02:33 <pt_15> Hey caowei :)
14:03:13 <devkulkarni> I have two main things on agenda for today: 1) solum-dashboard patches discussion 2) openstack summit
14:03:38 <devkulkarni> pt_15, zhurong: I am going through the solum-dashboard patches
14:04:24 <devkulkarni> pt_15: on https://review.openstack.org/#/c/344599/6 .. can you create a bug to track the work regarding the point that caowei brought up
14:05:11 <pt_15> devkulkarni: yeah, just saw that too! I'll do that asap :)
14:05:21 <devkulkarni> pt_15: and looks like this patch is in merge conflict: https://review.openstack.org/#/c/344675/
14:06:01 <devkulkarni> pt_15: just wanted you to be aware that because there are several patches outstanding, when some of them will merge, others may get merge conflict
14:06:10 <pt_15> yeah I've not made any changes to the update patch in a while
14:06:38 <devkulkarni> the merge conflict must be because few other patches just got merged
14:06:39 <zhurong> there patch have the order,
14:06:49 <devkulkarni> +1 zhurong
14:07:10 <devkulkarni> actually, if the patches are dependent on each other then there should be no merge conflict
14:07:11 <zhurong> should merge one by one as the pt_15 submit order
14:07:31 <pt_15> yeah, I actually made changes to other patches but didnt rebase the update one since it required another bug to be fixed first
14:07:53 <zhurong> yep, submit the next one, should also rebase the prev one
14:08:02 <devkulkarni> ah okay.. in that case you want to update the update patch and resubmit it
14:09:07 <devkulkarni> pt_15: btw, once all the app patches have merged, there is one last thing outstanding
14:09:24 <devkulkarni> that is to get rid of the assembly tab and the code related to assemblies
14:09:43 <devkulkarni> you can do it whenever you get time
14:11:51 <pt_15> devkulkarni: oh yes, I'll do that within the next few days :)
14:12:49 <devkulkarni> pt_15: cool.. and can you create a screencast? we can put that on Solum wiki
14:14:36 <pt_15> devkulkarni: yes I'll do that in the next couple of days too :)
14:14:48 <pt_15> I actually wanted to ask you something with regard to thag
14:14:50 <pt_15> * that
14:14:53 <devkulkarni> ok sounds good..
14:14:54 <devkulkarni> sure
14:14:58 <devkulkarni> go ahead
14:15:13 <pt_15> My setup is a little slow, so will that be a problem for the screen cast video?
14:16:21 <devkulkarni> it should not be. once you have recorded the video, you can edit it to make it shorter by removing some of the waiting period
14:17:00 <pt_15> OK cool! I'll make the video and share it with you in a couple of days at max :)
14:17:13 <devkulkarni> video length between 4 - 5 minutes is not an issue from viewer's perspective
14:17:39 <devkulkarni> anything beyond that and you will loose viewer's interest
14:18:17 <pt_15> Yes, that's true. I'll try and keep it as short as possible :)
14:18:32 <pt_15> While also showing all the features properly
14:18:45 <devkulkarni> yes, that is the right goal
14:19:31 <pt_15> Great! :)
14:19:39 <devkulkarni> pt_15: also feel free to showcase your work if any opportunities arise (such as class presentations or project presentations etc.)
14:20:32 <pt_15> Yes I'll definitely do that! :)
14:21:13 <devkulkarni> and if it is a public forum, share with us the announcement; we can put that on Solum wiki
14:22:02 <devkulkarni> any other thoughts/questions on the topic of solum-dashboard?
14:22:07 <pt_15> OK, cool, sure will do! :D
14:22:27 <pt_15> Nope, I think that's pretty much it from my side for now :)
14:23:36 <devkulkarni> alright. thanks pt_15 for working on this over the summer. it has added value to the project. thanks zhurong for guiding and helping pt_15 during this period
14:24:30 <pt_15> Not a problem at all devkulkarni, it's been my pleasure working on this! :)
14:24:36 <zhurong> Actually almost done by pt_15 herself
14:24:57 <zhurong> great job pt_15
14:25:06 <pt_15> Thanks a lot zhurong for all your help and guidance :)
14:25:15 <devkulkarni> collaboration wins :)
14:25:28 <pt_15> And thank you very much devkulkarni too for your guidance too! :d
14:25:38 <pt_15> Definitely does! :)
14:26:00 <devkulkarni> :)
14:26:17 <devkulkarni> ok, the second topic I have is about openstack summit in barcelona
14:26:43 <devkulkarni> are any of you planning to attend it?
14:26:56 <zhurong> topic result comes out?
14:27:07 <devkulkarni> I don't think so.. let me check
14:27:08 <pt_15> I'm certainly hoping to be able to attend it :)
14:28:06 <zhurong> we need have the topic, then can attend it
14:28:53 <devkulkarni> zhurong: have you submitted any talks?
14:29:18 <devkulkarni> good morning vijendar
14:29:27 <vijendar> hi
14:29:46 <devkulkarni> hi vijendar.. we were just discussing about openstack summit
14:29:54 <pt_15> Hey vijendar :)
14:30:11 <vijendar> pt_15: hi
14:30:14 <vijendar> ok
14:30:24 <devkulkarni> so one thing that I need to let the organizers know is our requirements
14:30:37 <zhurong> yep,  My friend and I have a joint topic. but haven't know can be chose.
14:30:41 <vijendar> ok.. how many slots are we getting this time?
14:30:43 <devkulkarni> for Austin summit we had 1 fishbowl session and 1 work session.
14:30:56 <devkulkarni> that is what I wanted to discuss
14:31:14 <devkulkarni> last time the fishbowl session was well attended but the work session was not
14:31:28 <devkulkarni> so I was thinking we can go with just the fishbowl session
14:31:30 <vijendar> correct
14:31:57 <vijendar> ok
14:32:14 <vijendar> when do we know if our talks got accepted or not?
14:32:28 <devkulkarni> for those of you who have not attended an openstack summit before
14:32:58 <devkulkarni> a fishbowl session is one where we get to give presentation about the current status of our project. it is intended for general audience
14:33:26 <devkulkarni> a work session on the other hand is where project contributors get together and discuss/debate about topics related to that project
14:34:30 <devkulkarni> last time we had only few of us for the work session
14:34:49 <devkulkarni> both these are for 50 minutes
14:35:02 <devkulkarni> vijendar: no, the results are not out yet
14:35:32 <zhurong> devkulkarni seem i know some result
14:35:43 <devkulkarni> zhurong: really?? are the results out?
14:36:55 <zhurong> devkulkarni I got a result from a tracter
14:37:30 <devkulkarni> you mean track chair?
14:37:42 <zhurong> yep
14:37:54 <devkulkarni> cool. I am sure the results should be out soon.
14:38:20 <zhurong> will get out in the week
14:38:33 <vijendar> nice
14:38:36 <zhurong> what your topic name?
14:38:36 <devkulkarni> this week? or next week?
14:39:04 <devkulkarni> there were two — one was a talk and another was a workshop
14:39:13 <zhurong> He said maybe this weekend
14:39:42 <devkulkarni> cool.. I think we can wait till next week then to know for sure
14:39:58 <zhurong> I got the topic name, you should give some key words in the topic name
14:40:44 <devkulkarni> btw there is one another thing that has happened recently — the openstack tc have decided to split the design summit and the main conference starting from the Boston summit
14:41:13 <devkulkarni> the design summit is where all the design discussions will happen
14:41:27 <devkulkarni> and main conference will have more consumer focused things
14:42:02 <devkulkarni> the main implication for us is that we may not get space in the design summit because we are a project that is tagged "single-vendor".
14:42:50 <zhurong> yep, many project had the "single-vendor" tag
14:43:05 <devkulkarni> openstack tc defines a set of tags and apply them to projects.. the "single-vendor" tag means that there are 90% code or reviews are done by folks from a single vendor/company
14:43:15 <devkulkarni> correct zhurong
14:43:47 <zhurong> we have 36 months to solve this
14:44:26 <devkulkarni> so there has been on-going discussion about a) what to do of projects that are single-vendor for 18 months after getting into big-tent and b) ways to get rid of this tag
14:44:48 <devkulkarni> zhurong: my understanding is it was 18 months from the time a project comes into big tent
14:44:55 <devkulkarni> anyways
14:45:19 <zhurong> maybe i misunderstand this
14:45:26 <zhurong> my pool English
14:45:49 <devkulkarni> one of the points that some of the community members have proposed is to remove such projects from the openstack bit tent after 18 months
14:45:59 <devkulkarni> let me share an email thread where all this was being discussed
14:46:21 <zhurong> I subscribe the ML
14:46:44 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2016-August/100796.html
14:47:00 <devkulkarni> then you must have already read this thread
14:47:14 <devkulkarni> so what does this mean to us —
14:48:26 <devkulkarni> 1) if we want our project to remain in the openstack big tent then we need to work towards trying to improve reviews/patches from non rackspace folks.. I think we have been making good progress on this already.. you all have contributed quite a lot in recent months
14:48:40 <zhurong> We should have more cores besides from rackspace, and more contribute from others :D
14:48:42 <devkulkarni> this is apparent from the stacklytics
14:48:55 <devkulkarni> zhurong: definitely..
14:49:23 <devkulkarni> zhurong: I think you are definitely on the path to become a core for solum-dashboard imo..
14:50:25 <devkulkarni> for the solum and python-solumclient, once any of you submit some patches and get some reviews on your names, it can happen there too
14:51:28 <devkulkarni> so yes, we need more cores, and the best way to become a way to submit patches and do reviews.. let me know if any of you are interested in this.. I can work with you to identify the right work that can help you become a core
14:51:49 <devkulkarni> second implication of all this single-vendor discussion is that
14:51:49 <zhurong> yep, this is the reward for the contributor
14:53:03 <devkulkarni> lets say we are not able to get rid of the single-vendor tag till Boston summit, then there are two possibilities — our project may get removed from OpenStack big tent or, we might still be in the big tent but we may not get space at the design summit
14:53:57 <devkulkarni> moving forward, the openstack tc is thinking of providing space at the design summit and the conference only to those projects that are in big tent and don't have single-vendor tag on them
14:54:42 <devkulkarni> so we have till the Boston design summit to change our situation
14:54:49 <zhurong> I can not understand what different from big tend and not big tend
14:55:10 <zhurong> Now all the project using the OpenStack namespace
14:55:32 <zhurong> using the same jenkins resource
14:56:13 <devkulkarni> zhurong: good question. so the main difference is the awareness that it creates.. also, recently the openstack marketing committee has started discussing about logos and marketing for various big tent projects..
14:56:26 <devkulkarni> but otherwise you are right
14:56:45 <devkulkarni> we can still use the Openstack namespace and the upstream gating resources
14:57:18 <devkulkarni> anyways, just wanted to bring all of this to your attention
14:57:48 <devkulkarni> we can continue to discuss/debate about this next week
14:58:00 <devkulkarni> as we are at the end of the time today
14:58:09 <devkulkarni> any thoughts/questions before we end?
14:58:58 <devkulkarni> zhurong: one another point is space at the OpenStack conference (probably this will also be reserved for big tent projects)
14:59:26 <devkulkarni> nothing is set in stone yet and the discussion is still pretty much evolving at the tc-level.
14:59:36 <zhurong> thx for your explain devkulkarni
14:59:57 <devkulkarni> I am glad this helped
14:59:58 <devkulkarni> alright
15:00:03 <devkulkarni> thanks for joining today
15:00:06 <devkulkarni> see you next week
15:00:09 <devkulkarni> #endmeeting