15:00:43 <amoralej> #startmeeting RDO meeting - 2017-10-04
15:00:43 <openstack> Meeting started Wed Oct  4 15:00:43 2017 UTC and is due to finish in 60 minutes.  The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:46 <openstack> The meeting name has been set to 'rdo_meeting___2017_10_04'
15:00:54 <amoralej> #topic roll call
15:01:11 <chandankumar> \o/
15:01:13 <rbowen> yo
15:01:15 <jpena> o/
15:01:19 <jschlueter> o/
15:02:12 <amoralej> #chair chandankumar rbowen jpena jschlueter
15:02:13 <openstack> Current chairs: amoralej chandankumar jpena jschlueter rbowen
15:02:55 <jruzicka> ☺
15:03:04 <amoralej> #chair jruzicka
15:03:05 <openstack> Current chairs: amoralej chandankumar jpena jruzicka jschlueter rbowen
15:03:26 <chandankumar> jruzicka: which client you use?
15:03:41 <chandankumar> jruzicka: i did not get smiles on weechat
15:03:44 <jruzicka> chandankumar, hexchat. has it's problems, but which IRC software doesn't :)
15:03:47 <number80> o/
15:04:03 <jruzicka> chandankumar, yeah I'm pushing for unicode this way ;)
15:04:03 <number80> chandankumar: update weechat, it works :)
15:04:13 <chandankumar> number80: sure.
15:04:45 <amoralej> #chair number80
15:04:46 <openstack> Current chairs: amoralej chandankumar jpena jruzicka jschlueter number80 rbowen
15:04:46 <amoralej> ok
15:04:49 * number80 prefers old style smileys
15:04:56 <amoralej> let's start with the first topic
15:04:59 <rbowen> :)
15:05:08 <amoralej> #topic ci-config cores
15:05:25 <amoralej> #info https://www.redhat.com/archives/rdo-list/2017-September/msg00008.html
15:05:36 <amoralej> i'm not sure who added that
15:06:17 <amoralej> anyone know who added that topic?
15:06:21 <number80> apevec: ^
15:06:42 <apevec> I have not, I just added comment
15:06:45 <apevec> adarazs, ^ ?
15:06:48 <myoung> o/
15:06:54 <apevec> he posted it on rdo-list
15:07:00 <number80> oh, I assumed from the colors
15:07:00 <adarazs> apevec: hi
15:07:03 <amoralej> #chair myoung
15:07:04 <openstack> Current chairs: amoralej chandankumar jpena jruzicka jschlueter myoung number80 rbowen
15:07:05 <number80> #chair myoung
15:07:06 <openstack> Current chairs: amoralej chandankumar jpena jruzicka jschlueter myoung number80 rbowen
15:07:11 <adarazs> apevec: it was weshay, but it might as well have been me :)
15:07:13 <adarazs> o/
15:07:33 <adarazs> amoralej: ^
15:07:42 <amoralej> so, we need to define some policies about how to become core to config
15:07:43 <adarazs> so anyway, we would like to get those rights, and we don't know what else to do.
15:08:21 <apevec> adarazs, sign here, in blood ;)
15:08:32 <Duck> quack
15:08:49 <adarazs> apevec: sure, that's standard procedure I think :)
15:08:51 <apevec> seriously, I've linked some other infras guidelines, we could look at that
15:08:52 <chandankumar> #chair Duck
15:08:52 <openstack> Current chairs: Duck amoralej chandankumar jpena jruzicka jschlueter myoung number80 rbowen
15:09:00 <Duck> chandankumar: thanks :-)
15:09:17 <trown> o/
15:09:22 <amoralej> #chair trown
15:09:24 <openstack> Current chairs: Duck amoralej chandankumar jpena jruzicka jschlueter myoung number80 rbowen trown
15:09:27 <adarazs> yeah but instead of trying to make an example out of us and blocking this for another month, can we just get the blessings and you can develop these policies in peace? :)
15:09:32 <number80> Well, from a general perspective, having clear guidelines to determine how one can become core is healthy
15:09:55 <number80> (up to infra group to determine what are the requirements)
15:10:27 <adarazs> or is there something against us submitting stuff regarding our job definitions there?
15:10:29 <amoralej> just note that granting permissions to config project will provide access not only to ci, but to all review.r.o config, there is no separated repo for ci config
15:11:05 <adarazs> yeah, maybe we should change that. I don't want to have access to all those, but it feels important to be able to change the jobs we rely on for upstream CI.
15:11:23 <jatanmalde> o/
15:11:42 <amoralej> adarazs, i'm in favor of having folks from ci team to submit ci jobs, you are much more familiar that us to tripleo jobs configs
15:11:50 <dmsimard> adarazs is already core
15:11:53 <amoralej> #chair jatanmalde
15:11:54 <openstack> Current chairs: Duck amoralej chandankumar jatanmalde jpena jruzicka jschlueter myoung number80 rbowen trown
15:12:13 <adarazs> yeah, but I got added long time ago by apevec for some not related testing I did.
15:12:24 <adarazs> :)
15:12:28 <trown> otoh... it is slightly better already then the current relationship between tripleo-ci and openstack-infra... at least we have a couple folks who can merge stuff
15:12:39 <adarazs> yeah.
15:12:48 <number80> If the issue is that perms == too much access, we can work toward isolating roles maybe?
15:13:34 <amoralej> #info current comitters are https://review.rdoproject.org/r/#/admin/groups/6,members
15:14:01 <dmsimard> We're not going to make everyone core but on the other hand we do not have criterias for becoming core. I would suggest that you propose two cores, we get a consensus on these two and we ramp them up on non-obvious things
15:14:54 <dmsimard> The policy for reviewing would be one of trust, not unlike what is happening in TripleO right now where people review things they are familiar on and may not approve something they aren't familiar with
15:15:29 <amoralej> adarazs, ^ what do you think?
15:15:34 <rdogerrit> Aditya Ramteke proposed openstack/designateclient-distgit rpm-master: Moved package description to global variable.  https://review.rdoproject.org/r/9897
15:15:39 <dmsimard> i.e, if you're changing something that is not tripleo-specific (pipelines, nodepool config, shared jobs, etc.), we need to have a "rdo" core to weigh in
15:15:57 <number80> dmsimard: sounds like a good plan
15:16:02 <amoralej> +1
15:16:06 <adarazs> this is what I expected... "please only submit to these parts that you understand, enjoy your core rights" :)
15:16:08 <trown> amoralej: is that accurate... could swear I have +2'd there
15:16:20 * number80 thinks myoung is a good candidate
15:16:22 <amoralej> trown, yes
15:16:22 <amoralej> https://review.rdoproject.org/r/#/admin/groups/2411,members
15:16:37 <amoralej> provenpackages also have +2/-2
15:16:40 <dmsimard> I think this is all common sense but we can formalize it in writing somewhere
15:16:43 <trown> ah ok
15:16:50 <amoralej> #undo
15:16:51 <openstack> Removing item from minutes: #link https://review.rdoproject.org/r/#/admin/groups/2411,members
15:17:04 <amoralej> #undo
15:17:05 <openstack> Removing item from minutes: #info current comitters are https://review.rdoproject.org/r/#/admin/groups/6,members
15:17:18 <number80> amoralej: well, it's useful to have them but only use them for emergencies
15:17:31 <amoralej> #info current commiters are  https://review.rdoproject.org/r/#/admin/groups/6,members and https://review.rdoproject.org/r/#/admin/groups/2411,members
15:17:37 * number80 don't give +W on infra reviews
15:18:08 <number80> If we have enough infra cores, I'd be ok to reconsider
15:18:26 <jpena> I'd suggest to start with dmsimard's proposal, and I can propose a formal policy somewhere in https://www.rdoproject.org/infra/
15:18:30 <adarazs> so yeah, this is what I expected. otherwise better ACLs are welcome, but for now I think we could just get some more people on that core list. sshnaidm|pto and panda are not going to (willfully ;) destroy things. :)
15:18:39 <adarazs> + trown
15:19:00 <trown> I have +2 through provenpackagers
15:19:02 <amoralej> #action jpena to propose a formal policy about becoming core for infra
15:19:08 <trown> because a long time ago I proved I can package
15:19:23 <jschlueter> hmm I don't have permissions to see the second linke to 2411,members
15:19:31 <adarazs> trown: makes sense then to have all the rights for everything else then ;)
15:19:43 <dmsimard> let's start with no more than two formal cores, we can revisit later if we need to.
15:20:00 <number80> jschlueter: you shouldn't need perms for that, unless you're not logged in
15:20:05 <dmsimard> this doesn't prevent anyone from sending patches, it makes it easier to merge them
15:20:15 <adarazs> number80: FWIW I don't see that link either.
15:20:36 <adarazs> number80: while logged in.
15:20:39 <jschlueter> I'm logged in but it gives me an error and shows nothing
15:21:00 <number80> Well, I have that when I try to look as anonymous user
15:21:01 <jschlueter> Code Review - Error
15:21:01 <jschlueter> The page you requested was not found, or you do not have permission to view this page.
15:21:16 <Duck> number80: same problem on the second link
15:21:29 <jschlueter> first link I can see
15:21:33 <amoralej> jschlueter, can you see https://review.rdoproject.org/r/#/admin/groups/6,members?
15:21:35 <adarazs> anyway, so do I have to propose sshnaidm|pto and panda again here formally? or do I have to propose myself again?
15:21:37 <number80> (first rule of the provenpackager group, you can't see the list of the group)
15:21:50 <adarazs> hehe :)
15:21:51 <jschlueter> amoralej: yes
15:21:57 * jschlueter nods to number80
15:23:08 <number80> Well, let's see with SF folks later
15:23:18 <Duck> number80: why hide the list at all?
15:23:36 <number80> Duck: I don't know, I don't understand gerrit configuration at all
15:23:46 * Duck hahaha :-)
15:23:57 <amoralej> :)
15:24:04 <dmsimard> adarazs: I'm +1 on sshnaidm|pto but I can't +1 panda. He's improving but needs more time.
15:24:31 <dmsimard> adarazs: you are a fine candidate however
15:25:05 <adarazs> okay, with trown, Sagi and myself we have enough people to submit stuff there when necessary if we have some emergency.
15:25:23 <dmsimard> jpena, apevec, amoralej, number80 ^ ack ?
15:25:28 <jpena> +1
15:25:29 <amoralej> +1
15:25:32 <number80> +1
15:25:35 <adarazs> anyway you guys made good and quick reviews on our changes, but I think most of the time it doesn't really make sense for you to spend time on our job changes.
15:25:37 <rdogerrit> Aditya Ramteke proposed openstack/networking-bigswitch-distgit rpm-master: Moved package description to global variable.  https://review.rdoproject.org/r/9871
15:25:52 <number80> adarazs: we agree on that
15:25:54 <amoralej> #agreed to give core access to config project to adarazs trown and sshnaidm|pto
15:26:22 <number80> done
15:26:29 <dmsimard> didn't get apevec's ack but democracy ?
15:26:33 * number80 updated the group
15:26:47 <amoralej> maybe we coulud use a office hours session to cover config project
15:26:53 <dmsimard> number80: no don't do that
15:27:00 <dmsimard> number80: you need to use the resources config
15:27:06 <number80> ack
15:27:08 * number80 undo
15:27:30 <number80> Attila was already in the group
15:27:39 <chandankumar> amoralej: +1 may be any day in tuesday RDO office hour
15:29:29 <jschlueter> chandankumar: that would actually be a decent idea, from my point of view
15:29:40 * apevec tests democracy++
15:29:41 <apevec> -1
15:29:44 <jschlueter> get a few more people paying attention to things during office hours
15:29:44 <apevec> now what :)
15:30:10 <jschlueter> apevec: you didn't -2 so still passes :-)
15:30:22 <apevec> correct answer!
15:30:32 <chandankumar> adarazs: what about a sessioon on project-config in rdo office hour?
15:30:36 <chandankumar> *session
15:30:49 <adarazs> thanks folks for taking the time for adding us.
15:30:53 <jatanmalde> +1 chandankumar
15:31:21 <chandankumar> s/project-config/config
15:31:31 <rbowen> So, we're still on topic 1 and it's half past.
15:31:41 <adarazs> chandankumar: oh okay, this makes more sense. but what do you mean?
15:31:59 <number80> apevec: ballot is closed!
15:32:11 * number80 hides
15:32:29 <number80> yep, next topic
15:32:31 <adarazs> chandankumar: what do you mean by session about the config? should I explain stuff about it or what? :)
15:33:10 <number80> adarazs: having a visio call to explain the CI setup and all relevant info
15:33:17 <number80> but let's discuss that later
15:33:30 <chandankumar> adarazs: yup the same
15:33:42 <adarazs> okay. it's fairly simple, but we can do that.
15:34:03 <adarazs> at least what's concerning the config repo.
15:34:14 <trown> adarazs: I think the knowledge transfer was meant in the other direction :P
15:34:15 <number80> amoralej: I think next topic is yours
15:34:24 <number80> (and we have plenty today)
15:34:26 <adarazs> trown: haha, okay :D
15:34:27 <amoralej> yeah
15:34:32 <amoralej> let's move on
15:34:43 <amoralej> #topic Mock 1.4 and network access in DLRN workers
15:34:45 <amoralej> jpena?
15:34:50 <jpena> yes
15:35:06 <jpena> so quick info: earlier this week we updated mock in the DLRN instances, and that brought a change in the default config
15:35:42 <jpena> before, when building packages with DLRN, we always had networking enabled, but now mock has changed to use nspawn and the default is no external networking
15:36:15 <jpena> This broke glare (https://review.rdoproject.org/r/9929)
15:36:16 <number80> Well, it mirrors Koji setup which is a good thing
15:36:55 <jpena> for now, I have re-enabled networking as a quickfix, but I wondered if we want to keep it disabled to avoid issues when building in Koji later
15:37:00 <number80> Glare is special case, the test case require networking is fairly recent (otherwise, it would have failed in CBS)
15:37:12 <amoralej> number80,  it failed
15:37:22 <amoralej> i disabled unit tests because of that for CBS
15:37:23 <number80> amoralej: I mean for the previous build, sorry
15:37:44 <amoralej> this was first cbs build ever for glare, :)
15:37:49 <apevec> that's bad unittest
15:37:51 <apevec> by definition
15:37:57 <number80> jpena: I'm +1 to use no networking setup, that's the role for DLRN to detect those issues
15:37:59 <apevec> needs to be fixed upstream
15:38:18 * number80 notices that the person who wrote that test is a RDOer
15:38:18 <amoralej> number80, i agree
15:38:20 <apevec> is there LP ?
15:38:24 <jpena> we have some other similar cases, like docs using intersphinx
15:38:34 <amoralej> not, i left a message to mfedosin in the review
15:38:45 <amoralej> but didn't receive feedback
15:38:49 <amoralej> i'll create a LP
15:38:56 <mfedosin> hey
15:39:01 <amoralej> :)
15:39:12 <rdogerrit> Merged openstack/oslo-vmware-distgit rpm-master: Add python-eventlet as BuildRequires  https://review.rdoproject.org/r/8631
15:39:16 <mfedosin> second please :)
15:39:44 <amoralej> mfedosin, we are disabling networking access whild building packages, so glare unit test fail because it get a file from outside
15:40:08 <mfedosin> ohh,
15:40:11 <number80> downstream review is  https://review.rdoproject.org/r/#/c/9929/
15:40:12 <mfedosin> yes, we do
15:40:15 <amoralej> apart from glare, some packages need access to internet to build docs, but i think we patched all or most of them
15:40:20 <amoralej> as part of the warning is error
15:40:30 <amoralej> so that should be ok also
15:41:00 <amoralej> so, anyone against disabling networking access in DLRN?
15:41:01 <mfedosin> okay, I'll fix it - I wanted to do it long time ago
15:41:15 <amoralej> thanks mfedosin
15:41:31 <number80> *nods*
15:42:13 <amoralej> jpena, for glare we'll have to disable tests until fix is pushed
15:42:18 <jpena> cool
15:42:19 <amoralej> if we want to disable networking
15:42:25 <jpena> I'm +1 for disabling networking
15:42:36 <jpena> it'll create some ftbfs, but that's good
15:42:48 <amoralej> yeah
15:42:49 <number80> +1
15:42:56 <chandankumar> +1
15:42:58 <jschlueter> +1 for disabling networking
15:43:17 <amoralej> #action jpena to disable networking in DLRN runs for all workers
15:43:22 <amoralej> next topic?
15:43:24 <jpena> yes
15:43:34 <amoralej> #topic OpenStack SIG in Fedora
15:43:51 <amoralej> #info https://www.redhat.com/archives/rdo-list/2017-September/msg00072.html
15:44:06 <amoralej> #info Initial slate: amoralej, apevec, chandankumar, dmsimard, jpena, snecklifter, tonyb, tristanC and hguemar
15:44:12 <amoralej> number80, ^
15:44:41 <number80> Well, since we're short on time, and most people signed up by their own will (or mine :P), I suggest that we vote directly :)
15:45:07 <rbowen> Is this just clients, or services also?
15:45:12 <rbowen> Or is that to be determined?
15:45:16 <number80> rbowen: only clients for now
15:45:20 <apevec> clients + oslo
15:45:25 <rbowen> ok, good.
15:45:26 <rbowen> Thanks.
15:45:42 <apevec> services are in rdo trunk Fedora (WIP)
15:45:51 <amoralej> i'm +1 about the plan in your mail number80
15:45:51 <number80> Make OpenStack clients great again is the motto
15:46:02 <rdogerrit> Aditya Ramteke proposed openstack/gnocchiclient-distgit rpm-master: Move package description to global variable.  https://review.rdoproject.org/r/9903
15:46:05 <chandankumar> number80: are we including dependencies also apart from clients + oslo in this group?
15:46:22 <number80> chandankumar: any dependencies that we can transfer to the SIG
15:46:37 <apevec> chandankumar, if general python-* it shouldn't be in that SIG, rather in python SIG
15:46:50 <number80> Well, both SIG can co-maintain it
15:46:51 <chandankumar> got it. :-)
15:46:56 <apevec> ok, that works
15:47:02 <chandankumar> cross sig calloboration
15:47:26 <number80> so anyone opposes it?
15:47:36 <rbowen> DOO EET
15:47:46 <number80> #action number80 start paperwork to create the Fedora OpenStack SIG
15:47:51 <number80> well, alea jacta est
15:47:54 <amoralej> nice
15:48:11 <snecklifter> well said, number80
15:48:31 <amoralej> #topic RDO booth volunteers needed for OpenStack Summit - https://etherpad.openstack.org/p/rdo-sydney-summit-booth
15:48:36 <amoralej> rbowen, ^
15:48:38 <rbowen> #info RDO booth volunteers needed for OpenStack Summit - https://etherpad.openstack.org/p/rdo-sydney-summit-booth
15:48:41 <rbowen> No more to say. :-)
15:48:45 <amoralej> :)
15:49:01 <amoralej> #topic Tentative test day schedule - https://www.rdoproject.org/testday/ - please point out any date conflicts
15:49:07 <rbowen> #info Tentative test day schedule - https://www.rdoproject.org/testday/ - please point out any date conflicts
15:49:11 <rbowen> Really not much more to say there, either.
15:49:21 <number80> rbowen: I suggest that call to be shared on the internal Red Hat openstack dev list as we have few people going there
15:49:26 <rbowen> Although a couple of those dates conflict with events that some folks may be at.
15:49:33 <rbowen> number80: I also copied it to that list, this morning.
15:50:05 <number80> rbowen: sorry, I must have wrong filters
15:50:19 <amoralej> number80, dates look ok to me
15:50:29 <amoralej> rbowen, ^
15:50:34 <rdogerrit> Aditya Ramteke proposed openstack/gnocchiclient-distgit rpm-master: Move package description to global variable.  https://review.rdoproject.org/r/9903
15:50:40 <amoralej> i just hope to be able to start getting promotions soon
15:50:42 <amoralej> in master
15:50:43 <rbowen> IN particular, the February one is during FOSDEM which I know a number of you attend.
15:50:44 <jpena> same here, no evident issues
15:50:49 <amoralej> we haven't promoted in about 3 weeks
15:51:01 * number80 is ok but travelling for both M1 and M2 test days (which is not a blocker)
15:51:18 <rbowen> Anyways, nothing more to say on this topic.
15:51:50 <amoralej> #topic DLRN Release format
15:52:12 <amoralej> is this from jruzicka?
15:52:59 <number80> should be
15:53:08 <amoralej> so, the point is fi we want to stay with the current format for release in DLRN builds or want to move to something compatible with fedora
15:53:29 <jpena> a compatible format would be 0.1.<date>.<hash> ?
15:53:56 <amoralej> i think there were some discussions some time ago
15:54:02 <number80> yes, and possible the 0.1 is bumpable
15:54:16 <amoralej> 0.1.<date>.<hash> or 0.<date>.<hash>.1 ?
15:54:33 <amoralej> i'm not sure what was the best option
15:54:33 <jpena> so that format only has one issue: upgrades between the packages with the old format and the new format won't be possible
15:54:44 <amoralej> ah, yeah
15:54:51 <jpena> 0.1.<date>.<hash> I mean
15:55:02 <number80> amoralej: 0.1.<date>.<hash> is the correct form (for upgrade path) but we can append .1 .2 for rebuilds
15:55:04 <amoralej> we discussed if doing it configurable and implement it only in master first
15:55:08 <chandankumar> 0.1.<date>.<hash> +1
15:55:10 <number80> (so third option)
15:55:23 <jpena> oh, sure
15:55:32 <amoralej> but in that case, when dlrn bumps release
15:55:38 <amoralej> what digit would it bump?
15:55:53 <amoralej> not dlrn, rdopkg i mean
15:55:59 <amoralej> i think that was the real issue
15:56:13 <jpena> in any case, we need to accept that change for queens if we want to do it now
15:56:28 <jpena> rdopkg would bump the 1 in 0.1....
15:56:36 <jruzicka> oh, sorry
15:56:37 <number80> Yep
15:56:52 <amoralej> so rdopkg always bump second digit in release?
15:57:01 * jruzicka got lost in gerrit
15:57:14 <jruzicka> rdopkg always bumps last numeric part of release
15:57:41 <jruzicka> it can be changed to any behavior but I need to know what it should do :)
15:57:43 <amoralej> then in 0.1.<date>.<hash> it would bump hash?
15:57:50 <amoralej> ok
15:58:02 <jruzicka> I have draft for current format support I still think it might be worth the change, what's your point o n that?
15:58:04 <amoralej> yeah, it doesn't make sense to bump date or hash
15:58:05 <apevec> rdopkg does hexa?
15:58:06 <jruzicka> espescially jpena
15:58:33 <jruzicka> apevec, no and it's a problem when it will bump hexadigit string when it only contains digits
15:58:59 <jpena> jruzicka: I think it's a good idea to make the release more compatible with fedora, just want to make sure nobody yells at us when upgrades don't work between to hashes :)
15:59:21 <jruzicka> jpena, allright, cool.
15:59:44 <jruzicka> 0.1.<date>.<hash> sounds OK
15:59:44 <apevec> let's break it now
15:59:53 <jruzicka> Fedora always bumps the second part?
16:00:06 <rdogerrit> Aditya Ramteke proposed openstack/oslo-versionedobjects-distgit rpm-master: Moved package description to global variable.  https://review.rdoproject.org/r/9883
16:00:20 <amoralej> jruzicka, in pre-release i think so
16:00:21 <jruzicka> apevec, and that answers my question whether I shoud support current format or wait for the new one I guess ;)
16:00:41 <apevec> jruzicka, you need to support both, we'll break master only
16:01:18 <jruzicka> apevec, OK, cool, at least the code I wrote will have some use ;)
16:01:46 <jruzicka> can someone articulate the change with and #info or #action?
16:02:07 <jpena> #action jpena to propose DLRN patch to change release to 0.1.<date>.<hash> as a configurable option
16:02:11 <amoralej> in what case will we be bumping the release
16:02:52 <rdogerrit> Gabriele Cerami created rdo-infra/ci-config master: cloud images promotion: disable removal of previously promoted images  https://review.rdoproject.org/r/9937
16:02:53 <jruzicka> jpena, please add me as reviewer ;)
16:02:57 <amoralej> i mean if someone bumps it to 0.2.x.y that will always be higher that more recent 0.1.x.y until a new version is release
16:03:08 <amoralej> jschlueter, ^ is that ok?
16:03:13 <jpena> jruzicka: ack
16:03:26 <amoralej> well, that can be discussed in the review
16:03:35 * chandankumar reminds meeting time cross > 3 mins
16:03:38 <amoralej> ok, we are out of time
16:03:43 <jschlueter> amoralej: should be ok with me
16:03:43 <jruzicka> #action jruzicka to support both current and new DLRN release format in rdopkg
16:04:06 <amoralej> ok, are we done with this topic jruzicka
16:04:07 <amoralej> ?
16:04:13 <jruzicka> amoralej, indeed
16:04:16 <amoralej> #topic open floor
16:04:32 <jschlueter> I think as long as next dlrn build is greater than that... or I will have to do extra work to detect this condition
16:04:38 <amoralej> any topic you want to bring?
16:04:57 <amoralej> jschlueter, that's my point, i think dlrn will not
16:05:05 <amoralej> but we can discuss it after the meeting
16:05:25 <amoralej> any volunteer for next week meeting?
16:05:36 <jpena> I can do it
16:06:06 <amoralej> #action jpena will chair next meeting
16:06:12 <amoralej> ok, i think we are done
16:06:19 <amoralej> thank you all for joining
16:06:31 <amoralej> #endmeeting