15:00:03 #startmeeting Workstation WG 15:00:03 Meeting started Wed Sep 14 15:00:03 2016 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:03 The meeting name has been set to 'workstation_wg' 15:00:06 #meetingname workstation 15:00:06 The meeting name has been set to 'workstation' 15:00:08 #topic Roll call 15:00:10 .hello pfrields 15:00:10 stickster: pfrields 'Paul W. Frields' 15:00:37 oh, is it now? 15:00:43 an hour earlier than I thought, good :) 15:01:23 :-) 15:01:48 .hello otaylor 15:01:48 otaylor: otaylor 'Owen Taylor' 15:02:26 .hello mclasen 15:02:27 mclasen: mclasen 'Matthias Clasen' 15:03:52 .hello rdieter 15:03:53 rdieter: rdieter 'Rex Dieter' 15:03:55 #chair kalev otaylor mclasen rdieter 15:03:55 Current chairs: kalev mclasen otaylor rdieter stickster 15:04:40 #topic Workstation OStree delivery for Beta -- are requirements met? 15:04:45 #link https://fedoraproject.org/wiki/Changes/WorkstationOstree 15:04:49 #link https://fedorahosted.org/rel-eng/ticket/6399 15:04:53 #link https://pagure.io/releng/issue/107 15:04:56 #link https://public.etherpad-mozilla.org/p/WSosTreeRequirements 15:05:23 cschaller coming online now 15:05:29 dgilmore: FYI Worskstation WG is meeting now on OStree delivery for Beta, to see if requirements are met 15:05:35 (hi) 15:05:51 hi 15:06:06 I was probably supported to provide a status for this, but I don't have much 15:06:07 mclasen: Do we know how the config for https://kojipkgs.fedoraproject.org/compose/ostree/rawhide/ is maintained? 15:06:07 #chair mcatanzaro cschalle 15:06:07 Current chairs: cschalle kalev mcatanzaro mclasen otaylor rdieter stickster 15:06:27 otaylor: it lives on pagure, let me find the repo 15:06:28 * stickster will limit this to stop at :30 so we can do Wayland status 15:06:55 mclasen: Is it https://pagure.io/workstation-ostree-config ? 15:07:12 yep 15:07:45 stickster: okay 15:08:07 otaylor: it is that repo 15:08:13 dgilmore: thanks 15:08:17 mclasen: That fourth link above purports to be the requirements for changes to processes/tools so that we can be offering a prototype/preview of the ostree based Workstation 15:08:39 otaylor: we have not had any f25 trees 15:08:46 because the f25 branch is missing 15:08:50 so, the main thing I haven't gotten an update on is the status of having an installer, and of merging back work from here: https://pagure.io/atomic-ws 15:09:06 dgilmore: in the workstation-ostree-config repo ? 15:09:11 mclasen: yes 15:09:18 ok, I'll get that created asap 15:09:25 I asked for it and for releng to get acces to the repo this week 15:09:36 I got access sbut apparently the branch was not created 15:09:41 so I will do so today 15:09:43 that would be useful (access for you) 15:09:46 thanks! 15:10:09 we have installer configs 15:10:29 https://pagure.io/fedora-lorax-templates 15:10:31 oh, good 15:10:33 they are in there 15:10:53 we are in better shape than I thought 15:13:10 with the branch in place, we'll have an f25 image with an installer for the beta, I assume ? 15:13:18 does that answer the question ? 15:13:32 mclasen: well it needs to be configured 15:13:41 and we need to test that it works 15:13:44 i'm not sure i want to promote this yet since the fedora ostree handling is not very good yet 15:13:47 but we can have it yes 15:13:53 among other things i'd like people to see static deltas 15:13:59 walters: it will be labeled as experimental 15:14:00 which really requires changing the cadence 15:14:33 what does "cadence" mean? too difficult english for me, sorry :) 15:14:52 walters: what do you mean by that? updating a branch periodically and generating a static delta between the commits on that branch? 15:14:53 walters: just to be clear, the "promotion" will be limited to noting in the release announcement that we have a Workstation in an experimental form factor for the intrepid 15:14:54 have a branch that updates once every two weeks e.g. 15:15:10 walters: that is not what was asked for 15:15:24 dgilmore: No, what you gave us is what we wanted! 15:15:27 kalev: "cadence" == rate of recurring release in this case 15:15:35 ahh, thanks stickster 15:15:50 kalev: think of it like "speed of the drumbeat" :-) 15:16:07 dgilmore: First we need to know we're building something that works before we can worry about how people efficiently update it 15:16:11 the repo will update with updates pushes 15:16:12 dgilmore: will the current setup update the ostree post-release at all ? 15:16:21 continuously ? 15:16:29 mclasen: we need to have bodhi update the repo with updates 15:16:39 its some configuration in bodhi 15:16:53 which to me is in the scope of what you asked for 15:17:20 mclasen: I think walters wants to have regular new updaed installer dvds 15:17:36 (which is what I'm doing in CentOS CI right now) 15:17:36 which you explictly said you did not want according to the notes I have 15:18:06 dgilmore: right, line 22-25 in https://public.etherpad-mozilla.org/p/WSosTreeRequirements 15:18:22 the request That I have is to amke the installer as part of the GA release, and all updates handled via ostree repo updates 15:18:33 stickster: yep 15:18:37 that's how I read it too 15:19:08 otaylor: mclasen: that is what you want? 15:19:45 * stickster notes this is just one of a number of reasons why we should not refer to this as an "Atomic Workstation" 15:19:58 dgilmore: Yes, that's what we want. I think that walters is saying that *eventually* we don't want every rpm-ostree compose to go directly to users 15:20:07 i have already had to fix multiple issues in the installer 15:20:26 I think it would make a lot of sense to follow the same release system as we have right now for regular fedora, with media together with GA and QA signing it off, and then updates afterwards 15:20:32 at least initially 15:20:34 kalev++ 15:21:03 yes, since that is what we asked for, we should be happy to get just that for f25 15:21:06 So, to the question asked in the /TOPIC... are we at a point where requirements are *nearly* met? 15:21:17 just to sanity check, i am the only person who is running and debugging this right now, right? 15:21:24 respinning the installer or batching updates would be separate topics 15:21:33 walters: I was running it for a few weeks, then I got off the train, need to get back on 15:21:34 walters: I'm not currently running it, thats true 15:21:53 I have used your installer successfully, at least once 15:22:17 stickster: I think the releng requirements are met, other than building installer images 15:22:40 otaylor: OK, and IIUC from above, that requires the branch creation so dgilmore can go ahead with that part, yes? 15:23:13 yes, thats my understanding 15:23:56 stickster: In terms of whether we want to advertise it in the release announcement, that depends on other things than the releng bits 15:24:30 otaylor: Yes, also on how wide a net we want to cast in terms of people trying it. Because that means an unknown bug input too 15:24:33 stickster: namely, making the experience smooth for the bits we expect to work, and being comfortable with people trying it out without the bits that we don't expect to work 15:24:40 exactly 15:25:24 dgilmore: where exactly does that branch need to be created, and who's resopnsible for that? 15:25:48 * stickster fires his typist again... bugger keeps coming back like a bad penny :-D 15:26:42 stickster: in the pagure repo 15:26:47 stickster: I am on it now 15:26:53 Ah, OK 15:27:04 atomic-ws? 15:27:05 the branch now exists 15:27:11 ha, cool, no #action needed then :-) 15:27:12 it just needs a bunch of adjustments 15:27:30 or maybe... 15:27:34 stickster: https://pagure.io/workstation-ostree-config is the source 15:27:44 I am working on the adjustments 15:27:48 #action dgilmore make adjustments in Pagure repo workstation-ostree-config to accommodate required installer builds 15:28:03 #info Requirements are nearly met at this point, looks on track for F25! 15:28:14 dgilmore: thanks very much for being here and helping with this section of the meeting :-) 15:28:19 dgilmore++ 15:28:31 stickster: no problem 15:28:33 2 minutes left before we need to move on, anything else? 15:29:15 #topic Wayland status for Beta 15:29:26 #link https://bugzilla.redhat.com/showdependencytree.cgi?id=1372055&hide_resolved=1 15:29:59 #info First and foremost, thank you to mclasen for the work of organizing the tracker :-) 15:31:11 mclasen: So if I read the statuses right, two of these bugs are fixed either in Fedora, or upstream and coming shortly to Fedora... 15:31:15 one is uncertain whether it can be reproduced (I couldn't on current F25 Workstation, and neither could at least one other person)... 15:31:29 the keyborad-display bug is fixed upstream or will be very shortly 15:31:34 and one looks like it might need some work (https://bugzilla.redhat.com/show_bug.cgi?id=1256443) 15:31:56 * stickster notes this last one ^ is the one mclasen is referring to 15:32:02 that's great to hear 15:32:14 the 2 gnome-shell bugs should be fixed in 3.21.92 15:32:31 mclasen: There is one other bug which looks like it's been accepted as a F25 Final blocker, the file-roller issue, but that should just be a matter of forcing the X backend while it gets fixed 15:32:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=1374321 15:32:49 the environment bug, I'm not sure. halfline explained the plan, but I don't know that the patches have made it into systemd 15:33:20 stickster: I'll find somebody to do that file-roller change today 15:33:30 halfline: if you're around feel free to poke your head in here :-) ... if I read the bug correctly, there was a fix to gdm which works around the issue, but I don't claim to be an expert here 15:33:36 If we don't know how to reproduce a bug, it should be removed from the blocker list 15:33:48 there's a few upstream bugs that I would consider blockers, that are not reflected here 15:33:49 is it just putting a g_set_env call in main() ? I can do that in that case 15:34:00 mclasen: Can you #link them here for reference? 15:34:48 Also, I wonder whether there is a running list of apps where the X backend is forced, so they can be knocked off in 3.23 timeframe where possible 15:34:55 (or later) 15:35:12 that's more an upstream question, of course, but would be good to know 15:35:13 https://mail.gnome.org/archives/release-team/2016-September/msg00036.html 15:35:17 has a bunch 15:36:21 mclasen: cool... if I read that right, these are patches coming in as freeze breaks upstream, so it's not like they're in limbo 15:36:34 and this: https://bugzilla.gnome.org/show_bug.cgi?id=771117 15:36:46 all of these should be fixed in 3.22 15:36:56 mclasen: anything you know of where there's no patch or ETA, and thus worrisome? 15:37:20 the environment bug is the one I would think of first 15:37:31 there's patches, but not entirely clear what the solution will be in the end 15:38:41 kalev: gdk_set_allowed_backends ("x11"); 15:39:03 mclasen: ahh, let me do that, thanks 15:39:14 hrrm, I see -- I did misread the bug for that one 15:41:11 stickster: another thing I didn't mention is that wacom tablet configuration missed our 3.22 freezes upstream 15:41:25 so we're looking at landing that in f25 as backports 15:41:38 is it possible to break the freezes upstream after .0? 15:41:58 it'll certainly make translators unhappy 15:41:58 or too much translator work like this+ 15:42:14 mclasen: AFAIK we don't have tablets as a criterion for the general Fedora desktop, but even if we did, the fallback to X still works AFAIK... I did it the other day 15:42:27 *(that's a lot of AFAIKs, sorry) 15:42:41 But it looks like we're in broadly good shape 15:42:54 mclasen: So we're really relying on halfline and systemd upstream to work out a solution where environment gets passed correctly for Wayland 15:43:09 we're in good shape, is my assessment too 15:43:43 yes. I think halfline ran off for lunch already 15:43:53 we can catch up with him later 15:45:22 * stickster notes someone raised this bug too: https://bugzilla.redhat.com/show_bug.cgi?id=1373169 -- but it doesn't seem clear that it's happening everywhere 15:45:46 That would be another good one for halfline 15:46:21 It does, however, happen here for me :-) 15:46:40 killing the session let me login again but that's pretty ugly 15:46:46 sessions not ending properly is not wayland-specific, unfortunately 15:46:52 *nod 15:46:54 Also the one where you cannot paste into the modal password dialog is quite unfortunate, do you think you could find someone with time for that mclasen? 15:47:15 mclasen: I think we can safely trust that will be worked assiduously :-) 15:47:35 I thought I had marked that for 3.22 already. I'll find somebody 15:47:41 Thanks 15:47:57 mcatanzaro: how far along is the webkit clipboard ? 15:48:25 mclasen: garnacho has it working, he just has to get it past code review :) 15:49:23 right, ok 15:50:27 I'm +1 for sticking with Wayland... i.e. no action ;) 15:50:42 So I'd like to propose this: #agreed The WG team has seen no issues that would prevent us from going forward with Wayland as default -- no action required 15:50:54 +1 15:50:55 mattdm: ^ fyi 15:50:57 +1 15:51:04 +1 on my own proposal ;-) 15:51:45 +1 15:51:50 exciting! 15:52:07 cschalle: rdieter: ? 15:52:34 hopefully they are awestruck that Wayland is doing this well :-) 15:52:52 please get your votes in guys, we have one more short topic to cover 15:53:13 Who wants to blog about it, cschalle? mattdm, can you talk to marketing team to make some news? 15:53:14 +1 15:53:22 sure, I can do that 15:53:37 (+1: 6, 0: 0, -1: 0) so far -- so we're good to go at this point. 15:54:03 #agreed The WG team has seen no issues that would prevent us from going forward with Wayland as default -- no action required (+1: 6, 0: 0, -1: 0) 15:54:15 mclasen: I put the file-roller oneliner patch in https://bugzilla.gnome.org/show_bug.cgi?id=770333 15:54:17 Nice work team! 15:54:46 #action mclasen + stickster follow up on noted bugs as discussed earlier 15:54:49 mclasen: sorry, didn't realize in time it was a gtk+ bug and not a file-roller bug, woops 15:54:53 #topic Deliverables for F25 15:54:56 #link https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fedora25#Workstation 15:55:22 Jan Kurik asked early this morning whether we could review this list. So far I see at least one thing missing which is installer images for the ostree-based Workstation, as we discussed earlier 15:55:28 stickster: sorry, I got pulled away @dayjob for a bit, consider me +1 too 15:55:35 those would be on here as "non release blocking" 15:55:39 rdieter: no worries sir! 15:55:50 #info previous vote is now (+1: 7, 0: 0, -1: 0) 15:56:24 kalev: I consider that use of custom clipboards a file-roller bug... 15:57:04 I don't think we know an image path in the distribution tree for these images yet, and I don't know what the testing commitment is based on the requirements we looked at earlier 15:57:22 mclasen: yeah, I don't disagree, just thought that it gets more easily accepted to file-roller upstream with this wording 15:57:26 #action stickster to follow up with jkurik to note missing ostree install image 15:57:39 Are there any other deliverables expected besides that, which change this list from F24? 15:58:31 mclasen: otaylor: ^ anything I missed? 15:59:18 stickster: Don't think so (the ostree images should be non-blocking, fairly obviously) 15:59:24 correct, noted above 15:59:28 * mclasen doesn't have anything 15:59:41 OK, I'll edit the wiki and follow up with jkurik as above 15:59:53 that takes care of this topic :-) 15:59:56 #topic Open floor 16:00:04 Now you have a whole 30 sec to talk about other stuff :-) 16:00:10 kalev: thanks for the quick patch; I'm trying to get a file-roller release for 3.22, will try to include that 16:00:58 #action stickster fix Fedora calendar entry for this meeting 16:01:09 mclasen: nice, thanks 16:01:10 OK, I think we can take everything else back to #fedora-workstation 16:01:14 Thanks for coming, everyone 16:01:16 #endmeeting