14:02:37 <mvollmer> #startmeeting meeting
14:02:37 <zodbot> Meeting started Mon Feb  6 14:02:37 2017 UTC.  The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:37 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:37 <zodbot> The meeting name has been set to 'meeting'
14:02:46 <mvollmer> .hello mvo
14:02:50 <zodbot> mvollmer: mvo 'Marius Vollmer' <marius.vollmer@gmail.com>
14:02:53 <pitti> .hello pitti
14:02:54 <zodbot> pitti: Sorry, but you don't exist
14:03:03 <mvollmer> I knew it!
14:03:23 <mvollmer> pitti, .hello takes your fedora account id
14:03:23 <pitti> Traceback: UnexpectedResponseError in pitti.py:23489
14:03:46 <mvollmer> i am not sure what it is good for, actually
14:03:59 <garrett> .hello garrett
14:04:00 <zodbot> garrett: garrett 'Garrett LeSage' <garrett@lesage.us>
14:04:02 * garrett tests
14:04:09 <mvollmer> it's mostly to let others know that you are in the meeting, I guess
14:04:10 <garrett> ok, nice
14:04:12 <pitti> .hello martinpitt
14:04:13 <zodbot> pitti: martinpitt 'Martin Pitt' <martin@piware.de>
14:04:32 <pitti> (can never have enough spam! :) )
14:04:41 <mvollmer> yeah
14:05:13 <mvollmer> #topic Agenda
14:06:54 <mvollmer> * Setting MAC addresses
14:07:18 <mvollmer> nothing else?
14:07:26 <larsu> .hello larsu
14:07:27 <zodbot> larsu: larsu 'Lars Karlitski' <lars@karlitski.net>
14:07:43 <stefw> * Licenses of packages
14:07:47 <stefw> .hello stefw
14:07:48 <zodbot> stefw: stefw 'Stef Walter' <stefw@redhat.com>
14:08:56 <mvollmer> okay, let's start
14:09:04 <mvollmer> #topic Setting MAC addresses
14:09:12 <mvollmer> so I started working on that card
14:09:28 <mvollmer> https://trello.com/c/Do2N49tA/451-networking-allow-changing-mac-and-set-for-bonds-etc
14:09:54 <mvollmer> there has been more input, but I don't understand it all, so I am just plowing ahead
14:10:36 <mvollmer> one thing that I forgot until now: we need NetworkManager 1.6 to set MACs on bonds
14:11:20 <github> [cockpit] stefwalter opened pull request #5849: tools: Check validity of po files during 'dist check' (master...validate-po-files) https://git.io/vDWEL
14:11:25 <mvollmer> so we are not the blocker here
14:12:04 <mvollmer> anyway, the feature seems straightforward, and I have it pretty much working here
14:12:18 <mvollmer> I'll write a test and make a PR
14:12:46 <mvollmer> eot
14:14:13 <mvollmer> #topic Licenses of packages
14:14:30 <stefw> so at FOSDEM i attended a talk about licenses
14:14:37 <stefw> which is usually a mistkae
14:14:48 <stefw> but this one was about projects which are multi-license
14:14:56 <stefw> and it turns out that most projects are multi-license
14:15:01 <stefw> our project is LGPL v2+
14:15:24 <stefw> but we include so much code from elsewhere that it effectively makes our project multi-license ... which is to say that multiple licenses need to be considered to properly consider the license of the project.
14:15:36 <mvollmer> (LGPLv2.1+)
14:15:41 <stefw> yup
14:15:57 <stefw> One suggestion from the talk was to include a separate COPYING file in each component ... as well as a README.sources in each component which includes the source and licenses of "embedded" code.
14:16:08 <stefw> this lines up really well with our pkg/ directtory and our use of bower components
14:16:31 <stefw> What do you think about this idea?
14:16:35 * larsu nods
14:16:41 <stefw> pitti, does it help resolve license ambiguities when distributing on Debian?
14:17:21 <pitti> stefw: a bit, but we already have this autogenerated COPYING.bower (or so) file
14:17:28 <pitti> which I'm refering to in debian/copyright
14:17:50 <stefw> yes, that's a good first step ... but doesn't help describe the fact that cockpit is separate applications from a license perspective
14:17:52 <pitti> the more tricky bit there is that these projects often themselves slurp in/bundle/minify sub-dependencies
14:17:59 <stefw> pitti, indeed
14:18:12 <pitti> (and don't care about tracking those at all)
14:18:27 <stefw> i guess a good first step is for us to care :)
14:18:49 <stefw> and describe it properly at our level, and then we can look for others that are getting it wrong
14:19:01 <pitti> but many of our components don't have a copyright at all indeed
14:22:50 <stefw> ok, sounds like we're good with this ... i'll put it on the trello board
14:24:51 <mvollmer> sounds good
14:24:51 <stefw> https://trello.com/c/6ibl1UJu/460-license-files-in-each-package
14:26:00 <mvollmer> so the way I understand things is that the presence or absence of COPYING doesn't mean anything, legally.
14:26:13 <mvollmer> the important bit is the header in each file
14:26:15 <stefw> i'll post the talk when it gets posted
14:26:21 <stefw> it describes this IRL
14:26:22 <stefw> not in theory
14:26:26 <stefw> and in the Xen project
14:26:32 <stefw> a multi-license project with multiple components interacting
14:26:43 <stefw> and how real lawyers approached this ... and the questions they asked
14:27:03 <pitti> mvollmer: well, many files in a source tarball don't/can't have such a header
14:27:15 <pitti> images, autogenerated files, documentation, and such
14:27:42 <stefw> the video will appear in this directory
14:27:45 <stefw> but is not there yet: http://video.fosdem.org/2017/H.1301/
14:27:49 <mvollmer> and we haev README.sources for those, right?
14:28:12 <stefw> https://fosdem.org/2017/schedule/event/mixed_license/
14:28:21 <stefw> and the correct term is "mixed license"
14:28:34 <stefw> so do a sed 's/multi/mixed/' on my above comments
14:29:00 <stefw> anyway the talk was very applicable to our project ...
14:29:05 <stefw> and worth watching once it's posted
14:29:43 <pitti> :x
14:29:50 <pitti> (sorry, EFOCUS)
14:31:04 <mvollmer> eot?
14:31:22 <stefw> yup
14:32:22 <mvollmer> #topic Anything else?
14:37:00 <mvollmer> okay, thanks everyone!
14:37:02 <mvollmer> #endmeeting