15:01:06 #startmeeting modularity_wg 15:01:06 Meeting started Tue Nov 28 15:01:06 2017 UTC. The chair is nils. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:06 The meeting name has been set to 'modularity_wg' 15:01:07 #meetingtopic Meeting of the Modularity Working Group (once every two weeks) 15:01:07 #chair dgilmore langdon mikedep333 15:01:07 Current chairs: dgilmore langdon mikedep333 nils 15:01:14 .hello2 15:01:18 #topic Roll Call 15:01:24 .hello nphilipp 15:01:25 .hello sct 15:01:27 langdon: langdon 'Langdon White' 15:01:30 nils: nphilipp 'Nils Philippsen' 15:01:30 #chair sct 15:01:30 Current chairs: dgilmore langdon mikedep333 nils sct 15:01:33 sct: sct 'Stephen Tweedie' 15:02:08 .hello2 15:02:09 asamalik: asamalik 'Adam Samalik' 15:02:36 .hello2 15:02:37 #topic Agenda 15:02:37 #info [langdon]: Stream naming convention updates? 15:02:37 #info [langdon]: Thoughts on modular server release 15:02:38 sgallagh: sgallagh 'Stephen Gallagher' 15:03:09 these two are (still) open issues on Pagure, anything else? 15:03:33 ok 15:03:42 #topic Stream naming convention updates? 15:03:55 nils: i would re order those, no? 15:04:02 +1 langdon 15:04:04 like i think thte second is higher priority 15:04:04 sure :( 15:04:07 :) even 15:04:09 #undo 15:04:09 Removing item from minutes: 15:04:11 ha 15:04:13 #undo 15:04:13 Removing item from minutes: INFO by nils at 15:02:37 : [langdon]: Thoughts on modular server release 15:04:17 #undo 15:04:17 Removing item from minutes: INFO by nils at 15:02:37 : [langdon]: Stream naming convention updates? 15:04:24 #info [langdon]: Thoughts on modular server release 15:04:30 #info [langdon]: Stream naming convention updates? 15:04:36 #topic Stream naming convention updates? 15:04:52 so, that's better 15:04:57 so.. discussion is happening here: https://pagure.io/Fedora-Council/tickets/issue/149 15:05:55 basically, concerns have been raised that the incompleteness of content and a low level re-architecture should delay/supercede/remove the f27 server release 15:06:06 and instead do a child-of-boltron release 15:06:35 and maybe ship regular f27 server from the builds we did on the traditional side 15:07:12 discuss! 15:07:23 yeah... and also a proposal of a new approach to modularize F28: https://asamalik.fedorapeople.org/modularity-hybrid.png 15:07:46 asamalik: or f27 :) 15:08:31 langdon: ha.. right.. :) I should say ...to modularize F28 which leads us to a Q: should we also do the same thing for F27? :) 15:08:40 i am not sure we have many people around :( 15:09:41 yeah.. :( 15:09:55 langdon, people who haven't discussed this in the ticket will have to catch up what was discussed already 15:10:04 ha 15:10:09 lest we want to rehash this here :) 15:11:18 Not sure.. Maybe the ticket is enough.. I just wanted to be sure this group saw the discussion 15:11:30 * tflink is still reading the ticket 15:11:48 probably... also sgallagh wants to talk about this in the Server WG meeting later today 15:11:53 Yes 15:11:55 And I'd like to forestall any forays in the field of "but we can do this already with -compat packages" which seems to happen in the ticket :D 15:11:59 Sorry, was distracted. I am here now 15:12:08 * asamalik welcomes sgallagh 15:12:36 The crux of the issue is that I have reservations about shipping what we have under the name Fedora Server Edition 15:13:09 In large part because I suspect that its lack of access to much of the endpoint software in Fedora is going to be the thing that all press focuses on 15:13:50 Combined with the fact that we're reworking the plan in F28, I think it might be more prudent to acknowledge publicly that we tried something and it didn't pan out 15:14:19 Rather than release something with the implied support(*) of Server Edition. 15:14:30 mhm 15:15:12 My perspective is that instead of shipping Fedora 27 Server Edition GA, we should switch our efforts immediately to Fedora 28 Server Edition and do a series of Alpha releases, converging again on the F28 Beta schedule 15:15:52 sgallagh: that makes sense to me... it of course doesn't mean we don't want to release it at all... maybe under a different name... but admitting it and making sure F28 will work out well is something that sounds right to me 15:15:53 sgallagh, switch all modules which are "f27" today to "f28" now and work from there? 15:16:16 The big tradeoffs on that are 1) can't test updates through bodhi 2) smaller amount of feedback 15:16:18 nils: not *exactly* 15:16:32 langdon: Why can't we test updates through Bodhi? 15:16:36 We can do that *right now*? 15:16:42 err, s/?/!/ 15:17:06 What would we update? 15:17:12 I've verified that modules submitted through Bodhi end up in updates-testing 15:17:19 I proved that out during the beta freeze 15:17:38 langdon: While we are in Freeze, it's the best way to try out new changes before stuffing them into the compose 15:17:41 Sure.. But that isn't at scale.. Just negative testing 15:18:10 Maybe it is enough.. But it makes me nervous 15:18:32 nils: Switch app-stream modules to depend on platform: f28 at least. 15:18:46 We're going to be changing (significantly) what platform:f28 means 15:18:55 It'll basically become the same as F28 traditional 15:19:04 nils: also, making them smaller, removing all the bundled dependencies, because they will be in the much bigger "base" thing 15:19:04 Which also means: no more bootstrap module 15:19:37 sgallagh, because that'll be gobbled up by "son of platform"? 15:19:39 nils: so no more dependency hell to deal with 15:19:46 Well, the technical implementation is still a bit TBD. 15:19:54 * sgallagh just had a few thoughts that I'll save for post-meeting 15:19:55 asamalik, that sounds sweet 15:21:17 nils: More or less; I just had a few ideas around "son of platform" that we need to work out. 15:21:33 on the other hand, and this is just a crazy idea to save F27.. could we generate a module that would exist on top of existing platform, containing all the dependencies for the leaf modules? 15:21:45 How much would the decision to shift focus to f28 be obviated if we had stream expansion? 15:21:50 It might be that we replace "bootstrap" with "everything" and then "platform" is a limited subset of "everything" that we know we can swap out sometimes. 15:21:54 But that's a rat-hole 15:22:36 asamalik: We *could*, but it's harder to implement than it sounds. 15:22:38 langdon: it wouldn't help at this situation, because platform f27 and f28 would be significantly different 15:22:47 like containing some of the deps vs. all of them... 15:23:17 so building the same thing on top of both wouldn't work... I think 15:23:25 sgallagh: yes, probably 15:23:39 that's why it's just a crazy idea :) 15:24:17 asamalik: Well, part of the stream expansion thing is that we'd get notifications for each platform that actually failed. 15:24:30 But you're right, that number would be very close to 100% at this juncture 15:25:58 yeah.. the way I see it, stream expansion is very useful for building against two versions of the same thing... not two completely different things 15:28:08 so yeah... if we could do an "environment with deps" in f27, then we could build the "app" modules against that and reuse them in F28 as well... 15:28:31 and the "environment with deps" would be basically a huge platform, or a shared-userspace module, or something similar 15:28:50 but it would be an extra work with implementing the same a different way, maybe? I don't know.. 15:28:58 asamalik: In other words... exactly the thing we plan to do in F28... 15:29:07 we would need a few days to play with it I guess... and to think 15:29:23 Which is a significant undertaking, which I think is better spent getting right for F28, rather than trying to shoehorn into F27 so late 15:29:42 sgallagh: right... 15:29:52 yeah :( 15:32:59 So.. Share your thoughts in the ticket and we move on? 15:33:24 unrelated... if we decided to go for F28, could we target releasing it earlier than other editions? would that look better? 15:33:46 langdon: yeah, probably.. we're not deciding here anyway 15:33:55 I'd think that a good release would be good enough, no? would it really need to be early? 15:33:59 asamalik: I'd prefer not to make scheduling decisisions like that 15:34:11 even better point 15:34:34 that was just another crazy idea, agree 15:35:19 ok, so moving to the next topic? 15:35:28 considering we leave our comments in the ticket? 15:35:52 langdon, so #link the ticket and #info that we'll leave comments there? 15:36:44 Nils could you? I'm on mobile for a few 15:36:50 sure 15:37:25 #link https://pagure.io/Fedora-Council/tickets/issue/149 Discussion is happening here 15:37:46 #info We'll continue discussion in the ticket 15:37:46 Thanks 15:37:54 alright 15:38:13 #topic Stream naming convention updates? 15:38:45 https://pagure.io/modularity/issue/75 15:39:11 langdon, I just listed that because the ticket is still open and I'm not sure if we updated the Module Packaging Guidelines yet 15:39:25 No.. Not yet :( 15:39:45 ok , I'll leave it open then 15:39:53 I think i sent them out though? Right? 15:40:09 IIRC you sent something out 15:40:27 yeah it looks pretty good, there are just few comments that need to be sorted out 15:40:33 mostly minor changes 15:40:41 K I'll try to follow up today 15:41:30 langdon, I'll try to remember closing the ticket when you're done, deal? 15:41:48 Ha.. Deal 15:42:00 langdon, let me know if there's anything I can help you with 15:42:09 ok... 15:42:15 #topic Open Floor 15:42:23 anybody got anything else to discuss? 15:44:26 maybe come to the Server WG later today? just a reminder :) 15:44:30 but I don't have anyting else 15:44:53 yeah, seems y'all can have back a quarter of an hour :) 15:44:55 I'll be there 15:44:59 #endmeeting