14:00:43 #startmeeting Workstation WG 14:00:43 Meeting started Mon Dec 5 14:00:43 2016 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:43 The meeting name has been set to 'workstation_wg' 14:00:49 #meetingname workstation 14:00:49 The meeting name has been set to 'workstation' 14:00:52 #topic Roll call 14:01:01 hello 14:01:03 .hello pfrields 14:01:04 stickster: pfrields 'Paul W. Frields' 14:01:28 Hm, the meeting room is apparently topic locked, not that it matters for minutes 14:02:09 jwboyer: if you get a chance, maybe you can fix that ^ ... chanserv says you're a founder 14:03:12 .hello catanzaro 14:03:13 mcatanzaro: catanzaro 'None' 14:03:25 maybe it's easier if we just move to #fedora-meeting-1 instead of fighting with topic changes here? 14:03:26 * pravins listening 14:03:55 kalev: don't worry, I'm not going to fight it, but let's not move again and cause more confusion 14:04:14 if we can't fix I'll set up a different location for next time(s) 14:04:22 * kalev nods. 14:04:45 #chair mcatanzaro kalev mclasen cschalle juhp rdieter_work 14:04:45 Current chairs: cschalle juhp kalev mcatanzaro mclasen rdieter_work stickster 14:05:14 Anyone seen other folks? I expect juhp to be here since we shifted time mainly to accommodate him ;-) 14:06:30 its snowing here, so owen might be in traffic... 14:06:52 mclasen: yay, winter weather! 14:07:54 we don't have quorum, but I think our first item was going to be on the Change for coredumpctl, right mcatanzaro ? 14:08:23 we could go ahead with that and hope other folks show up afterward; if not, short meeting. 14:08:57 #topic F26 Change for coredumpctl 14:09:15 #info (TOPIC: F26 Change for coredumpctl) 14:09:31 #link https://fedoraproject.org/wiki/Changes/coredumpctl 14:09:56 So I have a change page prepared but not yet submitted 14:10:38 I mailed one of the ABRT developers (Jakub Filak) to ask for feedback but got no response, maybe he's on vacation or just unhappy about the change. So I think we can proceed. 14:10:54 The SELinux bug is still a blocker. Last meeting we decided to escalate that to FESCo. 14:11:30 I forget whose action item that was. Mine was to write the change page. :) 14:11:47 That's all I wanted to say about this! 14:12:07 mclasen: do you know any of the other ABRT developers? I think we should at least get some sign they're aware of this change 14:12:19 I tihnk I saw jfilak recently left 14:12:25 left red hat, I mean 14:12:29 Ow 14:12:51 So he was the only ABRT developer who was really visible, bad timing. :( 14:12:52 so things might be a bit up in the air on the abrt side currently 14:13:03 oof 14:13:20 I see a mhabrnal on their commit log quite frequently 14:14:37 #action stickster Find out if there are any folks full time on ABRT atm 14:15:26 mcatanzaro: ISTR the idea was to try and get someone from ABRT + someone from selinux together with us to discuss the bug + change page 14:15:27 hola 14:15:31 before we go the fesco route 14:16:01 I agree, would be good to discuss with someone from the ABRT side before going behind their bcaks 14:16:39 If no one will talk with us or we can't get an agreement going, then FESCo is an escalation step 14:17:28 * kalev nods. 14:17:29 mcatanzaro: You might be able to reach the right people by raising visibility of the Change page on devel@ 14:18:24 mcatanzaro: so, abrt will pick up coredumps from the journal ? 14:18:34 It'll get announced there by jkurik, which happens (I think?) after the page is in the "ready for wrangler" status, which is done by adding a [[Category:...]] link 14:18:57 sorry I am late - forgot about the day change 14:19:21 yay, juhp_ 14:20:16 mclasen: Yes 14:20:34 then this seems uncontroversial to me 14:20:57 stickster: I guess we might as well just go ahead and do that and see if anyone responds? I guess it will be controversial actually, to no longer have core dumps created in cwd. 14:21:03 o/ rdieter juhp_ 14:22:14 mcatanzaro: Go ahead and change the category on the page -- that would be the next step AFAICT. It looks basically complete to me 14:22:32 #action mcatanzaro move page to "ready for wrangler" status 14:22:56 I'll still try to find us someone in ABRT to talk with us along with SELinux dev from the relevant bug 14:22:56 stickster: Done, wheels are now in motion.... 14:23:04 stickster: Sounds good, thanks. 14:23:20 Do we have cschalle here yet? 14:23:35 I have been here the whole time :( 14:23:58 Awesome, in that case... 14:24:05 #topic Branding proposal 14:24:12 #info (TOPIC: Branding proposal) 14:25:03 ok, should I just kick off? 14:25:20 cschalle: sure -- sorry, was navigating to the mail thread but I'm slow on this new keyboard still 14:25:49 So I wrote a first draft to the mailing list with a proposed wording for a mission statement around branding. Didn't get a lot of feedback so far. 14:27:02 I am sure the wording can be better, for instance based on hadess feedback I have been pondering if the word distinguishable would be better than the word distinct for instance, as I guess the word distinct might convey a bigger departure than what I think we envisioned 14:27:35 "distinct" connotes "different" 14:28:07 but at this point I guess I would like to hear from the other working group members what they think about the general mission statement, as once we have something we agree on I think we should also get the council to sign off on it before starting to look at implementation 14:28:23 I think it looks good, but not a native English speaker here 14:28:33 silly question, got any links for the draft, or can post what the proposed mission statement is? 14:28:36 I guess this is a bit language-lawyerly, but then again, if we don't want to be bogged down in that part of the discussion, makes sense to say "distinguishable"... meaning "you can tell" 14:28:53 rdieter: I'm trying to find the link in email web ui, bear with me :-) 14:29:13 rdieter, its on the workstation mailing list 14:29:23 title Branding Mission Statement 14:29:35 #link https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/message/JDTS6HNMQA2VTTQ7C7BAF5ZQC25JL75V/ 14:29:36 (assuming you are subscribed to the list ;) 14:30:35 obvious first question: distinct from what ? 14:30:46 I'm good with s/distinct/distinguishable/ -- I think it still establishes the goal that e.g. mattdm wants 14:30:48 distinct from the fedora server ? 14:30:56 thats fine with me 14:30:56 stickster, yeah, I think in my mind both distinct and distinguishable both mean 'identifiable', but distinct maybe comes across as 'completely different' ? 14:31:13 mclasen, distinct from the rest of the world 14:31:33 cschalle: maybe not "completely," but yeah, "different" is sort of understood when you say "distinct" because it's like saying "distinct from some other thing." 14:31:40 that, I'm not so sure about... we want to be the same as the rest of the world, in most respects 14:32:09 mclasen, to some degree yes, which is why we are having a discussion now about distinct vs distinguishable :) 14:32:22 I think "distinguishable" is better, since it specifically means the viewer can tell what they're seeing (they can distinguish it), without presuming that it has to be *substantially* differnt 14:32:44 But "distinguishable" doesn't automatically mean "identical" either, so let's not assume that ;-) 14:33:07 I don't think the intent is for Workstation to be different from Server (that's kind of implied with Server having only Cockpit as its official GUI) 14:33:19 so is this more about theming or is there more planned to it than that? 14:33:28 I don't know what to think of this proposal TBH. I agree that Fedora needs to be distinguishable; right now if you change the desktop wallpaper you've no way to tell the difference between it and Debian or any other GNOME distro. 14:33:34 It pretty much means recognizable as Fedora 14:33:36 I agree with the mission to make the fedora workstation a coherent product ('more than sum of parts') 14:33:40 But I hope we don't start making huge downstream UI changes. 14:33:41 it's a fine line I guess... because as others pointed out, we don't necessarily want to change anything radical about the GNOME interface, which has been user tested to some degree I guess 14:33:45 I'm not sure branding has a significant role in that 14:34:09 juhp_, well that is the follow-up, to discuss how to implement the mission statement, doubt we go down the path of trying to do a separate theme though, most likely going to be something a lot more subtle 14:34:18 cschalle: +1 14:34:22 okay 14:34:25 also mcatanzaro += 14:34:27 +1 14:34:48 sounds reasonable to me 14:35:19 I think one issue is that when we've had this discussion, invariably five people jump into the discussion with strawmen that don't necessarily work from a design perspective 14:35:29 I don't think the plan here is to make huge downstream ui changes, maybe just put a fedora logo and name here and there. right cschalle? 14:35:50 I would really like to see designers bring their expertise to bear here, and not presume what the result is off the bat 14:36:18 kalev: I don't think that's necessarily what's going to happen either. I think cschalle's proposal rightly leaves the implementation to the designers. 14:36:27 kalev: heh, that kind of example is what I was hoping to avoid as a rat-hole :-D 14:36:35 kalev: worst kind of branding 14:37:00 kalev, well I don't want to preclude the implementation discussion to much, but yeah my approach is that I eventually want to come up with something that is clear, yet unintrusive. And I do want us to review the current branding things we got as part of this, so it is not just about adding here, but about where and how 14:37:43 * kalev nods. 14:38:34 cschalle: So do we have any designer(s) lined up to work on this within a reasonable time frame, i.e. before we get to Alpha freeze (end of Feb)? 14:38:35 my hope is that whatever we do in Fedora would also work in RHEL, so that we could share code and bugs and everything 14:38:58 I think it is going to require some serious effort to get there, in particular if it has to be distinct 14:39:02 kalev: That's not a bad point 14:39:12 stickster, I don't have anyone formally assigned at this point, but hopefully between you and mclasen you should be able to rustle up people 14:39:15 mclasen: "distinguishable" ;-) 14:39:16 but I agree that listing our current 'branding' efforts is a good starting point 14:39:18 * mcatanzaro has to leave early today, bye 14:39:26 * mcatanzaro pleased that designers will be consulted 14:39:32 mcatanzaro: thanks for being here! 14:40:12 I can volunteer to start a wiki page for that, do we have a canonical place for it ? 14:40:23 * mclasen hasn't been in the fedora wiki in some time... 14:40:57 mclasen: I honestly don't know. If not, I guess one thing we should consider is how this fits in with other edition branding, e.g. Cockpit/Server 14:41:01 anyway, my suggested path forward is that I will put the statement onto the wiki and also check with mattdm if the council wants to review it before we move forward. I will replace distinct with distinguishable 14:41:26 ah, ok, so mclasen beat me to the wiki page creation :) I am fine with that 14:41:41 might not be as much about matching, more about being complementary... again, design question 14:42:08 #action mclasen start wiki page about the larger branding effort 14:42:18 so is it Fedora Branding or Workstation Branding btw? 14:42:28 juhp_: "Yes" 14:42:28 #action mclasen stickster powwow about designers to rope into effort 14:42:29 I will do a page that lists what branding we currently have in place 14:42:37 sgallagh, lol 14:42:38 Fedora Workstation, sgallagh doesn't like it when we try to dictate him and the server team ;) 14:42:42 I'm somewhat on the fence about larger efforts 14:42:47 cschalle: Not so, actually. 14:43:04 /me clarifies 14:43:15 sgallagh: juhp_: I think whatever happens in Workstation should at least be *complementary* to e.g. something like Cockpit in the Server edition 14:43:29 I think that the direct need right now is for "Fedora Workstation" to be recognizable as compared to e.g. Debian GNOME 14:43:44 Desktop branding? :) 14:44:02 As a long-term goal, I think Fedora as a whole should probably establish some additional branding guidelines that Workstation and Server/Cockpit would try to adhere to. 14:44:23 sounds reasonable yeah 14:44:53 juhp_: I'm trying to indicate that this isn't a "Fedora" XOR "Workstation" topic, but a "Fedora Workstation" topic. 14:45:19 does Cockpit have any kind of Fedora branding as prior art we could use? 14:45:20 ok - I am just trying to clarify the intent 14:45:58 kalev: Cockpit has fairly simple (but effective) branding 14:46:09 sgallagh, by Workstation I meant Fedora Workstation... 14:46:34 The login page for it has a logo available and all of the logged-in pages identify that the system is "Fedora Workstation", "Fedora Server", "Red Hat Enterprise Linux", etc. 14:46:34 sgallagh: but is it distinct ? 14:46:38 Cockpit is never called "Cockpit" in Fedora Server 14:46:43 it is "Fedora Server" 14:46:59 nice! 14:47:20 mclasen: I'm afraid of getting into a debate about the meaning of that word. 14:47:29 sorry, just kidding 14:47:30 It's never ambiguous what OS it's running on 14:48:04 (Also, if you run Cockpit on Fedora Workstation, it clearly identifies the system as being "Fedora Workstation Edition") 14:48:25 because that is what it is :) 14:49:17 thats nice 14:49:30 Now, the approach that Cockpit has taken is unlikely to be a good fit for Workstation 14:49:36 But it *is* recognizable 14:50:04 So mclasen, it seems like the WG should participate on, or at least stay tuned to, your wiki page so we have an idea what the objectives for the designers are 14:50:20 https://fedoraproject.org/wiki/Workstation/Branding 14:50:35 great that is what I would have used too :) 14:50:36 more to come 14:50:38 * stickster takes a moment to note... he has to close this meeting at :55 (in 5 minutes) to chair another meeting elsewhere 14:51:39 Sounds like no one's opposed to rolling forward with this... and I guess we can go to open floor for a few minutes? 14:51:49 #topic All other business - open floor 14:52:00 #info (TOPIC: All other business - open floor) 14:52:53 do we need to act on the flatpak runtime discussion ? I have to admit that I didn't fully follow the mailing list discussion on it 14:53:05 Oof, I need to catch up on that thread myself mclasen 14:53:12 ok, next time them 14:53:15 then 14:53:22 OH! Meeting schedule 14:54:12 So... the next meeting is scheduled for Monday Dec 19... but I will be on PTO. I'll hit list to find a chair. The meeting after that is Monday Jan 2 which is an observed holiday for most of us 14:54:36 I would like to not skip two meetings, thus the above. Any opposed or can't make it to either one? 14:55:51 OK then... 14:55:53 #action stickster hit mailing list to explain meeting schedule going forward, establish a chair for Dec 19 meeting 14:55:57 I can't make it to Jan 2 probably 14:56:32 kalev: yeah, I doubt many folks will... I would think we should cancel that one, but the 19th we should do... esp. with the flatpak questions potentially in the air 14:56:41 * kalev concurs. 14:56:46 * stickster might be persuaded to get up in time for that meeting and chair it in his PJs, not sure yet 14:56:54 +1 14:57:10 OK, closing up here then, I have to roll to my other meeting! 14:57:17 Thank you for attending, everyone! 14:57:20 #endmeeting