15:00:03 #startmeeting modularity_wg 15:00:03 Meeting started Tue Oct 18 15:00:03 2016 UTC. The chair is nils. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:03 The meeting name has been set to 'modularity_wg' 15:00:04 #meetingtopic Weekly Meeting of the Modularity Working Group 15:00:27 #chair dgilmore haraldh langdon sct 15:00:27 Current chairs: dgilmore haraldh langdon nils sct 15:00:36 #topic Roll Call 15:00:41 .hello nphilipp 15:00:42 nils: nphilipp 'Nils Philippsen' 15:00:44 .hello tflink 15:00:45 tflink: tflink 'Tim Flink' 15:00:46 .hello asamalik 15:00:48 asamalik: asamalik 'Adam Samalik' 15:00:57 #chair tflink 15:00:57 Current chairs: dgilmore haraldh langdon nils sct tflink 15:01:09 .hello langdon 15:01:10 langdon: langdon 'Langdon White' 15:01:13 .hello sct 15:01:14 sct: sct 'Stephen Tweedie' 15:01:15 .hello jkurik 15:01:17 jkurik: jkurik 'Jan Kurik' 15:02:00 #topic Agenda 15:02:20 Does anybody have anything for the agenda? Otherwise we'll do open floor right away. 15:02:27 nils, i did have one thing 15:02:30 JUST came up 15:02:34 langdon: :) 15:02:41 i would like to bump this meeting back by 30m.. 15:02:58 you mean this instance, or all meetings? 15:03:01 i might also propose shifting to every 2 wks as we seem to have less to talk about 15:03:04 all 15:03:14 well.. all but this one ;) 15:03:23 okay let's make it official 15:03:49 #info bump meeting back by 30 mins, shift to bi-weekly 15:03:54 #topic bump meeting back by 30 mins, shift to bi-weekly 15:04:12 to ask the stupid question - you mean 30 minutes earlier, right? 15:04:27 tflink: not actually stupid 15:04:39 tflink, ha.. no.. later :) 15:04:49 good thing I asked :) 15:04:58 ahh so I got understood it right 15:05:09 isn't it already too late ? 15:05:09 tflink, no lie 15:05:25 yeah.. im wondering if i am confusing myself with daylight savings 15:05:28 looking at my calendar 15:06:05 in that case I should mention that 6pm CEST/CET is kind of a hard cut off time for me, as I'm commuting by public transit and I have a private appointment every Tuesday evening. 15:06:07 ok.. kill that itdea 15:06:19 agree with nils 15:06:28 my calendar is VERY hard to read :/ 15:06:34 langdon++ 15:06:34 nils: Karma for langdon changed to 10 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:06:42 ha 15:06:43 yes, your calendar is hard to read :o) 15:07:12 Except if the answer you're trying to come up with is "Langdon doesn't have time" ;) 15:07:15 .hello ttorling 15:07:16 moto-timo: ttorling 'None' 15:07:16 ha 15:07:33 langdon: so it was just a DST time shift issue? 15:07:35 ok.. well. so.. here is the related q.. does it follow dst? 15:07:56 langdon: And if so, _whose_ DST? 15:07:58 i think it is not following dst currently as it is set as utc time.. so.. 15:08:01 "The meetings are at 15:00 UTC every 7 days." 15:08:09 it starts to conflict after US switches 15:08:19 So, they would shift with the respective daylight sing time cut-off dates 15:08:26 ok.. so everyone else won't have a conflict? 15:08:40 langdon: Right, we have a grooming conflict as of Nov. 1st 15:08:57 sct shifting all that around anyway.. which is why i am seeing conflicts 15:09:09 But 15:09:23 if it just conflicts with other team meetings, we can easily swap those around 15:09:42 not all the same people 15:10:05 so I'm mildly in favour of following DST, but it's manageable either way 15:10:13 me too 15:10:25 makes it less confusing for my brain :) 15:10:31 Yep 15:10:40 but.. cz and us mismatch for like a week.. so thats complicated :/ 15:10:54 UK and US DST are different, of course, but that's OK --- nearly all my meetings are synchronised to US DST 15:11:18 s/UK and US/US and rest-of-the-world/ 15:11:47 well.. so.. votes? 15:11:55 follow utc? 15:12:08 * tflink doesn't care so long as he knows if/when the time changes 15:12:32 utc++ 15:12:32 jkurik: Karma for chanueting changed to 1 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:12:36 ha 15:12:39 Mild vote for DST, can live with utc 15:12:49 jkurik: haha, someone will be very confused 15:12:55 lol 15:12:56 hmmmm.. 15:13:05 ok.. lets stick utc then.. until things break again :) 15:13:12 shift to every 2wks? 15:13:22 can live with utc, shifting it 30 mins later local time is a harder problem for me 15:13:31 2wks +1 15:13:35 works for me, we can shift back to weekly if it becomes an issue 15:13:37 nils, ohh i killed that idea already :) 15:13:41 langdon: aah 15:13:43 right 15:13:57 * threebean waves "hello" 15:14:02 so +1 on every 2 weeks 15:14:04 in that case, I lean to keeping it dst-aware, just because then it's not a back-to-back mtg with you know what, but that's not a real issue 15:14:21 yeah, +1 FWIW for bi-weekly 15:14:30 +1 for bi-weekly 15:15:13 ok.. #agreed the modularity wg meeting will shift to every 2 weeks starting next time. We will also follow utc ignoring daylight savings. So, next meeting: Nov 1. 15h UTC 15:15:16 ?? 15:15:17 +1 for fortnightly meetings :) 15:15:33 #action jkurik to setup calendar to have the Modularity meeting biweekly 15:15:45 y'all down with that #agreed? 15:15:49 yup 15:15:51 i didn't actually "set" it 15:16:00 ack 15:16:04 #action nils to change the wiki page accordingly 15:16:12 nils, you fine with utc? 15:16:22 langdon: yeah sure :) 15:16:26 ok.. posting 15:16:32 Thanks! 15:16:41 ohh.. can someone quickly check my math though? 15:16:47 im TERRIBLE with calendars.. 15:16:52 as proven earlier ;) 15:17:00 Yes, 1500UTC is right 15:17:26 It's already appearing at 3pm in my calendar in November, and UK will be on UTC by then 15:17:29 and Nov 1 is the next one? 15:17:39 Yep 15:17:51 #agreed the modularity wg meeting will shift to every 2 weeks starting next time. We will also follow utc ignoring daylight savings. So, next meeting: Nov 1. 15h UTC. 15:17:55 sct, thanks 15:19:52 I checked langdon's math and sct's math and both are correct :) 15:19:57 ha 15:20:09 correct math is the best math 15:20:10 ok.. move to open floor? unless anyone had anything else? 15:20:55 yup 15:21:00 #topic Open Floor 15:21:45 so, anything to discuss? 15:22:13 I was attempting to create a docker module, but I'm not sure what scmurl is allowed 15:22:19 I'm guessing only stg? 15:24:29 config.py: SCMURLS = ["git://pkgs.stg.fedoraproject.org/modules/"] 15:24:35 moto-timo: ^^ seems like it 15:24:39 k 15:24:48 I'll play with the COPR interface then 15:25:20 moto-timo: do you mean for pkgs/components, or modules? 15:25:26 modules 15:25:48 I wanted to try out my idea of having multiple docker versions 15:25:51 okay, in that case I understood it right 15:25:56 yes 15:26:19 moto-timo: I guess, talk to threebean if you need a new module? 15:26:28 sure, I can do that 15:26:50 It's not really a "need", but rather curiosity 15:27:00 trying to dogfood this modularity stuff :) 15:27:07 :) 15:27:16 ty 15:28:08 anything else from anybody? 15:28:13 moto-timo: yeah, just give me a name for it and we can create it. 15:28:46 nothing from me 15:29:19 nothing from me 15:29:29 nope 15:29:35 good 15:29:49 Thanks everyone, and see you in two weeks! 15:29:54 #endmeeting