17:00:02 #startmeeting 17:00:02 Meeting started Tue May 31 17:00:02 2016 UTC. The chair is OdyX. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:09 #topic Check-in round 17:00:20 Sam Hartman 17:00:21 Didier 'OdyX' Raboud 17:00:26 Philip Hands 17:01:18 Tollef Fog Heen 17:01:32 aba, dondelelcaro, keithp: ? 17:01:48 yup, I'm here 17:02:13 Keith Packard 17:02:40 he he. Hello bdale 17:03:01 * bdale apparently hasn't removed the ctte calendar provider from his calendar config yet... 17:03:05 Let's wait until *:05 to proceed. 17:03:25 bdale: you can candidate at the end of the year, don't worry :) 17:03:31 pfft 17:05:17 There. Let's proceed. 17:05:26 #topic Next Meeting? 17:05:33 Option B "Tuesday 17:00 UTC (June 28th)" 17:05:36 Option M "Thursday 18:00 UTC (June 30th)" 17:05:43 Any opinions ? 17:05:44 I thought we were meeting during debconf? 17:05:51 either works, I'll be at debcamp for both 17:05:57 but I'll just have arrived for the first one 17:06:18 I won't be there for debcamp, just debconf 17:06:18 * fil is at debcamp too 17:06:22 but what keithp said, push it out a week? 17:06:27 I won't be at DebCamp. I suspect it might make sense to drop the IRC meeting in favour of one IRC meeting during DebConf. 17:06:45 I will find an end of June meeting before I arrive at debconf I think on the 1st really hard 17:07:09 So what about we push it one week, same time ? 17:07:15 wfm. 17:07:17 sounds awesome 17:07:36 we need to meet and create some content for the ctte bof too, but we can do that throughout the week 17:08:00 Tuesday 5th ? 17:08:11 17 UTC 17:08:15 #save 17:08:20 if that's not in the middle of dinner 17:08:55 Let's agree on the principle, and fine-tune when we have more info. 17:08:58 wfm 17:09:23 wfm 17:09:26 #agreed Push end-of-June meeting to early-July, during DebConf, around Tue 5th, 17UTC. Fine-tune when DebConf program is known. 17:09:35 I'll handle that and communicate through the list. 17:10:10 #action OdyX to handle the meeting coordination. 17:10:18 #topic 766708 Cross toolchain packages in Debian 17:10:29 fil: the stage's yours. 17:10:56 We've duly received your private report, but some transparency to a public meeting makes sense, I think. 17:11:37 well, I've chatted to all the people that seemed likely to have an opinion about it, and they are all between indifference and thinking the bug should probably be closed 17:12:17 yup, here. 17:12:33 for reasons that are mostly about the fact that it's not really aged well 17:12:40 There's still a tension between the protagonists around the cross-toolchain question, right? 17:12:52 and that it's a mix of two bugs that makes the waters muddy 17:13:09 OdyX: yes 17:14:00 #info #766708 & 771070 are two mixed issues, which aged since their creation. 17:14:07 I beleive so -- or at least there's something that needs resolving -- not sure about the tension being between the protagonists, or more between the proposed solutions 17:14:49 Although I don't like this type of "timeout" outcome, closing this seems to be the least worse of all other possibilities, right ? 17:14:50 the underlying issues would seem to be behind #815172, for instance 17:15:24 do they want us involved or do they just want to make an attempt to work it out between the various solutions? 17:15:37 That'd be asking fellow developers to produce a "state of the issue" for us, again. 17:15:38 I'd think so -- that bug seems to be acting more as a blocker to progress than aything esle 17:16:07 We could close with willingness to get involved if anyone has specific requests of us. 17:16:09 Mithrandir: they'd like us to find some solution that everyone is happy with. 17:16:13 (that was in reference to the timeout comment BTW) 17:16:18 I'm pretty sure this one doesn't exist. 17:18:04 hartmans: I think that sounds fine. 17:18:13 hartmans: sure. 17:18:26 So… Although that's not a fantastic outcome; closing this one with a excerpt of our understanding of the status & a statement of our willingness is a fine course of action. 17:18:55 I just dislike the "timeout" part, that might (again), be due to our lack of bandwidth at critical times. 17:18:55 odyx: yeah. /me is sad it's come to this. 17:20:10 It's a bad outcome in absolute, but I feel it's the best amongst our possibilities, right ? 17:21:39 agreed 17:21:40 it seems to me that this needed a very quick decission, and that as soon as the deadlines had passed there's not much motivation to apply effort to it -- if the only result is that we learn to make a decission of some sort before such deadlines in future, that would be positive 17:22:34 It's not glorious, but so be it. Let's head for a better future. 17:23:38 Let's "#agreed Close #766708 with an excerpt of our understanding of the status & a statement of our willingness to be involved again; as well as a promise to be quicker" ? 17:23:54 second 17:24:17 that seems like a responsible option at this point 17:24:24 #agreed Close #766708 with an excerpt of our understanding of the status & a statement of our willingness to be involved again; as well as a promise to be quicker 17:24:51 fil: I suspect you're our best informed person there. 17:25:37 #action fil to Close #766708 as #agreed, eventually asking privately for feedback before. 17:25:49 (again, please say if I'm too pushy). 17:25:59 #topic Additional business 17:26:08 Hmm, I knew you'd say that -- I'm still pretty light on the background TBH. I just spent some time nudging poeple on IRC -- I can knock something up on the list, but would definitely want others to check it over 17:26:43 :) 17:26:59 That's arguably part of the problem too: we're all way too light on the background… 17:27:58 no additional business from me 17:28:15 * fil also gets the feeling that one half of the argument has yet to be coherently expressed 17:28:17 There was ansgar's "Consider "/usr w/o initramfs or programs in /bin depending on libraries in /usr/lib" 17:29:08 In the past, the TC has not taken subjects upfront, but rather waited for them to be brought to it. 17:29:25 I think it's in our interests to understand the evolving situation though 17:29:43 (and I don't have good remembrances of the cases in which TC members brought general design topics to the TC) 17:29:43 I know I've been watching the discussions with interest, expecting them to appear here at some point... 17:29:48 I think we could volunteer to come up to speed and ask the proponents if it would be helpful for us to learn the issue and become involved in the discussion before it gets to us. 17:29:53 Would we like to do that? 17:30:15 DebConf looks like the good moment to do that. 17:30:20 agreed 17:30:58 it might be good to assign a TC member to provide a report on the issue for us 17:31:10 * fil hides 17:31:11 provide a bit more context and data for the debconf meeting 17:31:36 That'd amount to not closing the bug, no ? 17:31:42 * hartmans hides I hope to be back to being productive by mid July, but doing this in June is something I cannot do 17:32:21 OdyX: I think keithp is talking about the bits raised by ansgar, not the cross-toolchain bits. 17:32:29 ah, good :) 17:33:08 sorry, yes 17:33:34 only piece of additional business from me is that I'll be switching employers as of next week, to FINN.no. 17:33:53 (they use debian and will be paying my airfare to .za. Yay) 17:33:59 nice! 17:34:23 yeah, I hope it'll be good 17:34:30 have high hopes. :-) 17:34:30 For me there's a underlying "procedural" question: do we wait until the situation becomes heated and someone brings the question to us, or do we pick the issue proactively, under §6.1.2, ideally §6.1.5. 17:35:05 my preference is get involved proactively informally as a body of debian developers who can get involved in a discussion. 17:35:12 hartmans: agreed 17:35:34 I'm somewhat wary of using 6.1.5 and would prefer to at least start with just what hartmans suggests. 17:35:43 That is, we're a group of eight developers (well seven). We can go talk about debian issues if we want. We ask some of the proponents informally if it would help for us to do that sort of informal ground work 17:36:46 hartmans: absolutely. There's just §6.3.5 to be kept in mind. 17:36:56 hartmans: I think this is slightly more than informal; it's a 'fact finding missing' for us to become aware of the nuances of the issues so that we can help guide things 17:37:03 OdyX: that's just as the committee. 17:37:24 individual members are free to do as much detailed design work when wearing non-ctte hats. 17:37:34 (as much as they want) 17:37:43 Mithrandir: sure. As long as we don't restrict the discussion to ctte forums. 17:38:09 indeed, I'd think it should be held on -devel (or -project, when appropriate) 17:38:17 keithp: is this something you'd be interested to bootstrap and coordinate ? 17:39:58 OdyX: I think I can 17:40:04 Great, thanks! 17:40:26 I think my irc may have dropped something though; was there a link to a discussion posted at the top of this item? 17:40:34 no 17:40:59 #action keithp To start the enlightenment of the TC members on the "consider "/usr w/o initramfs or programs in /bin depending on libraries in /usr/lib" question. 17:41:34 wilco! 17:41:46 Having a BoF about this would @DebConf would help everyone visualize what the questions at stake are. 17:42:02 meh. s/would @DebConf/at DebConf would/ 17:42:13 Still wrong. 17:42:15 Anyway :-P 17:42:17 #save 17:42:25 Thanks for the transparency Mithrandir. 17:42:34 #topic Check-out round 17:43:13 IRC is frustrating as we're getting more and more used to "John Doe is typing" live-notifications; but it went well enough I suspect. 17:43:34 See you (all?) at DebConf! 17:43:53 looking forward to it! 17:43:58 see you all around indeed. 17:44:03 it'll be good 17:44:04 likewise 17:44:26 see you 17:44:35 yes, looking forward. 17:44:40 45 minutes in. Good timing! 17:44:58 #endmeeting