17:01:13 #startmeeting murano 17:01:14 Meeting started Tue Aug 26 17:01:13 2014 UTC and is due to finish in 60 minutes. The chair is ruhe. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:17 The meeting name has been set to 'murano' 17:01:25 #link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda 17:01:51 murano team, are you here? 17:02:24 Hi 17:02:30 sergmelikyan, katyafervent, slagun, sjmc7: ping 17:02:30 Hi o/ 17:02:33 hi 17:03:16 would someone like to add a topic for discussion before we begin? 17:03:33 \o/ 17:03:53 ok. we can add more topics while we go 17:03:56 #topic action items review 17:04:01 there was only one 17:04:07 gokrokve_ to create an etherpad for team to fill pros and cons of becoming a part of two programs vs having our own program 17:04:27 gokrokve_: took it a bit differently and send an email with this idea to public mail 17:04:35 #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/043602.html 17:04:51 it sounded like the glance team were enthsuastic, heat much less so 17:05:07 that's correct 17:06:37 this idea came up as a result of feedback from TC. but since heat team is not so enthsuastic about this. but all of that is still a useful feedback 17:07:02 * but since heat team is not so enthsuastic about this we can build our next steps on that 17:07:46 sorry, i had too many meetings today. my brains works slow 17:08:05 we can continue on this topic in open discussion 17:08:14 #topic juno-3 release 17:08:22 #link https://wiki.openstack.org/wiki/Juno_Release_Schedule 17:08:27 that's just a heads up 17:09:05 we're following general openstack release schedule, so we're going to release munora juno-3 on september 4 17:09:45 actual juno release is targeted for october 16. so we can spend that time on bug fixing and documentation improvements 17:10:18 our team should have some more time for upstream stuff midway through september i think 17:10:39 our first release is keeping us busy 17:11:36 sjmc7: i hope that lessons learned during your release will help to improve murano, i know they will 17:12:17 anything else for this topic? 17:12:44 #topic documentation improvements in juno 17:13:04 so, katyafervent put up a document with items we can improve in our docs 17:13:13 #link https://etherpad.openstack.org/p/murano-docs 17:13:22 folks, please review this document 17:13:41 feel free to add more items and/or comment on importance of each item 17:14:23 i'll create an action item for katyafervent to send out notice about this work to ML list 17:14:33 Ok 17:14:50 #action katyafervent send out a notice about documentation improvements in murano 17:15:48 sjmc7: you said that your team is going to work on documentation. is it in juno time frame? 17:15:57 during september 17:16:16 great 17:16:19 so i think we could get it merged back within juno timeframe 17:17:27 sjmc7: will you have time to review this document? maybe, mark the items your team needs to have. just to avoid work duplication 17:17:39 i'll make sure our docs team know about it 17:17:43 it's not our developers writing it 17:17:49 ah. thanks 17:18:06 anything else for this topic? 17:18:48 no 17:19:17 40 minutes left and we're ready to switch to #open discussion 17:19:23 #topic open discussion 17:19:42 Will we support getting-started guide? 17:20:24 katyafervent2: if we have documentation we either support it or get rid of it (in case if it's obsolete) 17:20:40 Having only developers oriented documentation is wrong, we have few group of users and we should have clean targeted documentation 17:20:57 Ok, so it should be totally reworked 17:21:10 ours will be user-oriented 17:22:44 slagun: are you here? 17:22:53 o/ 17:23:06 do you have any updates on "trusts"? 17:24:28 I tried several alternate approaches and it seems that trust is the only option for nod though I not like it much. Currently I updating engine's code to support new approach 17:24:58 I thing I'll finish by Thursday (tomorrow gonna be yaql day) 17:25:08 *think 17:25:30 ok. so, theere is a good chance we get trusts in juno 17:26:15 anything else for today? 17:27:48 do we have super critacal bugs? 17:28:09 we have several bugs with high priority 17:28:12 will we do a blueprint review someday? 17:28:25 what time do we have until the code freeze? 17:28:29 katyafervent2: i'll review blueprints and contact people in person 17:28:44 katyafervent2: as i said juno-3 is targeted for september 4 17:29:10 and after juno-3 is code freeze? 17:29:28 no, there will be release candidates 17:29:41 we will accept only bug fixes during that phase 17:29:45 https://wiki.openstack.org/wiki/Juno_Release_Schedule 17:29:48 ok 17:29:53 thanks for the link 17:31:40 i guess we can wrap up early today 17:32:07 and get back to our routine 17:32:10 Goodbuy everyone! 17:32:22 *Goodbye 17:32:34 thanks eveyrone and goodbye 17:32:42 thx 17:32:48 #endmeeting