OK my confusion definitely reduced but still some remains and they may only be trivial details: Cloud WG has explicitly mentioned an Atomic WG more than once, most recently yesterday 17:40:46 <trishnag> #topic Open Floor 17:41:07 <sayan> what about making the Atomic WG? [...snip...] 17:42:45 <jberkus> sayan: I assumed that was a given https://meetbot.fedoraproject.org/teams/fedora_cloud_wg/fedora_cloud_wg.2016-09-28-17.00.log.html Also I read in the Fedora magazine meeting that just wrapped up 30 minutes ago, that Atomic is the default for F25 (among Cloud deliverables). To my ears, "default" and "primary" download sound like they'd be release blocking. And the point of that is what bugs would block release, what criteria apply or not, to that deliverable. And in the previous meeting a week ago: 17:14:15 <jberkus> here's a draft from the designer: https://raw.githubusercontent.com/fedoradesign/nextweb-assets/master/Mockups/Brochure%20Site/brochure-mock-atomic_WIP.png 17:14:23 <jberkus> sayan: I can't answer that. someone else has to 17:15:37 <sayan> the mockup looks good to me 17:16:06 <jbrooks> jberkus, looks nice 17:16:12 <jberkus> just so everyone's up to date, the problem is that this redesign orphans the AWS picker for Cloud base images (as opposed to Atomic) 17:16:21 <maxamillion> I like it 17:16:22 <maxamillion> +1 17:16:29 <jberkus> presumably that now needs to live somewhere on Server 17:16:42 <jberkus> but someone more central to Fedora than me needs to take it to them 17:16:48 <jbrooks> So, is cloud base going to server for 25? Or is that 26? 17:17:03 <jberkus> 25 https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-21/fedora_cloud_wg.2016-09-21-17.00.log.html But then in the Server meeting this week, taking on cloud images was discussed in the context of Fedora 26, not Fedora 25. So... if I'm spreading confusion or focusing on details that don't matter that much, most definitely throw tomatoes (preferably heirloom or a nice red field). Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
