17:00:16 #startmeeting Council (2015-03-16) 17:00:16 Meeting started Mon Mar 16 17:00:16 2015 UTC. The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:19 #chair mattdm jreznik jwb cwickert rdieter langdon sgallagh decause 17:00:19 Current chairs: cwickert decause jreznik jwb langdon mattdm rdieter sgallagh 17:00:21 #topic introductions, welcome 17:00:24 hello everyone! 17:00:24 YESSSSSSSSSSSSSSSs 17:00:28 who do we have today? 17:00:39 a very excited josh! 17:00:39 Hello 17:00:47 * cwickert thought we only had meetings every other week? 17:00:51 i am excited that we have a follow up meeting, on time, with an agenda. SUCCESS 17:00:52 hola 17:01:15 jwb: heh. 17:01:21 jwb: +1! 17:01:31 * jreznik is here too, trying to multitask a bit but here 17:01:31 * decause waves 17:01:40 cwickert: usually, but last week everyone was excited to do another 17:01:41 cwickert: usually, had a bunch of stuff we weren't able to cover 100% last week, so here we are 17:01:54 hello decause! 17:02:04 :) 17:02:12 glad to finally be here 17:02:16 okay so, let's get right to it! 17:02:20 #topic agenda 17:02:27 #topic agenda 17:02:29 - 5 minutes: intros and welcomes and agenda and stuff 17:02:31 - 10 minutes: outreach steering committee 17:02:33 - 10 minutes: third-party repos 17:02:35 - 10 minutes: university involvement objective 17:02:37 - 10 minutes: contributor survey 17:02:39 - 10 minutes: open floor, time permitting 17:02:41 - 5 minutes: next meeting, action plans 17:02:43 ^ above is from the mail I sent this morning.... 17:02:52 anyone have anything to add (or remove)? 17:03:05 i'd remove contributor survey 17:03:11 I have not seen this email... 17:03:14 because we're going to run long on at least 2 of those topics 17:03:26 * decause has not seen this email either :/ 17:03:28 jwb: yeah that's why I put it last 17:03:36 yep, it's probably too much for one meeting 17:03:41 sent email to council-discuss 17:03:46 i got it 17:03:51 and we don't have to sort out everything Board did not do in a few meetings 17:03:54 * jreznik got it too 17:03:56 * decause adds to taskwarrior 17:04:27 so skip that and add 5 minutes to the first two topics? 17:04:33 yes 17:04:39 works for me. 17:04:40 +1 17:04:49 #topic outreach steering committee 17:05:01 * decause has created a trac: http://fedorahosted.org/fosco 17:05:04 cwickert, did you have a chance to move further on this? 17:05:52 it is very much just a shell at the moment, but should help direct tickets and action and collect knowlege 17:06:02 .hello langdon 17:06:05 langdon: langdon 'Langdon White' 17:06:11 mattdm: no, still working on the summary of the previous discussions as I thought I had one more week 17:06:16 hi langdon! current topic is outreach steering committee 17:06:37 mattdm, yeah.. sorry .. lost track of time 17:06:48 cwickert: yup no problem. can decause help in any way? 17:07:14 mattdm: I'll finish the summary later tonight and then ask for ideas. 17:07:25 in such case, we can skip it too today, it doesn't make sense to go over it without having more details 17:07:31 cwickert: awesome thanks 17:07:46 #action cwickert to finish outreach summary later today, ask for input 17:07:58 jreznik: yeah, I agree. 17:08:07 cwickert: anything else you can use from anyone to help? 17:08:30 * decause also created #fedora-outreach on Freenode 17:09:04 mattdm: not at the moment. I think we need to agree on some very basic questions first, e.g. whether or not FOSCo is going to replace FAmSCo or not and so on 17:09:26 * mattdm nods 17:09:44 okay... let's move on and come back to this next week, with that hopefully posted + some input on it as well 17:09:55 #topic third-party repos 17:10:17 jwb, do you want to introduce your thoughts here? 17:10:28 sort of 17:10:39 i'll start with a recap from FESCo last week 17:10:45 k 17:11:10 the Software installer in Workstation gained support for disabled repository metadata searching (i'm paraphrasing) 17:11:23 #link https://fedoraproject.org/wiki/Changes/DisabledRepoSupport 17:11:48 the Workstation WG wanted to know if it was feasible to install COPR repository files that were disabled by default. they took that request to FESCo, and FESCo agreed 17:11:51 thanks jreznik 17:12:32 now, that gets Fedora into a place were people can search for things that are permissible in COPRs but no in the main Fedora repositories for whatever reason 17:12:32 btw. we wanted something similar with Playground repo, that would somehow allowed similar thing 17:12:52 FESCo rejected it that time but now as we have implementation ready... 17:12:53 jreznik, right, i was also going to mention that 17:12:55 jreznik: Yes, I think we need to have the Env/Stacks group collaborate on the curation process 17:12:59 outcome is update to this policy: 17:13:01 #link https://fedoraproject.org/wiki/Third_Party_Repository_Policy 17:13:09 mattdm, correct, thanks 17:13:43 now. beyond that specific request, the Board weighed in on that policy when it was originally created and didn't offer very specific guidelines on Policy 17:14:48 we have had requests in the past for various third party repositories outside of COPRs to be searchable 17:15:04 specific, approved, and currated repositories. not something like rpmfusion 17:15:54 i am going to go out on a limb and suggest that with the new mechanism in place, it might not be a bad idea to sit down and figure out exactly what we want to allow and disallow outside of COPRs 17:15:57 and not to dance around it: the change page specifically mentions "non-libre but licit" software Steam and Chrome 17:16:45 mattdm, yes, correct. i had forgotten those were used as examples 17:17:13 the question is, what "(or possibly sanctioned)" means in the change page - is it rpm fusion too? as it's currently sanctioned 17:17:20 So a valid question to ask here is whether the Council thinks that the benefits to Fedora outweigh the possible negative implication of supporting the installation of non-libre software. 17:17:25 no, i just said not rpmfusion 17:17:34 jreznik: RPMFusion is not sanctioned and never has been 17:17:39 jreznik: I drafted that page, I can answer that 17:17:45 It's "tolerated" by necessity :) 17:17:50 jreznik: "sanctioned" is one of those awesome english words which can also mean its own opposite 17:18:09 yeah, english is terrible 17:18:12 mattdm: ok, I'll take a lesson here :) 17:18:21 Yeah, that word should be considered inflammable... 17:18:27 let's say "approved" and "disapproved" 17:18:29 sgallagh: :-P 17:18:54 in _this_ sense, "sanctioned" means basically "explictly allowed" 17:19:22 one second please 17:19:27 mattdm: I don't think so as it's next to not officially included... 17:19:35 to be clear, the Board weighed in with two specific statements: 17:19:41 "The board believes that shipping repository metadata that points at 17:19:42 non-free software is incompatible with Fedora's foundations" 17:19:43 "needs to be clearly identified as not officially included (or possibly sanctioned) by that distribution" 17:19:47 "The board believes that reducing technical barriers to explicit user 17:19:48 choice to install third-party software (non-free or otherwise) is 17:19:48 compatible with Fedora's foundations." 17:20:22 This topic is likely to get into a debate about the "Freedom" foundation, but I'd like to make sure we accommodate the possibility that advancing Freedom may mean permitting small exceptions in order to expand to wider influence. 17:20:35 jwb thanks for finding those -- was looking for exact statements but couldn't find em 17:20:40 so. the new technical implementation in Software does not ship repository metadata, and it eases explict user choice 17:21:04 maybe the question is one level above - are our project's core values still valid when our top subprojects thinks, it hits theirs mission? 17:21:20 jreznik: Sorry, could you rephrase that? 17:22:47 sgallagh: I'll try - workstation is our major edition, seems like they think it makes harder to reach theirs (and in this case also our) goals because proprietary software is needed for the target audience 17:22:53 The projects core values are just that -- they're fundamental. However, they're _values_, not strict legal code. 17:23:35 sgallagh, so your take is that any such proposals on other third party repos should include statements as to who else will be reached and why that will be good for Fedora? 17:23:36 jreznik: Thank you, that's a much clearer question 17:23:49 jwb: I certainly think so. 17:23:53 jwb: Yes, I think that would go a long way towards justifying the request 17:24:02 And reducing unnecessary religious warfare 17:24:23 ! 17:24:28 go ahead stickster 17:24:58 btw. I still stand behind my opinion during that Board discussion - I'm ok with it but with user's consent on making repository searchable *before* searching for it... I'm not happy about having proprietary stuff but I'm also pragmatic and I understand why we need it 17:25:21 First, jreznik++ for summarizing an important point, although I think s/proprietary software/software not included in Fedora *such as* proprietary software/ ... 17:25:30 (note that we're now 15 minutes on this topic, but as we shortened the last one, we still have time) 17:26:26 mattdm: I would be okay with postponing the University Involvement topic if we get to that point. This is pretty important and more urgent. 17:26:41 Second, I wanted to clarify how a statement should be detailed to help the Council here. For instance, one way to explain the case for something like Chrome would be to show market penetration, and workflows that developers use with that tool. 17:27:25 stickster: Yeah, that's a more verbose way of saying what I was trying to above: that any exemption should come with a carefully-researched justification. 17:27:48 Then one might reasonably say that our goal is to attract developers to discover the many benefits of our free software platform while easing their migration -- they can get access to tools with which they're already comfortable with minimal friction. 17:27:48 I notice that the current change proposal has the installation of the "non-libre but licit software" listed as a benefit in itself. Given our mission to advance free and open source software, I don't think that that's sufficiently explanatory. 17:27:59 stickster: yes, like that. 17:28:19 stickster: Yeah, please include that phrasing in the Change page :) 17:28:25 as, potentially, an aside.. can we work in a way that FOSS alternatives might be presented when choosing non-foss software? 17:28:30 mattdm, the Change uses it as an example of the possible. not what is actually changing 17:28:37 langdon +1 17:28:52 langdon: IIRC, there's some effort underway to display "similar applications" which may help that 17:28:55 jwb: yes, but it's in the "benefits to fedora" section 17:29:02 But I'd have to double-check with Richard 17:29:11 mattdm, then i'd simply say strike that line 17:29:16 jwb: That's correct, because at the time it wasn't clear what if any .repo definitions would be shipped 17:29:23 So the page is largely theoretical 17:29:42 stickster, then until we get to a concrete proposal for a non-COPR repo, i suggest striking that line 17:29:50 agreed 17:30:00 langdon: Yes, the function is already built in so if you enable a disabled repo, we can display specific Fedora-related text to the user (including presumably a link to more info) 17:30:14 langdon: I believe that is on a per-repo basis. 17:30:21 jwb: I can do that. 17:30:35 Where should the reasoning stuff go? 17:30:50 stickster, in a separate request to enable a specific repo? 17:30:58 stickster, meh.. works for "chrome" but not for "rpmfusion" (just two examples off the top of my head) 17:31:13 s/enable/ship a disabled repo file for 17:31:13 to langdon's point: is there a "FOSS alternatives" resource page somewhere we point people at already? 17:31:21 decause, no 17:31:26 langdon: I specifically am not interested in anything that means risk. Forget about rpmfusion, it's not part of this discussion at all 17:31:42 #action decause start sourcing a "FOSS Alternatives" resource page 17:31:46 stickster: I'm happy to see that text, that explains it to users but I'd still prefer having this dialog available even before this software *is* searchable 17:31:54 stickster, hence the "example" remark.. i just mean a "repo that has more than 1 piece of software in it" 17:32:00 proposal: The Council is amenable to allowing a limited set of third-party repositories be searched in Fedora software stores, however each such example should be brought to the Council with a justification of how it would benefit Fedora's mission to include the software contained in that repo. 17:32:05 if it would please the counci, we can simply state officially that rpmfusion repo files cannot be included in any Fedora package or COPR 17:32:13 decause: awesome! something we're looking for in our openalt group! 17:32:13 that way we stop talking about it. 17:32:16 (just to see if we have an agreement on that point at least) 17:32:50 sgallagh, i think that might be slightly overstating it 17:33:04 jwb: In what way? 17:33:09 sgallagh: You need an editor. ;-) 17:33:17 stickster: I've got vi! 17:33:20 i don't think we've said we're amenable to allowing. i think we've all said we're amenable to discussion of specific repos 17:33:22 sgallagh: I'm still not confortable with that searchable by default without opt-in or opt-out before searching... that's the only problem I have with the whole thing 17:33:36 decause, there is an outstanding web page the tells you how to shift from non-free->foss (mostly about privacy concerns) produced by someone at gnu? or libre-planet or something.. must dig.. 17:33:40 jwb: Well, that was what I was trying to determine: a vote on whether we are amenable as a whole 17:34:01 sgallagh, yes but amenable to allowing is phrasing that is suggestive towards permission 17:34:12 jreznik: If it's not searchable by default, the discussion is moot because nothing will be discoverable 17:34:12 nobody has said they're leaning that way 17:34:17 jwb: OK 17:34:57 sgallagh: Correct on discoverability. Otherwise the barrier for users hasn't changed and the feature's worthless. 17:35:03 Well, worth less. 17:35:29 so.. just because I am confused.. does "3rd-party repo" == "repo that only provides one piece of software" (and maybe its deps) in this conversation? 17:35:41 langdon, most likely yes 17:35:55 stickster: exactly 17:36:08 however, i'd like us to take one step back 17:36:13 langdon: Yes. At this point I don't think anyone's comfortable with "repo full of software" other than COPRs where there is at least reliably just FOSS 17:36:22 langdon: From the earlier conversation, I think the idea was that we would stick to that, in order to reduce burden on legal agreements 17:36:39 stickster: but fot COPR, I'm definitely +1 17:36:42 because we're talking about "repos" in the traditional RPM sense of things. yet App containers can be just as much third party 17:36:49 so maybe, can we switch it to more phases? 17:37:07 like phase 1 COPR - that's what I understand they are asking for now 17:37:10 jreznik, i'd not be supportive of that 17:37:13 * stickster EOF until someone calls him 17:37:14 and deal with other phases later? 17:37:24 jreznik, COPRs is already approved 17:37:37 * langdon thinks he must have missed the first bullet.. 17:37:57 langdon, you didn't miss the bullet. you missed being on the board where the original proposal was submitted 17:38:04 langdon: COPR was approved by the old Board and recently revised for functionality by FESCo 17:38:07 there's a bit of tribal knowledge here 17:38:09 It's covered. 17:38:12 jwb: and for COPR, I'm definitely +1 but any other repos may need different way how to deal with it 17:38:22 jreznik, which is exactly what we're discussing 17:38:35 * jwb thinks people missed his Container statement 17:38:57 jwb: I saw it, but I was concerned that it would confuse the topic further 17:39:03 * mattdm did not miss the container statement 17:39:08 jwb: it's not that clear as it was repeated several times, that for now, we talk about COPR for now 17:39:17 but I got it now 17:39:45 sgallagh, if we're going to craft a process or policy on how to deal with thrid party things, then it should be general enough to cover third party things, not just RPM repositories 17:39:59 sgallagh, otherwise this topic will come up again in a year and we'll fight all the same battles 17:40:00 I agree that anywhere we are saying 'repo' we should keep 'app delivery by whatever mechnism' in mind. 17:40:08 jwb: I agree 17:40:56 okay, so, what immediate outcomes are we looking for here? 17:41:00 so for today, phase 1 = copr repos with only libre software, yes? 17:41:04 decause, no 17:41:08 that's already approved 17:41:11 kk 17:41:12 thanks 17:41:13 a clarified preemptive statement of some sort? 17:41:26 mattdm, yes. along the lines of what sgallagh was getting at with his proposal 17:41:51 Proposal: The Council does not approve a blanket exemption for searching any third-party repository. Individual repositories can be assessed based on a case-by-case basis with a justification provided on how it will benefit the Fedora Project to include it. 17:42:21 yes, something quite like that 17:42:36 ! 17:42:54 I'm roughly for that, but I would like to s/benefit Fedora Project/advance the Fedora Project's mission/ 17:43:06 inode0: go ahead 17:43:23 Has the council already rejected that shipping 3rd-party metadata is inconsistent with Fedora's foundations or is it a given that it is going to do that? 17:43:34 Seems to be implicit in the discussion? 17:43:36 (Have to jump in as editor.) To state it more succinctly: The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will benefit the Fedora Project. 17:43:44 EOF 17:43:52 inode0, the Board rejected that outright. the Council has not overruled that decision 17:44:10 stickster: I like it this way 17:44:14 How can any of this be done without doing that? 17:44:18 inode0: Implicit in the discussion is that we are potentially open to the idea of including certain repositories if doing so would result in a significant net gain. 17:44:33 net gain to Fedora's overall mission 17:44:42 inode0, because the metadata is not being shipped with the new Software mechanism 17:44:43 what is the "burden" on approval of the repo? council decision? wkstn wg? fesco? something else? 17:45:01 langdon: I'd say the burden has to be on the Council 17:45:19 all nuanced with the newer statement of course: "The board believes that reducing technical barriers to explicit user choice to install third-party software (non-free or otherwise) is compatible with Fedora's foundations." 17:45:22 Either it is conveniently shipped with Fedora or it isn't helping any. 17:45:32 inode0: "third party" doesn't necessarily mean proprietary. that's a separate axis. 17:45:33 sgallagh, don't have a strong opinion (and that seems right to me).. but, I think it should be in the phrasing 17:45:52 stickster, care to edit in langdon's point? 17:45:52 stickster: maybe I'd patch it - not only approve but also "Council reserves right to ask for other technical means of enabling these repositories" aka consent with searchability before it's turned on/off (aka opt-in, opt-out) 17:45:58 or.. we need the "how" somewhere 17:45:59 mattdm: I didn't say proprietary did I? 17:46:00 langdon: I think stickster's phrasing covers it 17:46:18 inode0: okay, but I don't see how "third party" is necessarily incompatible with our foundations 17:46:43 too broad. some third party could be completely aligned in every way. 17:46:50 sgallagh, ok.. re-reading.. hmm.. sure.. not sure what i think was missing 17:46:52 inode0: Right, "third-party" could conceivably be CPAN or Rubygems.org (in theory) 17:46:54 yes, 17:47:05 Or "LAMP-in-a-container" 17:47:29 er, LAMP+app (which makes more sense) :-P 17:47:34 mattdm: yep, there are more 3rd parties and each can be decided separately... this way, we will unblock it for clear good 3rd parties 17:47:38 Do we want to vote on stickster's phrasing? 17:47:58 Proposal: "The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will benefit the Fedora Project." 17:47:59 are people opposed to my amendment? 17:48:07 might need to be careful on containers (e.g. docker hub).. (or rubygems.org)... they have lots-o-software ... so neither would pass the 3rd-party rule right as proposed 17:48:07 so non-free is more what I meant, sorry 17:48:10 sgallagh: I'd like to patch it with my appendix (or some other way for opt-in/opt-out for users) 17:48:11 /me missed it 17:48:25 s/benefit Fedora Project/advance the Fedora Project's mission/ 17:48:47 mattdm: +1 to that last edit 17:48:50 mattdm: I'm for your change of phrase. 17:48:56 mattdm, not opposed 17:48:59 Proposal: "The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will advance the Fedora project's mission." 17:49:17 jreznik: The council always reserves all rights to change its mind. I think that addendum is redundant :) 17:49:31 +1 to that 17:49:35 +1 17:49:39 In fact, that's a reasonable level someone could meet, whereas the way I phrased it first was probably an impossible bar :-) 17:49:41 +1 17:49:53 * langdon wonders if he hasn't had enough coffee.. 17:50:00 +1 17:50:06 langdon, because? 17:50:16 +1, even I'd like to have it stated there :) 17:50:19 but, I want to make sure we don't get into another "what does metadata mean"? argument with "search enablement". Is what Software does now "search enablement"? 17:50:35 so .. is the proposal from ~13:48 (est) by sgallagh the one to vote on? or is there an appendix? 17:50:45 langdon, 13:48 17:51:05 mattdm: We could be more exacting, "approve including a disabled repo definition" 17:51:06 langdon: 13:48; if you want the appendix, vote -1 17:51:26 2.. any comments on my concern that rubygems.org and docker hub wouldn't be "allowed" in the current definition of "3rd party"? 17:51:40 stickster, i dislike that. it is too technically specific 17:51:43 stickster: _too_ exacting; I want general but clear 17:51:44 stickster: We were trying to avoid specifying an implementation 17:52:05 langdon: right, that's a really good concern. the current docker client _does_ search a third party repository 17:52:08 langdon: I missed that. 17:52:20 Then I think the original is probably specific enough 17:52:24 langdon, they already aren't "allowed" 17:52:36 langdon: In my head, that's covered, but if the language is implying otherwise, maybe it needs to be tweaked 17:52:52 jwb, i am just clarifying that they are "lots-o-software" repos vs "single-app" repos 17:53:10 * mattdm notes clock since kushal isn't here today to do so :) 17:53:33 langdon, oh i see 17:53:46 mattdm, i propose we just continue 17:53:48 we are back to that some software already does it - aka firefox... 17:54:07 jreznik: Or curl. 17:54:22 Or $LONG_LIST_OF_SOFTWARE_WITH_WHICH_YOU_CAN_DOWNLOAD_THINGS 17:54:24 * mattdm is okay with continuing 17:54:37 however, I am +1 one on this language ""The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will advance the Fedora project's mission." but am still confused about where the appendix remark came fron.. and I think we need to address "lots o software" repos another time.. 17:54:50 langdon, i think this propoal is mostly along the lines of the default software installation tools. not ... tool-specific items like rubygems 17:55:09 i don't even know what the appendix is supposed to be 17:55:11 langdon: The appendix was jreznik asking for the council to reserve the right to demand that the tool provide an opt-in or opt-out for this 17:55:12 jwb +1. should we work that in there? 17:55:28 jwb, ha.. i wish it was that simple .. you can (well, technically, "used to be") get vagrant from rg.o :) 17:55:36 maybe we should add it to the proposal it is for the default software installation tools 17:55:41 langdon: I argued that the council always reserves all rights and that this was redundant 17:55:43 mattdm, no 17:56:01 i mean, there is only so much language lawyering we can do if we aren't going to blanket approve or disapprove things 17:56:10 jwb: maybe into the quesiton we are answering, not the answer itself. :) 17:56:12 so there will naturally be some things we need to review 17:56:22 sgallagh, ahh.. got it now.. ok.. im +1 on the proposal by sgallagh.. I think the council will attempt to not be wishy-washy but makes no promises :) 17:56:46 right on wishywashy :) 17:57:09 I'm still unclear why "all cases must be approved individually" is apparently controversial 17:57:22 sgallagh, i don't think it is? 17:57:30 jwb: Then why are we still arguing? 17:57:40 because people are confused as to what exactly we're voting on 17:57:54 jwb, i prefer to think "just me" :) 17:57:57 Shall I re-propose it? 17:58:03 langdon, no, i didn't know what "Appendix" meant either 17:58:06 Proposal: "The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will advance the Fedora project's mission." 17:58:14 +1\ 17:58:23 +1 17:58:27 +1 17:58:27 I'm +1 on the proposal, and perhaps we need a subcommittee and/or separate meetings on these 3rd Party questions/approval for the future? 17:58:33 +1 17:58:40 +1 17:58:44 it is 2 mins til 17:58:46 cwickert still around? 17:59:13 +1 17:59:13 decause: ideally most discussion would happen onlist (and not in the meeting). crazy? 17:59:24 rdieter: yeah :) 18:00:24 * cwickert is busy at work and had no chance to follow the discussion, sorry 18:01:06 cwickert: *nod*. did you see the proposal a few lines up from sgallagh? if you're good with that (and that's all we've really gotten to) we can call it approved 18:01:21 langdon, if it makes you feel better, i think docker hub is a great example to start from. 18:01:58 jwb, certainly more obvious.. but, technically, pypi or rubygems.o has the same problems.. lots of "software" not just libraries 18:02:16 although.. i suppose.. most of pypi and rb.o is foss, right? 18:02:18 mattdm: +1 18:02:24 cwickert: okay cool 18:02:30 langdon, yes. docker hub is frankly worse than rpmfusion in that regard 18:02:58 #agreed "The Council must individually approve search enablement for any third party repository on a case-by-case basis. The justification must include how the content will advance the Fedora project's mission." 18:03:41 Is there a further proposal for now, or should we go back to lists to figure out some of these issues with things like docker? 18:03:53 mattdm, i don't believe there is a further proposal 18:04:26 ok. anything in specific we want to discuss now or on lists? 18:04:44 * jreznik has to leave now, so nothing to discuss here today 18:04:58 mattdm, i might bring up docker hub. i make no promises 18:05:09 jwb fair enough 18:05:29 okay, so... meeting time +5. 18:05:41 #topic wrap-up 18:06:01 Unless there's anything particularly urgent, let's discuss the other things on list and in their respective tickets. 18:06:08 decause: Do you have 30 minutes to spare this afternoon? 18:06:34 I want to pick your brain about the University stuff 18:06:43 sgallagh: perhaps if we can do a conf call (I've got about 15 mins of driving time in the near future) 18:06:56 #action sgallagh and decause to get together about the university objective proposal 18:07:12 decause: It can wait until tomorrow if you're booked. 18:07:26 sgallagh: I can handle it on my drive, or later tonight 18:07:37 sgallagh, and spot, right? 18:07:47 sgallagh: we'll coordinate after 18:07:56 ok 18:08:13 thanks everyone! 18:08:16 #endmeeting