14:01:39 #startmeeting trove 14:01:40 Meeting started Wed Sep 26 14:01:39 2018 UTC and is due to finish in 60 minutes. The chair is dkrol. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:44 The meeting name has been set to 'trove' 14:01:50 Hello 14:01:58 Hello 14:02:16 hi 14:02:19 let's wait a few more minutes for others 14:02:23 mpiwowarczy: hi 14:03:16 #topic roll call 14:06:01 so only three of us today ? :) 14:06:24 still stable :) 14:06:54 I think we can start 14:06:59 great 14:07:18 #topic Core team members 14:07:35 bzurkowski: you added this topic to our discussion 14:07:40 Yes 14:08:09 I did the math and it turns out that we have only 4 active core members in this release 14:08:57 Marcin is with us for a longer time a does great job reviewing changes and commiting new fixes 14:09:14 I suggest adding him to the core team 14:09:42 hmm... but why do we need more core contributors ? 14:10:26 Because we need to facilitate the progress in the project 14:10:55 We have a lot of opened changes with many +1s or single +2s 14:11:06 do you think our current progress (I mean pace of merging) is too low ? 14:12:34 from my side I offer my work on review work 14:12:36 I have an impression that often a second core is missing that would approve the change 14:12:47 if it is needed I can help as core member :) 14:13:25 I get it 14:13:41 so we can vote but there are only two of us right now ? 14:13:57 it's not a lot :) 14:14:11 but I do not vote for nothing as it is about me :) 14:15:13 it seems we don't have quorum of core contributors right now 14:15:56 otherwise I agree with you, Marcin should be recognized as a core contributor 14:16:02 dkrol: You are right, but this is what we had for several past meetings... 14:16:40 I'm voting in favor of adding Marcin to the core team 14:17:40 shouldn't we try to contact them first ? 14:17:57 at least try to 14:18:43 can we do that on mailing list or somewhere? 14:19:24 we can get emails from gerrit and send them an invitation 14:19:33 and do the voting next week 14:19:51 dkrol: Yes, let's ask others about their opinion 14:19:56 will it be ok for you ? 14:20:37 dkrol: Sure 14:20:49 ok, thank you for understanding 14:21:12 #topic Recent changes and reviews 14:21:21 lets move to recent changes 14:21:53 from my side ... 14:22:04 I saw several python3-first changes 14:22:35 and I sent an email to stable branches mainteners 14:22:53 and I was asked a question: "is python3 support going to be backported to stable branches?" 14:23:11 and this seems to be a very good question 14:23:45 my first impression after reading https://docs.openstack.org/project-team-guide/stable-branches.html 14:23:48 #link https://docs.openstack.org/project-team-guide/stable-branches.html 14:24:13 how it is in other projects? 14:24:15 was that python3 should not be backported to stable branches 14:24:26 I didn't check it 14:24:51 but we should have our own opinion as well 14:25:05 before taking a look at other projects 14:26:10 what is your opinion ? 14:26:46 definitely you are right 14:27:08 but AIK only important changes are backported to stable branches 14:28:20 moreover python3-fists doeasnt have any functional changes, hence, what is a reason to backort them? 14:29:25 if anybody want to use trove trove in new python, will also use latest Trove version 14:29:45 I'm wondering why they are pushing python3-first changes so deep, up to ocata stable branch 14:29:50 I would think so too 14:30:14 maybe we could ask goal champions about it ? :) 14:30:16 Ocata and some subsequent branches will be dropped until Python 3 comes 14:30:29 The thing is that this is not happening by mistake, but defined explicitely in goal tools 14:30:33 #link https://github.com/openstack/goal-tools/blob/4125c31e74776a7dc6a15d2276ab51ff3e73cd16/goal_tools/python3_first/jobs.py#L54 14:30:48 dkrol: We should ask goal champions as you suggest 14:31:44 #action ask python3-first goal champions about supporting stable branches 14:32:13 ok 14:32:21 keep in mind, there is a lot of changes in python3-firsts tasks 14:32:28 besides this - do you have anything elso ? 14:32:43 else about recent changes ? 14:32:49 it is always a little risky to pull these changes to stable releases 14:33:06 dkrol: Nothing more from my side 14:33:37 im working on moving functional tests to python3 - https://review.openstack.org/#/c/604816/ 14:33:48 but it is still in progress 14:34:20 want to use tox and wrap trovestack script in virtualenv to execute int_tests 14:34:41 that is all from my side 14:34:42 ok 14:34:52 from my side - I'm working on trovestack redesign but I didn't push anything yet 14:35:10 I think in the following week there will be something to report :) 14:35:26 #topic Trovestack redesign 14:36:05 we can change a topic now 14:36:26 One moment 14:36:27 so basically I was working on extracting minimal code to build mysql image 14:36:55 OK, continue 14:37:02 ok 14:37:15 I thought you were gonna skip trovestack redesign topic 14:37:43 it turned out trovestack is a bigger monolith I was thinking 14:38:22 it is not trivial to extract anything from it 14:38:52 there is a mix of functions in trovestack, functions and functions_qemu files 14:39:02 and they are tightly coupled :) 14:40:40 I'm at the moment where I have a seperate script for building minimal ubuntu mysql image which passes trovestack tests 14:41:24 I need to do some working on refactoring and verification but it should be ready for review in the follwoing week 14:41:38 how about you ? do you have anything on this topic ? 14:42:11 So finally you wrote image building script from scratch, right? 14:42:34 Based on existing code in trovestack 14:42:45 yes 14:43:00 and also trove registration script 14:43:19 once the image is built it has to be registered 14:44:51 ok, lets move on to the next topic 14:44:59 since we are running out of time 14:45:03 #topic Python 3 first support 14:45:17 mpiwowarczy: do you have any update about it ? 14:46:14 nothing more than functional test 14:46:32 we are still unable to update any point from https://etherpad.openstack.org/p/trove-python-3 14:46:40 :( 14:47:02 ok 14:47:09 lets move to the last topic 14:47:10 dont worry, work goes forward :) 14:47:15 #topic Building the community 14:47:24 bzurkowski: :) 14:47:52 dkrol: :) 14:48:11 I added this topic to talk about condition of Trove community 14:48:15 bzurkowski: the floor is yours 14:49:41 We all want to achieve great goals in this project by introducing advanced features and improvements 14:50:23 +1 14:50:40 However, we cannot make progress without the right number of people involved in the project 14:51:49 I looked at previous meetings from several years ago 14:52:32 There were 20 people instead of three during each weekly meeting 14:52:53 There were special meetings for discussing only blueprints 14:52:55 #link https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting 14:53:19 maybe we sould consider add something like "quick start" to documentation 14:53:23 Let's collect ideas about how we could put life back into the project 14:53:34 it will make it easier start working with Trove 14:54:38 bzurkowski: do you have anything specific on mind ? or do you want to start brainstorming about it ? 14:54:39 for now it isnt easy for newbies bring up trove with instances 14:54:46 The meeting is almost over so I suggest creating a pad for ideas 14:54:54 We could review it in the next week 14:55:08 dkrol: Rather start brainstorming 14:55:32 #link https://etherpad.openstack.org/p/trove-revitalization 14:55:33 Marcin's idea is a good start 14:55:40 how about it ? :) 14:56:11 dkrol: Thanks :) 14:56:29 ok, so let's have this discussion next week 14:56:39 thanks for coming today 14:57:15 bye 14:57:18 #endmeeting