15:00:39 #startmeeting RDO meeting - 2017-09-06 15:00:39 Meeting started Wed Sep 6 15:00:39 2017 UTC. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:39 The meeting name has been set to 'rdo_meeting_-_2017-09-06' 15:00:40 Meeting started Wed Sep 6 15:00:38 2017 UTC and is due to finish in 60 minutes. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:43 The meeting name has been set to 'rdo_meeting___2017_09_06' 15:00:59 feel free to add last-minute topics to the agenda at https://etherpad.openstack.org/p/RDO-Meeting 15:01:01 #topic roll call 15:01:09 \o 15:01:16 o/ 15:01:27 #chair dmsimard PagliaccisCloud 15:01:27 Current chairs: PagliaccisCloud dmsimard jpena 15:01:27 Current chairs: PagliaccisCloud dmsimard jpena 15:01:50 [sensu] NEW: master.monitoring.rdoproject.org - check-delorean-pike-current @ http://tinyurl.com/y9q43qte |#| Build failure on centos7-pike/current: os-faults: http://trunk.rdoproject.org/centos7-pike/report.html 15:01:56 o/ 15:01:59 \o 15:02:01 \o/ 15:02:09 #chair jruzicka 15:02:09 Current chairs: PagliaccisCloud dmsimard jpena jruzicka 15:02:10 Current chairs: PagliaccisCloud dmsimard jpena jruzicka 15:02:36 o/ 15:02:42 #chair hguemar 15:02:42 Current chairs: PagliaccisCloud dmsimard hguemar jpena jruzicka 15:02:43 Current chairs: PagliaccisCloud dmsimard hguemar jpena jruzicka 15:02:44 * Duck o/ 15:02:47 WTG on the pike release everyone! 15:02:49 \o/ 15:03:02 #chair chandankumar 15:03:02 Current chairs: PagliaccisCloud chandankumar dmsimard hguemar jpena jruzicka 15:03:04 Current chairs: PagliaccisCloud chandankumar dmsimard hguemar jpena jruzicka 15:03:12 #chair Duck 15:03:12 Current chairs: Duck PagliaccisCloud chandankumar dmsimard hguemar jpena jruzicka 15:03:13 Current chairs: Duck PagliaccisCloud chandankumar dmsimard hguemar jpena jruzicka 15:03:21 hguemar: :-))) 15:03:27 pan pan 15:04:29 ok, let's start with the agenda 15:04:38 #topic rdopkg-0.45.0 15:05:31 chkumar246 proposed rdoinfo master: Open Queens branch for vmware-nsx tempest plugin https://review.rdoproject.org/r/9303 15:05:39 jruzicka ^^ 15:07:54 sorry 15:07:56 back 15:08:14 #info changelog in release commit message: https://softwarefactory-project.io/r/#/c/9503/1//COMMIT_MSG 15:08:33 #info Python 3 support available with python3-rdopkg 15:08:37 CLI rdopkg subpackage is using py2 until py3 is more tested 15:08:52 it contains fixes for tripleO CI/DLRN problems - unpin of old version as part of DLRN py3 support under review: https://softwarefactory-project.io/r/#/c/9515/ 15:09:14 and finally... 15:09:18 #info Fedora review is ready for approval after 2 years \o/ https://bugzilla.redhat.com/show_bug.cgi?id=1246199 15:09:20 bugzilla.redhat.com bug 1246199 in Package Review "Review Request: rdopkg - RPM packaging automation tool" [Medium,Post] - Assigned to karlthered 15:09:28 o/ 15:09:31 \o/ 15:10:04 ٩( ᐛ )و 15:10:11 2 years, I should have waited one more 15:10:18 :) 15:10:40 another good news is that, once rdopkg is packaged, DLRN can be packaged too 15:10:42 I needed to fix a thing or two before being worthy part of the distro ;) 15:11:12 * jruzicka not blocking progress 15:11:14 :D 15:12:00 I'll start building Fedora packages shortly :) 15:12:15 One question is howto use the jruzicka/rdopkg copr repo now 15:12:44 we still have to keep it around for EL7 builds or testing ground 15:13:01 for some time it will mirror Fedora until rdopkg is in all repos and then it can become a testing repo? 15:13:22 with bleeding edge/testing builds maybe? 15:14:55 Yep 15:15:07 * hguemar needs to test cbsbuild under python3 too 15:15:27 koji client is py3 compatible but it may be broken 15:16:19 hguemar, oh yeah, please do 15:16:31 that's it 15:17:14 next topic? 15:17:30 yup 15:17:43 #topic Defining core contributors policies 15:17:55 o/ 15:18:23 Recently we had requests to give core perms to people to CI repo 15:18:56 I think we need to document process and requirements as good practice for community project 15:19:38 I'll try to define a proposal for packaging, but if people can think of infra, CI repo proposals, it'd be nice 15:19:54 It will lower the psychological barrier for contributors too 15:20:20 that's interesting. Do you have any reference document we could use as inspiration? 15:20:46 i think i found one... somewhere on the openstack.org site. trying to track it down now 15:21:04 I was thinking about taking inspiration from upstream and Apache foundation 15:21:47 https://docs.openstack.org/contributor-guide/docs-review.html#achieving-core-reviewer-status 15:22:02 * hguemar is looking to find the Apache one 15:23:24 +1 15:23:30 that's a good starting point. I'll give a thought to the infra part, our repos contain stuff for several not-so-related pieces of infra, and we may want to be granular 15:23:34 there's also this https://docs.openstack.org/infra/manual/core.html 15:24:00 #action hguemar prepare a proposal to define how to become on individual packages and distro 15:24:39 jpena: Yeah, that's up to infra group to define that, you may want have different level of access 15:25:57 * hguemar has nothing more to add 15:26:13 this is going to be a short meeting, then 15:26:16 #topic roll call 15:26:19 #undo 15:26:19 Removing item from minutes: 15:26:20 Removing item from minutes: #topic roll call 15:26:24 #topic open floor 15:26:43 anything else to discuss? 15:27:17 one question: 15:27:26 Merged config master: Shorten job name for uploader periodic jobs https://review.rdoproject.org/r/9309 15:27:39 * How to reach new contributors for next action and feedback on easyfix initiatives? 15:28:18 As a follow-up, I'd like to hear from newcomers what they'd like to tackle on their next steps 15:28:26 PagliaccisCloud, snecklifter: ^ 15:28:28 i can post in the linux academy community about contributing? 15:28:36 Yep 15:28:47 Iron out details with chandankumar 15:28:57 ok 15:30:14 blog would be fine, 15:30:55 cool. we've been getting a few students asking how to get started contributing code 15:31:05 hguemar: for next steps they might need some exampels. 15:31:30 *examples 15:31:44 Depends on the area, they want to contribute too, we may want to pair them with someone 15:32:33 Better i will prepare a feedback with some questionaries for improving easyfix initative as well as next actions items? 15:32:42 hguemar: ^6 what you say? 15:32:49 ack 15:33:19 that's it from my side. 15:34:08 #topic Chair for the next meeting 15:34:16 who wants to volunteer? 15:34:32 chandankumar, https://goo.gl/e4Yyqw 15:34:38 * hguemar can't say he will get his connection fixed for sure next week 15:35:14 PagliaccisCloud: awesome thanks :) 15:35:42 * chandankumar take a look in a while 15:35:56 jpena: next week is ptg how many will be here? 15:36:20 * chandankumar will volunteer for next meeting 15:36:20 I think most of us will be around 15:36:20 Only dmsimard, trown and jschlueter from usual folks attending this meeting 15:36:47 #action chandankumar to chair the next meeting 15:37:08 I'll be going to gnocchi sprint at local pycon the week after that 15:37:44 * hguemar hopes that they will bring some pecorino 15:38:03 hguemar: :-) 15:38:25 * chandankumar is having fun with tempest plugins split. 15:38:49 if there are no more topics, let's get our 20 minutes back 15:39:05 #endmeeting