15:00:59 #startmeeting 15:00:59 Meeting started Wed Oct 22 15:00:59 2014 UTC. The chair is jwb. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:59 #meetingname workstation 15:00:59 The meeting name has been set to 'workstation' 15:00:59 #meetingtopic Workstation WG meeting 15:00:59 #topic init 15:00:59 #chair juhp cwickert otaylor mclasen cschalle ryanlerch jwb kalev 15:00:59 Current chairs: cschalle cwickert juhp jwb kalev mclasen otaylor ryanlerch 15:01:05 hi all. who's around? 15:01:25 I'm here 15:01:29 * cwickert is here 15:01:35 hi 15:01:35 . 15:01:51 * sgallagh is around 15:01:52 * kalev appears in a puff of magic. 15:01:59 i like magic 15:02:25 ryanlerch, mclasen_ cschalle ? 15:03:21 mclasen_ had another appointment and won't be around for the meeting 15:03:37 currently here, but running out in 15 15:03:44 * stickster comes in, sorry for lateness 15:04:05 hm 15:04:15 kalev, mind if we start with netinstall then? 15:04:20 sure 15:04:22 ok 15:04:29 #topic Netinstall 15:04:35 kalev, take it away! 15:04:51 so the story here is that release engineering had a plan how to handle netinstall in F21 15:04:56 i am here 15:05:24 * ryanlerch is here too 15:05:31 the plan was to create a separate repo for each of the products, and have each product's netinstalls read comps and packages from that repo 15:05:48 this would have ensured that in each netinstall, only the relevant products things show up in Anaconda 15:05:56 however, this plan backfired 15:06:11 we do have a separate repo for each product and the installer read comps from there 15:06:47 but in addition to that, the installer also uses the updates and updates-testing repos, which have all the other stuff too 15:06:53 kalev, so three seperate boot.iso s? 15:07:01 so we get weird stuff like Mate apps being offered for workstation 15:07:07 ryanlerch: that was the original plan, yes 15:07:30 ryanlerch, technically there already were for alpha 15:07:40 sgallagh opened a ticket with fesco asking what to do now 15:07:43 * kalev finds the link. 15:08:07 kalev, the mate apps offered? like in the software selection screen in anaconda?> 15:08:08 kalev: I don't find extra apps that concerning, tbh 15:08:22 after all, we're also offering all the worlds apps in gnome-software 15:08:29 (or we should be, at least) 15:08:29 You would only see that if you went to the detailed software selection? 15:08:51 give me two minutes, I'll boot up the netinstall and take a screenshot how it currently looks 15:09:02 #link FESCo ticket on netinstall: https://fedorahosted.org/fesco/ticket/1358 15:09:04 and with netinstall, it's somewhat a bit unclear if it's supposed to be more flexible in choices or not 15:09:14 unlike the live image which is the main deliverable 15:09:22 gah, I seem to have deleted the netinstall iso, can't take the screenshot now 15:09:56 I'd certainly suggest that for workstation, we *don't* want netinstall to be more flexible at a UI level - we just want it to be a non-live-image based way to get to the same end result 15:10:08 are the Beta netinstall images actually different? 15:10:32 On the other hand, if you are writing a kickstart file to install fedora workstation, you should have access to any application in Fedora 15:10:36 I think what we should strive for is that an install that ends up calling itself 'workstation' is more or less identical what you get to a non-netinstall, plus possible extra apps 15:11:10 mclasen_, sounds okay yes 15:11:16 the live image doesnt show the software selection option in anaconda, right? 15:11:23 no, they don't 15:12:01 but it's not possible to not show it in the netinstall one? 15:12:33 not currently, at least 15:12:45 ryanlerch: I think what would be good is if the user at least doesn't have to visit that branch in the tree 15:12:50 but if we wanted to have that, I'm sure we could work with anaconda people to achieve that 15:13:31 otaylor, true it could be an advanced option 15:13:37 ok, netinstall downloaded, screenshots coming up in a sec 15:14:03 It sounds like there might be a way to implant a kickstart file on the separate ISOs that makes the appropriate software/sources selections, skipping those steps in Anaconda? 15:14:21 I don't see much point really in shipping the netinstall image if we're going to cripple it 15:14:28 If we could ship a workstation netinstall image that was set up so the default software set was what you get from the live image and the software selection branch was in the "happy" state, it doesn't seem that important what you find under software selection - it's a bit of a deceptive path for the user to think they need to go there - but we want to push the live image anyways 15:14:32 It wouldn't prevent the user from visiting those screens, AIUI, juhp_ 15:14:56 It would pre-select choices so that you'd get something equivalent to Live install 15:15:14 okay 15:15:19 that doesn't sound bad to me, but it sounds like something that won't happen by Beta 15:15:25 juhp, i don't see it as crippling it, its more that the user installs the extra software in (IMHO) a better interface for doing so -- the Software app 15:15:39 And if it doesn't happen by Beta, should we dare change it for Final? 15:16:00 jwb: It would be tough to change for Beta, and thus scary for Final (to answer sgallagh) 15:16:10 Looking at the ticket - option 3. (the current thing) seems poor to me - there is an inconsistent set of software available 15:16:16 ok, so this is how netinstall currently looks like: 15:16:19 https://kalev.fedorapeople.org/netinstall1.png 15:16:20 https://kalev.fedorapeople.org/netinstall2.png 15:16:21 https://kalev.fedorapeople.org/netinstall3.png 15:16:24 this kind of stuff is why i was concerned about saying no working netinstall iso for Alpha was ok 15:16:27 otaylor: Option 3? 15:16:28 jwb: sgallagh: Rel-eng must have some sort of per-product boot.iso creation already, but this implantation would be a separate step 15:16:35 beceause now is not the time to be doing these kinds of changes 15:16:36 all the netinstalls looks the same, no difference between server of workstation, atm 15:16:47 kalev, right also my impression 15:16:49 (but honestly, it's not a terribly sophisticated change, and easy to test without ruining our nightly composes) 15:16:54 sgallagh: the ticket that stickster linked to has 3 numbered options (https://kalev.fedorapeople.org/netinstall2.png) 15:17:09 kalev, it still chooses Server as the default packageset, even on the workstation boot.iso? 15:17:15 tes 15:17:17 yes 15:17:46 honestly I would be perfectly happy with a unified netinstall for the products 15:17:51 we can request to not ship the workstation iso in that case 15:18:06 jwb: I think so too, this is the option that makes most sense right now 15:18:17 Wait, why does the selection screen have Fedora Workstation and GNOME Desktop as separate optionss 15:18:21 I must have missed the link... 15:18:31 i actaully hit this this morning, installing a new laptop from a boot.iso -- server was selected and chosen by default -- i didnt even have to "confirm" the change 15:18:33 I mean, if we were to ship a Workstation netinstall, people expect it to at least default to Workstation 15:18:44 * stickster sees that (3) is basically what he was talking about -- and sgallagh wisely pointed out an ugly cost to that approach 15:18:44 sgallagh: sorry https://fedorahosted.org/fesco/ticket/1358 15:18:47 otaylor, I mentioned that on the mailing list quite a while back :) 15:18:49 otaylor: I guess it is just a dump of whats in comps ? 15:18:49 before i realised, id started the install, and had to go back and start again 15:18:59 but if all the netinstalls are exactly the same and default to server, we shouldn't promote one of them as workstation 15:19:52 #link https://fedorahosted.org/fesco/ticket/1358 15:20:05 yeah, a unified boot.iso wouldnt really be part of any of the three products... 15:20:31 sgallagh: Hm, maybe my suggestion is not quite (3). If one was to provide a kickstart with just %packages selected, it wouldn't preclude use of updates I think. 15:20:47 sgallagh: I'm theorizing on whether this would work, though -- would need anaconda input either way 15:20:53 so in the ticket i suggested option (1) with server as the default because it seemed to be the most likely usecase of a netinstall 15:20:56 ryanlerch++ 15:21:05 and because workstation really wants to promote the live image 15:21:07 * mclasen_ has to bow out, sadly 15:21:14 mclasen_, np. thanks for coming 15:21:14 mclasen_: o/ 15:21:35 stickster: one of the proposals I made was to ask Anaconda to read a file on the image containing the environment group to default to 15:21:53 We could easily swap the products around that way (and make like easier on Spins too) 15:22:05 sgallagh: I don't think an Anaconda change would be great at this point... but a kickstart wouldn't require any change to the code ;-) 15:22:26 sgallagh: fwiw, I think it's also the cleanest approach and much nicer than the current way where we have to ship a full tree for each product on the mirrors 15:22:48 what would the use case be for someone downloading and using the Workstation netinstall over the full live image? 15:23:04 * jwb shrugs 15:23:34 not netinstall per se, but it's cousin, the PXE install can be very useful in corporate environments 15:23:56 * jsmith does lots of PXE installations :-) 15:24:11 * stickster not so much, but I use netinstall so I don't have to pull e.g. whole DVD. 15:24:27 stickster: unless you have a local mirror the effect is the same 15:24:27 Metered internet? 15:24:35 so instead of brainstorming for all possible solutions here, can we focus on 1) what does the WG want out of a workstation netinstall.iso and 2) if we can't get 1 do we ask them to not ship one at all? 15:24:49 stickster: net install == download from the net ... so that doesn't help 15:25:31 stickster, drago01 is pointing out there is no DVD any longer, so the live image size is the same download size as a net install. not 4GB 15:25:35 drago01: Yeah, I'm still thinking of unified DVD> 15:25:42 but all of this is irrelevant at the moment 15:25:56 so, what does the WG want for a workstation netinstall iso? 15:25:58 drago01, you can typically select a smaller package set in netinstall than Live 15:26:09 jwb: I'd say 1) anything labelled as a workstation netinstall.iso needs to install the workstation software by default if the user doesn't take any specific action 15:26:14 1) personally I think as long as we can get it to default to WS that is fine for a first attempt (and then we do a proper fix for F22). 2) Yeah, then there might as well just be a generic netinstall or whatever we want to call it 15:26:35 me was typing, but (1) what cschalle just said 15:27:01 2) if we can't get a workstation iso that is set up by that way by default, then please dont' call it the workstation netinstall.iso 15:27:11 proposal: Workstation is OK with netinstall defaulting to Server, but asks FESCo to only ship a single netinstall and remove the Workstation specific netinstall and install tree from F21. 15:27:11 that all seems to be the general agreement. does anyone disagree? 15:27:28 kalev, +1 15:27:33 jwb: Which is the general agreement? 15:27:40 kalev, +1 15:28:37 otaylor, what you and cschalle said, but i believe kalev's proposal is the only feasible solution in time for beta 15:29:34 jwb, so on the workstation download page on the website, we will still just have links to the live image (both arches) -- no link to the netinstall iso 15:29:51 kalev: +1 (with the caveat that I'd not want that netinstall.iso described in any way on the "Get Fedora Workstation" web pages) 15:30:06 ryanlerch, yes 15:30:18 ok, this setup sounds ok for me 15:30:36 otaylor: yes, my sentiment exactly -- if we ask to have the workstation netinstall removed, we can make sure web pages don't link workstation netinstall 15:30:53 This makes sense to me -- the option will still be there for a consumer to get a netinstall, but we're not going to promote it 15:31:04 cwickert, ? 15:31:18 i.e. they can download existing netinstall e.g. Server, choose the Workstation product from the environment list in Anaconda. 15:31:20 I hope we could have a WS netinstall iso for F22 though 15:31:22 kalev, otaylor -- the plan on the website for workstation was to just have the two live images as options (64 bit being the default) 15:31:56 #agreed Workstation is OK with netinstall defaulting to 15:31:56 Server, but asks FESCo to only ship a single netinstall and 15:31:56 sorry, busy 15:31:59 remove the Workstation specific netinstall and install tree from 15:32:02 F21. 15:32:03 ugh, that was terrible formatting 15:32:05 #undo 15:32:05 Removing item from minutes: AGREED by jwb at 15:31:56 : Workstation is OK with netinstall defaulting to 15:32:08 heh 15:32:33 #agreed Workstation is OK with netinstall defaulting to Server, but asks FESCo to only ship a single netinstall and remove the Workstation specific netinstall and install tree from F21. 15:32:48 ok. kalev do you want to follow up with FESCo then? 15:32:59 sure, will do 15:33:01 thanks 15:33:07 #action kalev to follow up with FESCo 15:33:13 ok, let's get to branding 15:33:19 #topic Branding work 15:33:36 lots of discussion on brand and logos on the list, plus the websites work 15:33:41 ryanlerch, want to cover the state of things? 15:36:14 * jwb hopes ryanlerch is typing furiously 15:36:48 multitasking is hard :-D 15:37:11 stickster, run over and hit ryanlerch with a stick to get him to type faster :) 15:37:19 ow 15:38:15 The beatings will continue until morale improves. 15:38:56 * stickster notes ryanlerch is typing furiously 15:39:00 we have summarized the points of view of the different voices on the thread, and are going to reach out to them, and the GNOME design team to try find a way to try to come up with a plan to both make Fedora more visible on the workstation, but keeping the style and design goals of GNOME in mind. 15:39:37 ok. in time for F21? 15:39:39 I saw mattdm yesterday while I'm up here in Westford and we discussed also... we want to have a win-win for Fedora + GNOME brand 15:40:17 It's hard to say this would block F21 release 15:40:31 that's not what i asked :) 15:41:24 I suspect we could have a plan together by then, but depending on the level of change needed, it seems like that could be difficult 15:41:25 IMO, it would be great to have some more branding in place for the Workstation for f21, to cement the Workstation as a product, and it's own thing. 15:41:54 ok. so possible for f21 but not a blocker 15:42:00 I guess it would depend on getting support from all involved, and not disrupting the release schedule 15:42:04 ryanlerch, what about the websites rework? 15:43:47 Ideally I think it would be good to get some brand input from someone who has expertise in brand appearance/effect on audience 15:44:06 the websites team is working on implementing the mockups that were proposed last week, and should have a preliminary implementation fairly solid by this time next week. I will need some input from the WG on some of the features that we want to highlight on the brochure page. 15:44:47 as for downloads, the workstation downloads page is going to have 2 options -- the 64 bit and 32 bit live images. -- 64bit being the default choice. 15:45:49 * stickster notes that the highlights don't need to be 100% diff between F20->F21. We should be emphasizing all the strong suits of the WS even if they've been there for a while 15:46:01 er, maybe s/all// 15:46:04 stickster, +1 15:46:07 "all" of them won't fit. 15:46:08 stickster, +1 15:46:25 Release notes are where we talk about changes... the brochure is general promotion 15:46:40 What do people think of saying something like "Built on GNOME technology" somewhere in there? 15:47:19 I was thinking about it while driving this morning... 15:48:34 stickster: let a windows or osx user read that an he/she would wonder wtf that means 15:48:35 yeah, I don't have a strong objection, but I kinda wanted to emphasize the FW being its own thing (and not just a vehicle for GNOME (or anyone else), so on that basis I am a bit tempted to try not making GNOME a bit part of the announcement for the first release 15:48:59 * stickster not hung up on it, just an idea :-) 15:49:10 stickster: for people that know it it doesn't add much 15:49:16 cschalle, i kind of agree -- people that know what GNOME is will recognise it immediately. 15:49:30 from the screenshots and such 15:49:35 true 15:49:47 agreed 15:50:26 What do people think about having a picture of fried pickles? 15:50:49 I think that would be in breach of our code of conduct ;) 15:50:53 * stickster pipes down, just being goofy ;-) 15:51:09 you can't really download food 15:51:12 anything else on branding? i'd like to get to the open seat briefly 15:51:16 not sure we have time for anything else 15:51:39 what else was on the agenda? 15:51:46 xdg spec? 15:51:50 package additions/removals and the xdg thing 15:52:00 ok 15:52:15 kalev had an item about added/removed apps too 15:52:21 oh, sorry -- thanks jwb 15:52:29 thanks for the update ryanlerch 15:52:31 * stickster too old & slow 15:52:36 #topic Open WG seat 15:52:48 * kalev notes that we don't have aday today. 15:52:51 so last meeting we had rdieter_work say he was interested and aday was on PTO 15:52:59 and i haven't heard from aday in the interim 15:53:05 I hear he should be back next week 15:53:24 does the WG want to wait to talk to aday? 15:53:38 yes, please 15:54:00 I'd like to wait too 15:54:10 ok 15:54:17 Yeah, that would be fair 15:54:42 ok, we'll wait 15:54:49 #topic open floor 15:55:05 we'll do a short open floor and see if we can cover the other agenda items on the list 15:55:23 anyone have anything? 15:55:41 kalev: package stuff? 15:55:56 yes, but that's not urgent, we're running out of meeting time now 15:55:59 stickster, i don't think we'll have time to walk through it 15:56:01 just wondering what time is the next meeting in two weeks? 15:56:12 juhp_, oh, timechange stuff :\ 15:56:34 let's see... i think .eu and .us will be on the same time by then? 15:56:35 yeah, no idea how big the list is... jwb, kalev, does this need some sort of special time to get through before next biweekly? 15:56:49 stickster, i think we can probably walk through most of it on the list 15:56:53 k 15:56:55 * kalev nods. 15:57:03 * stickster eats some more fried pickles 15:57:29 juhp_, what time is 15:00 utc in your locale on nov 5? 15:58:00 jwb, 00:00 JST 15:58:08 that's the current meeting time right? 15:58:12 yes 15:58:27 JST = Jens Standard Time ? 15:58:30 which is 11am east coast US 15:58:33 haha 15:58:38 J = Japan :) 15:59:02 no DST here... 15:59:11 date --date='15:00 utc nov 5' on the command line seems to work for figuring out the local time 15:59:35 kalev, yeah. 10am EST which is an hour earlier 15:59:46 i'll create a whenisgood and send it around again 15:59:52 it's an hour earlier for Europe too 15:59:52 cool 16:00:01 kalev, yes 16:00:07 i'm sure everyone else's meetings will shift because of the change and we might wind up conflicting a bunch if we stay at 15:00 utc 16:00:16 * jwb hates timezones 16:00:34 #action jwb to send a whenisgood for the next meeting 16:00:40 anything else for open floor? 16:00:43 thanks! 16:00:48 Thanks jwb 16:01:00 #info follow up on package adds/removals on-list in the meantime 16:01:04 thanks all 16:01:09 #endmeeting