15:02:54 #startmeeting modularity_wg 15:02:54 Meeting started Tue Dec 11 15:02:54 2018 UTC. 15:02:54 This meeting is logged and archived in a public location. 15:02:54 The chair is nils. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:54 The meeting name has been set to 'modularity_wg' 15:02:54 #meetingtopic Weekly Meeting of the Modularity Working Group 15:02:54 #chair dgilmore 15:02:54 Current chairs: dgilmore nils 15:03:05 #topic Roll Call 15:03:07 .hello psabata 15:03:07 .hello2 15:03:10 contyk: psabata 'Petr Ε abata' 15:03:12 .hello nphilipp 15:03:14 asamalik: asamalik 'Adam Samalik' 15:03:17 nils: nphilipp 'Nils Philippsen' 15:04:18 #topic Agenda 15:04:53 #info #112 Discussion: Module lifecycles 15:05:04 #info #115 Discussion: Stream branch ownership for packages & modules 15:05:18 #info 15:05:18 118 Modularity WG Charter Review 15:05:23 #undo 15:05:23 Removing item from minutes: INFO by nils at 15:05:18 : 15:05:30 #info #118 Modularity WG Charter Review 15:05:44 #topic #112 Discussion: Module lifecycles 15:05:54 #link https://pagure.io/modularity/issue/112 15:05:59 #chair asamalik 15:05:59 Current chairs: asamalik dgilmore nils 15:06:05 adam? 15:07:27 so all the info is in the ticket 15:10:26 * contyk is a little distracted but looks now 15:12:02 sorry there was someone super confused ringing the door bell... 15:12:04 * asamalik is back 15:12:50 so what I'd appreciate on this ticket is a feedback on the proposal 15:12:58 so regarding your concerns in the ticket 15:13:02 GA slips too 15:13:09 Some thoughts: 1) When you say "...is getting built in new releases forever" I understand it as "...until further notice", we should make it clear that nobody really commits to "eternal maintenance" 15:13:30 and, as contyk mentioned 2) we can't compute EOL from release because slips 15:13:54 I think it would be best to discuss it with other groups especially 15:13:59 ...releng 15:14:22 yeah 15:14:39 I would say the most reasonable thing is just to rely on platforms 15:14:43 contyk: yes 15:15:21 we could also put it on FESCo's agenda 15:15:42 contyk: I think that could be a good idea 15:15:45 if that sounds reasonable to you, I'd say defer it 15:15:47 Where are EOLs/SLAs kept currently? There's this flag you have to specify when branches are created. 15:15:47 * contyk nods 15:15:57 I'll update the ticket and file it with FESCo 15:16:00 because this spans across many different groups 15:16:01 nils: nowhere 15:16:02 contyk: thanks! 15:16:13 contyk, write only memory, gotcha 15:16:41 #action contyk updates the ticket and files it with FESCo 15:16:51 contyk++ 15:16:53 anything else to #info? 15:16:55 contyk++ 15:16:55 nils: Karma for psabata changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:17:10 Apparently not. 15:17:30 #topic #115 Discussion: Stream branch ownership for packages & modules 15:17:41 #link https://pagure.io/modularity/issue/115 15:19:09 asamalik, that's yours. I think the ticket is clear, so we could vote on it right away. 15:19:23 there's a proposal to ask FPC to weigh in 15:19:32 ah right 15:19:34 I think we... that 15:19:40 though I'd also say it's a FESCo matter rather than FPC 15:20:32 should I also file a ticket for that then? 15:20:48 contyk: I think that would be good 15:20:56 will do 15:21:07 because the change it proposes is quite significant 15:21:31 contyk: thanks! 15:21:42 #action contyk files a ticket with FESCo for review 15:22:29 anything else here? 15:22:43 nils: I'd say let's move to the next topic 15:22:53 aye 15:23:07 #topic #118 Modularity WG Charter Review 15:23:17 #link https://pagure.io/modularity/issue/118 15:23:59 so I already thought we vote in the meeting and that whoever is present can vote 15:24:10 Langdon isn't here but he asked me if we can take it up regardless 15:24:25 +1 to sgallagh's proposal 15:24:32 and I like sgallagh's proposal 15:24:36 +1 15:25:23 I'd say sgallagh's plus the bit of langdon saying "removing the voting member concept" 15:25:34 nils: +1 15:25:47 I didn't make that clear in my proposal, but I meant to supplement that part. 15:25:57 I took it that way :o) 15:26:46 "a simple majority vote of those present" could have been phrased better, I suppose. 15:27:29 * sgallagh goes back to hacking on libmodulemd 15:27:46 sgallagh: +1 15:28:11 I think it's clear enough, but should extend to all steps (i.e. people present == people putting votes in in the ticket or the meeting) 15:28:44 Seems fair to me. 15:34:12 how do you know who's present in the ticket? 15:34:16 asamalik, contyk, so let's use sgallagh's proposal with the above clarifications: no more voting membership, all voting except "If there are any πŸ‘Ž, it is added to the next meeting agenda, where a simple majority vote of those present will decide it.") happens in the ticket. 15:34:23 contyk, those who vote 15:34:48 ah, thought you wanted to replace +1 with "majority" 15:35:05 If you are present (whatever that means) but don't vote (or explicitly abstain), your presence doesn't matter 15:35:37 *replace +3 with majority 15:35:53 I just don't want tickets with mere one +1 passed because 100% people present voted for 15:36:39 but I was reading it too quickly 15:36:44 we're keeping +3 in the tickets, right? 15:36:49 yes 15:36:55 ok, so +1 15:37:00 uhm 15:37:07 "If at the end of one week there are not at least 3 πŸ‘, it is extended one further week and requires only a single πŸ‘ to pass." 15:37:30 yeah, but the first week 15:37:31 nils: yes, that motivates people to care 15:38:23 Right, it helps ensure tickets don't languish 15:38:24 So you can pass a proposal if you're the only one voting on it within two weeks? 15:38:35 nils: Yes. 15:38:50 Kinds conflicts with contyk's "I just don't want tickets with mere one +1 passed because 100% people present voted for" 15:38:53 That's the risk if you are lazy 15:38:55 nils: and if no one else says "no" 15:39:00 of course 15:39:07 That's very much intentional. 15:39:23 * contyk nods 15:39:29 Just trying to ensure we're all on the same page. 15:39:30 It forces those who care to respond in a timely manner or forever hold their peace 15:39:42 right :) 15:39:48 cue the wedding march 15:39:48 (Or start another proposal, I suppose) 15:39:53 watch the queue during holidays, guys! 15:39:58 heh 15:40:35 I wonder if the "week" unit should be changed to whatever period passes between meetings 15:40:43 it's generally a week but not always 15:41:01 contyk: like if we cancel because of holidays? 15:41:06 yes 15:41:08 common holidays 15:41:09 contyk: I'm in favor of assuming that people will generally not abuse the system 15:41:16 And fixing it if they do 15:41:17 but the meetings only matter if some things get voted down 15:41:21 sgallagh: +1 15:41:23 * contyk nods 15:41:30 yeah let's not overcomplicate it right from the start 15:41:42 that punts the proposal to the next meeting 15:41:46 If it was going to be abused, I think FESCo would have already had it happen 15:41:48 nils: yeah, but in FESCo we typically close and announce the decisions after the meeting, not anytime 15:41:58 yeah, let's have the same as FESCo 15:42:15 Well, the *announcement* happens at the meeting, but the decision can be recorded earlier 15:42:21 And implemented as soon as the conditions are met. 15:42:57 Also, FESCo has a fast-track policy where +7 bypasses the week of waiting (for urgent decisions). I don't think we necessarily need the same here though. 15:43:14 we don't even have that many people involved 15:43:18 That kind of only works when you have a fixed number of voting members 15:43:21 also that 15:43:52 so what's next? 15:44:00 have we agreed? 15:44:30 I think so 15:44:36 I think I'm confused how the amendments we talked about would look like in the text :) 15:45:24 s/one week/until the working group meeting after the one week/ <-- suitably rephrased? 15:49:45 nah, let's keep just one week 15:49:51 assuming people will not abuse it 15:50:06 ok, keep thumbs up/down emoji or make it text (votes for/against)? 15:50:48 nils: +1, πŸ‘, "yea" or any other affirmation should be valid. 15:51:08 * contyk needs to enable unicode fonts in his xterm 15:51:16 ok, so let's make it textual and leave it open how people express that 15:51:28 πŸ‘Œ 15:51:45 βœ“ 15:51:57 s/unicode/emoji-enabled/ 15:52:17 anyway, we're fine with the proposal then? 15:52:21 yup 15:52:24 if so, who will update the charter? 15:52:30 +1, πŸ‘, yay! 15:52:37 I'll do 15:52:41 thanks 15:53:21 #action nils updates the charter according to sgallagh's proposal in ticket #118 with the clarifications discussed 15:53:31 Do we have anything for open floor? 15:53:51 just a note that the ursa major discussion is still ongoing 15:54:00 watch the fesco ticket if interested 15:54:01 #topic Open Floor 15:54:12 .fesco 2003 15:54:14 contyk: Issue #2003: Ursa Major (modules in buildroot) enablement - fesco - Pagure.io - https://pagure.io/fesco/issue/2003 15:54:15 #info the ursa major discussion is still ongoing 15:54:30 and that today is my last day to be fully present here this year, taking vacation 15:54:32 we should also get zodbot commands for modularity issues 15:54:35 #link https://pagure.io/fesco/issue/2003 Issue #2003: Ursa Major (modules in buildroot) enablement 15:54:39 yes! 15:54:43 .modularity 15:54:48 that'd be nice 15:55:01 anyone willing to take an action to pursue that? 15:55:02 (except, would it be logged as a link?) 15:55:17 I can! 15:55:20 could be fun 15:55:28 although I could do that in January :) 15:55:29 asamalik++ 15:55:31 cool! 15:55:57 #action asamalik pursues getting a .modularity zodbot command (like .fesco, only greener) 15:56:53 great 15:56:55 anything else? 15:56:58 Speaking about times of absence, should we skip one or two meetings around the holidays (after Christmas, first January week)? 15:57:00 nothing from me 15:57:13 yes 15:57:31 let's skip 25th and 1st 15:57:45 +1 15:57:50 +1 15:58:53 #agreed We'll skip the WG meetings scheduled for 2018-12-25 and 2019-01-01 because many people are absent. 15:59:04 That's it I guess. 15:59:13 Thanks everyone! 15:59:17 thanks! 15:59:19 o/ 15:59:24 #endmeeting