15:00:00 <nils> #startmeeting modularity_wg
15:00:00 <zodbot> Meeting started Tue Mar  6 15:00:00 2018 UTC.  The chair is nils. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:00 <zodbot> The meeting name has been set to 'modularity_wg'
15:00:00 <nils> #meetingtopic Meeting of the Modularity Working Group (once every two weeks)
15:00:00 <nils> #chair dgilmore mikedep333 tflink
15:00:00 <zodbot> Current chairs: dgilmore mikedep333 nils tflink
15:00:06 <nils> #topic Roll Call
15:00:11 <nils> .hello nphilipp
15:00:12 <zodbot> nils: nphilipp 'Nils Philippsen' <nphilipp@redhat.com>
15:00:28 <sgallagh> .hello2
15:00:29 <zodbot> sgallagh: sgallagh 'Stephen Gallagher' <sgallagh@redhat.com>
15:00:46 <tflink> .hello2
15:00:47 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com>
15:01:48 <nils> #topic Agenda
15:01:48 <nils> #info [puiterwijk]: Using Bodhi for modular content
15:01:55 <nils> anybody got anything else?
15:01:56 <contyk> o/
15:02:02 <contyk> .hello psabata
15:02:02 <puiterwijk> Hi
15:02:03 <zodbot> contyk: psabata 'Petr Šabata' <psabata@redhat.com>
15:02:05 <puiterwijk> .hello2
15:02:07 <zodbot> puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' <puiterwijk@redhat.com>
15:02:51 <asamalik> .hello2
15:02:54 <zodbot> asamalik: asamalik 'Adam Samalik' <asamalik@redhat.com>
15:02:54 <sgallagh> nils: I can briefly talk about libmodulemd-1.1 coming out soon
15:03:11 <nils> ok
15:03:37 <nils> #info [sgallagh]:  imminent libmodulemd-1.1 release
15:03:52 <nils> good
15:03:59 <nils> #topic Using Bodhi for modular content
15:04:02 <nils> #chair puiterwijk
15:04:02 <zodbot> Current chairs: dgilmore mikedep333 nils puiterwijk tflink
15:04:20 <puiterwijk> So, I wanted to propose using Bodhi for Modular stuff from now on, with the Bodhi enabelement of last night.
15:04:40 <puiterwijk> That will allow us to finetune and test all the processess for pushing updates and updates-testing for modular content
15:04:47 <sgallagh> puiterwijk: Can you please describe what the workflow will look like?
15:05:03 <puiterwijk> sgallagh: basically the same as an RPM build for u-t.
15:05:19 <puiterwijk> Basically, you build a module, you go to Bodhi, and you create a new update for the module build NSVC
15:05:44 <puiterwijk> It will then mash that with the daily composes into the updates-testing repo (and post-GA also for updates)
15:06:16 <puiterwijk> The whole idea is that for a maintainer, modules should handle the same as updates when it comes to Bodhi
15:06:21 <sgallagh> Prior to GA, someone from rel-eng will manually deal with things for variants-fedora.xml?
15:06:35 <puiterwijk> Yes, for now. I am working on a patch to make that not needed, but that'll take a week or so
15:06:57 <sgallagh> (We will probably need to make that explicit; right now variants-fedora.xml just takes "the most recently built module for the specified stream")
15:07:04 <puiterwijk> So for right now, until either GA or that patch (whatever comes first), when things go to stable, the variants.xml needs to be manually updated
15:07:11 <sgallagh> ack
15:07:47 <puiterwijk> But when using Bodhi for stuff before, as said, we can test everything, and that is tied into autosigning now
15:08:02 <puiterwijk> Modules get signed when you submit them to Bodhi, just like any other RPM, as of last night
15:08:43 <puiterwijk> And my question was basically whether the modularity WG is okay with giving this a try to see how it goes.
15:09:19 <contyk> you can be very specific in variants.xml
15:09:30 <contyk> we did that for f27 at one point, too
15:09:32 <puiterwijk> contyk: yeah, you can, and sgallagh meant we should. Right now we aren't
15:09:38 * contyk nods
15:09:51 <sgallagh> Yes, what puiterwijk said
15:10:04 * sgallagh feels like he says that a lot ;-)
15:10:26 * puiterwijk is not sure whether that's a good thing, but will assume yes for now :D
15:11:34 <puiterwijk> And if anyone hits issues with submitting modules to bodhi, just ping me. I know how this stuff works and am willing to be responsible for making things work
15:12:44 <nils> #chair langdon
15:12:44 <zodbot> Current chairs: dgilmore langdon mikedep333 nils puiterwijk tflink
15:13:12 * puiterwijk wonders how he can sweeten the deal any further... :)  If there's anything, just let me know
15:13:14 <nils> Not sure if we have a quorum for formal voting, but I'm also not sure if this is necessary. What are you guys' thoughts?
15:13:50 <sgallagh> nils: I'm heavily in favor, since it will make the process of landing new modules MUCH easier on the packager side
15:14:00 <sct> .hello sct
15:14:00 <zodbot> sct: sct 'Stephen Tweedie' <sct@redhat.com>
15:14:05 <nils> #chair sct
15:14:05 <zodbot> Current chairs: dgilmore langdon mikedep333 nils puiterwijk sct tflink
15:14:55 * nils stares at the voting WG members
15:15:59 <nils> dgilmore, langdon, mikedep333, sct, tflink? ^^^^
15:16:26 <langdon> nils: im really not available today.. still on the road...
15:16:32 <sct> nils: Apologies, I missed the topic (buried in patches).  I can nod sagely but I have no idea what I'm voting for. :)
15:16:33 <nils> aah
15:16:39 <tflink> sorry, stuck in another meeting that's gone over
15:17:08 <puiterwijk> One-line summary: Using Bodhi for modular content from now with bodhi enabelement to start testing and finetuning the process, puiterwijk willing to be responsible for it
15:17:11 <nils> I take that as a blessing -- let's go informal then
15:17:30 <langdon> however, i read the scrollback and i will follow sgallagh's vote
15:17:32 * sgallagh thinks this should really be a rubber-stamp
15:17:36 <nils> mhm
15:17:40 <nils> two in favor so far
15:18:23 <nils> anybody else with an opinion? :)
15:18:37 <sct> Yeah, I can't see a reason not to, we need to be testing it at some point
15:18:40 <sct> +1
15:19:10 <nils> alright, no votes against
15:19:40 <nils> let's count this as rubber-stamped
15:20:23 <nils> sound good? --> #info puiterwijk's suggestion to enable the bodhi workflow for modules was accepted
15:21:19 <sgallagh> ack
15:21:57 <nils> #info puiterwijk's suggestion to enable the bodhi workflow for modules was accepted
15:22:04 <puiterwijk> \o/
15:22:08 <puiterwijk> Thanks!
15:22:19 <nils> #topic imminent libmodulemd-1.1 release
15:22:26 <nils> #chair sgallagh
15:22:26 <zodbot> Current chairs: dgilmore langdon mikedep333 nils puiterwijk sct sgallagh tflink
15:23:14 <sgallagh> I released libmodulemd 1.0 a couple weeks ago and have been making minor bugfixes to it since, but there are a few things I am prepping that make API changes.
15:23:44 <sgallagh> These changes are *forwards-compatible*, so it will not bump soname, but it *will* have a minor impact on people using the Python bindings.
15:24:14 <nils> I don't think there are too many consumers of the GI Python bindings of the lib yet.
15:24:18 <sgallagh> Specifically, the GObject Introspection versioning requires me to bump it to be Modulemd-1.1, which means that the import statement will need to be updated.
15:24:31 <sgallagh> It's pretty trivial; s/1.0/1.1/
15:24:50 <sgallagh> The major changes in this release will be:
15:25:45 <dgilmore> hi
15:25:46 <sgallagh> 1) It will align better to GObject conventions from the GNOME project, which means that get() will be deprecated in favor of peek()  (to indicate its read-only nature) and I have also added a dup() routine which  makes a deep copy
15:26:16 <sgallagh> 2) It will add support for handling and returning arbitrary objects representing non-modulemd subdocuments in the YAML stream.
15:26:32 <sgallagh> This is needed in particular to be able to handle including module default information in the repodata.
15:26:56 <sgallagh> It is being written to be generic, so we can add support for additional document formats in point releases.
15:27:17 <sgallagh> That will be ready and in u-t by the end of the week
15:27:22 <sgallagh> EOF
15:27:46 <nils> anything to #info, other than the release itself?
15:28:19 <sgallagh> #info libmodulemd-1.1 coming sometime this week, may require minor tweaks to python import
15:28:57 <sgallagh> I think that should do it
15:29:06 <nils> good
15:29:11 <nils> #topic Open Floor
15:29:30 <nils> puiterwijk, patricku, do you want to do it yourself?
15:30:00 <nils> well, doesn't matter I guess
15:30:03 <nils> #info autosigning is now working for modules and signs it as soon as a module is submitted to Bodhi
15:30:32 <nils> anything else?
15:32:49 <nils> ok :)
15:32:57 <nils> Thanks for joining everybody!
15:33:01 <nils> #endmeeting