 Oh, sir. Oh, I'm taking them all? Hi. All right. I appreciate it. What? I forgot when your talk is. I should have called it out. Yeah. Oh, yeah. I'm tangled up. Okay. So, who's going to present? We're not going to share this. What do you have two microphones? Yeah, we have two. So, one of them is this one. Okay. We have 40 minutes total. And we'll show you when it's left. You have scarves to give out as questions if you have time for questions. All right. And water is here. And let's make this thing. So, which one do you have? It's HDMI, right? Okay. It should work. So, we have a quick review. We have a quick review. Okay. I'm going to go to 1024 resolution. But yeah, it will work probably. This might as well do it. Maybe it won't. We have a quicker review one. Can you see this? Yeah. My track hat is all those lucky. Oh, there we go. It came back. There we go. Okay. Okay. Okay. It's decent already. Yeah, it's so good. It looks okay. Get it to a four by three. How far do I want to go? 1024. Please. Just exit full screen. Oh, I need this. Go back. Put the main screen. Okay. Just go to the next slide. It's just because this slide doesn't have it on it. Oh, you're all right. Is this a PDF or something? Yeah, maybe it's a bit presenting. It's still working on this. Sorry, this is actually a, it's my Samsung. That's the issue here. Is that what I'm talking about? It's loading. Okay. So hopefully we'll be able to start now. So please welcome our next presenter, Paul Freels. So welcome everybody. Sorry for the interruption. Sorry for the trouble getting started here. We ended up being delayed a bit by the last speaker. And then technology happened. So yeah, I'll be taking that out of your next bonus. I'll talk to Denise about that. I know you don't. Yeah, it's probably good because you know what's going on. We're going to talk about Fedora Workstation. As Matthew indicated earlier, 80% of the downloads are Fedora Workstation. We're going to kind of speed through the beginning here and talk a little bit about the background of Workstation. I think before we start, we should say that this talk doesn't go well in this boring. Then you can blame Christian Schaller, who was supposed to be here and give this talk. But he's expecting his second child any day now. So he decided to stay home for that and sent us instead. All right. Basically, why do we have a Workstation? Matthias is going to explain what we've done so far, what's happening now. We're going to talk about the outlook for the future. All right. So why a Workstation? The main reason is because it appeals to a broad range of users. The Workstation, we've talked about it targeting software developers. And that is indeed our focus for features. We're going to make decisions about what priorities we have and what's going to matter. But the important thing to remember is that developers are not unlike other people. They have 90% of the same needs that any of us have. I'm not a software developer, but most of the things that happen at Workstation actually benefit me as a user. Because developers share a lot in common with other productivity users. So the way we talk about this and I guess want to talk about the very esoteric subject of target audience I usually get bored and fall asleep at that point. Because I think we've done a pretty good job of explaining this, but I'm explaining it here again. Developers are a central focus, but the things that we do for them tend to benefit all users. And we do care about that. Developers also like to play movies on their desktop, for example. Who is it who's working on this stuff? The Workstation Working Group. We have a close collaboration with other upstreams. So the Working Group itself is made up of several people. Mattia sits on the Working Group, I sit on the Working Group. There's a number of people who I think are not represented here today who are part of it. Ryan Lurch. Call of Lembur. Rex Dieter definitely helps keep us oriented on desktop standards and making sure that we work well with other desktops as well as we move on in technology. As we're doing this, we collaborate closely with other upstreams, like the GNOME community, obviously, where we get a huge amount of technology. So the things that you see in Fedora Workstation, although we're proud of them being in Fedora, a huge, huge thanks and respect goes out to the GNOME.org community because they are actually creating and integrating downstream in Fedora. And, of course, there are other things that we pick up as well, LibreOffice, as little Firefox and so forth. There are many variances. So we don't simply take things from the upstream and then plop them down. We do actually think about some curation. We think about what are the things that the developer who sits on a Fedora Workstation is going to want installed by default. And we do make some choices to make sure that that's a smooth experience and that it matches our focus. Actually, use the down arrow here. It's easier. Okay. So I'll talk a little bit about what we've done so far. As the slide says, the Workstation is, I think, three releases old now. We started in 21, 22, 23. And so far, we've had, I think, fairly conservative approach to the changes we've made. To organize what we're doing here for the Workstation, we keep a task list on the wiki. You can look at that if you're interested in all the details. Here, I want to just call out a few of the highlights. So on the next slide, if you go on. I'll start with talking about software installation. That's been a really important focus area for us. Loam software is the application we have for that. It has come a long way since we first started doing it. One area where we really improved things is that Richard, who's sitting up there, has been really successful in pushing and pulling both upstreams and packages to provide us with better updater. Updater is the descriptions, keywords, screenshots, and translations for that. We need to present applications well in the UI. And so Richard has been using the carrot and the stick quite a bit to give us that data from the people who maintain those packages. And that not only helps us for representing the applications well in the UI, but it also helps us for making them searchable. So the keywords in particular that you really find applications better. Another aspect in which we've improved the search experience is that we also show the application search results in the GNOME shell overview. So if you're searching for something in the shell, then you'll find applications there as well. Another thing we've done here is we've reintegrated the codec and font and other extras installation into GNOME software. That used to be provided by GNOME PackageKit. And now it's all in one place so we don't need to include GNOME PackageKit at all. The last point on this slide here is about application add-ons. That's a concept that we introduced in GNOME software because one size does not really quite fit all when it comes to showing applications. There are lots of complicated applications like for instance Eclipse which come with tons of plugins and we kind of want to be able to support that well in GNOME software so we added the concept of add-ons. And for that we also need application metadata or add-on metadata. And I think that's still a little bit of an ongoing process to ensure that we have quality data for that as well. Right, next thing to call out here is the terminal. It's obviously a very important application for developers as I've included. It's been most of your day in the terminal and it's also an application that has a very long history and has very strong expectations for how a terminal application is supposed to behave. So any change we make here kind of has to be approached very carefully. Nevertheless, we try to identify a few things where we could make improvements and I've listed a few here. We've brought back transparency just for a little traffic demand. We've added notifications for long-running commands that is when you type make in WebKit for instance and then it takes two hours or so so you do something else and you forget about it. But when it's done you get a notification. That's nice. And then there's again search. It's a repeat topic here. The GNOME share search also shows you open terminals. And one last point I wanted to make about terminals is that the GNOME terminal maintainers also are a conservative bunch. So this is an example for where we introduced a bunch of work that we first did downstream and then we try to convince them to take it upstream and I think at this point only the transparency is to the downstream bit. Some more small things here. There's of course a lot of change that has happened over three releases and I cannot list all of this here. What I wanted to say about these is we try to address the real concerns that people have when they use the Linux desktop and try to make it change for the better. And one concern that we've heard repeatedly is that battery life is an issue. If you use your Mac that's much better and our Linux we're not doing so well so we try to make an effort to improve this and one of the outcomes of that is that we added support for handling the backlight automatically. That's a big power drain in the laptop. Maybe the biggest one that we can actually affect. So if you happen to have a laptop that has an ambient light sensor you can enjoy this feature. Or you can again go to Richard and buy a Colorhack ALS which gives that as a little USB dinghy. What I also wanted to say here is another example of a feature where the UI that we added in the control center to turn this on is really just the tip of the iceberg. We had to do all the user space plumbing that's called IIO sensor proxy. We had to work with color developers to fix driver bugs before we could actually put this tiny bit of UI in place on top of it. Yeah I think I'll skip the other two points here back to Paul. Okay I think I'm on again. There we go. Okay so we have a couple graphs right we didn't want to be the only people who showed up to the gun fight without a gun so we have some graphs for you. Right now and Matthew's going to recognize a couple of these right at least the next one I think I actually just lifted from his presentation. So this is a quick graph of some of the reports that we get back from ABRT and in looking at this you're going to see different colors here right the red line here is our current release Fedora 23 that's why you don't really see much happening until recently. We've managed to cut down on a lot of the noise that happens in ABRT I think that's why there's a much larger mass up here but one of the things that's been going on is for example our Fedora Kernel team has done a good job working with the ABRT guys to get rid of some of the noise that's there but also you know we tend to use the statistics that come out of the retrace server to sort of power our efforts to look at certain bugs so look at the things at the top the things that are causing the most user pain the highest incidence of reports and sort of address those and as you can see in general even though you know F23 certainly has had a rise in bugs I'm sorry it's a little bit obscured by the controls here for the slide show but you can see that's really not peaking anywhere near what we were seeing just in the very last release Fedora 22 so we feel like we're doing a pretty good job taking care of some of those issues it's really started to make a dent in the perceived quality of Fedora overall not just the workstation but certainly that is what we concentrate on alright and you'll recognize this from Matthew's slides the geologic ages of Fedora and you know just the point that we wanted to make here I think is that with the advent of the additions and the huge rise in this green area right from Fedora 21 forward we really look at this as a huge opportunity and something that people have definitely people have definitely glommed on to this idea that these additions can be better at focusing on a specific audience and doing something and doing it well as opposed to having you know one one addition or one thing that we produce that everybody then has to sort of tune in their own way if we can actually do some pre-tuning of those things before they get to the people that use them we can do a lot better job of serving those folks so anything else you want to say about that no I just want to say I love this graph it's so nice and colorful it's very rainbow like I really like I like the purple thing because that was when I was FPL that was that was my age the age what was it it sticks to rassic there you go I like it I take over again here at this point talking a little bit about what's coming in Fedora 24 that's the near future Matthew stole a little bit of my thunder for this slide because he talked about a bunch of this stuff already but I'll try to add some wrinkles here to this so Wayland first bullet point here so in the focus for a lot of my team's efforts this cycle we're basically really trying to dot the eyes and cross the T's and make the end session really have feature parity with the X11 session for your day-to-day use so as Matthew said we'll probably not even notice that you're using Wayland I guess from a marketing perspective that's a bit of a nightmare as a feature we do all this work for years then we do our job really well nobody will even notice that it has changed so we'll see how that goes as Matthew said we're still on the finish line for this and we'll make the decision whether we are ready to go out 24 before the alpha in early March switching X for Wayland but the benefit is basically it's enabling I mean on the one hand like from an engineering perspective Wayland avoids a lot of the crankiness and the things we had to work around in the X protocol for 20 years but it's not interesting for users it's interesting for us as engineers who work with the protocol Wayland enables us to isolate applications much better from each other like X basically was just one everything that could talk to each other and could see each other there was no notion of you could run an untrusted application because you could just steal all your keyboard input without you knowing so it's basically enabling isolation sandboxing for applications so as I said it's a nightmare the next bullet point here is much better for marketing perspective because you can actually take nice green shots of GNOME software offering you a graphical upgrade Matthew already talked about this as well it's basically the successor for the old pre-upgrade tool I think it was called and we'll do a good job here hopefully and we'll notice that when you run Fedora24 and the next release comes out we'll offer you to download and install Fedora25 and we'll try to check whether any applications or packages you have installed might break due to that and we'll warn you about it so that should all be in place and that will not only be in place for going from Fedora24 to Fedora25 but also we'll try to backcode this to Fedora23 so you can actually use it to go to Fedora24 already the next two bullet points here are also about GNOME software I guess you get the sense that GNOME software really still is a very active focus of work for us so BIOS firmware updates will be offered in GNOME software in Fedora24 if you went to Richard's talk yesterday you learned a lot more about that than I could ever say and if you missed it without the recording this is really interesting XTG app installation XTG app I haven't mentioned that before it's our effort to define how a container-wise desktop application should look and GNOME software will support installing these there's going to be a little bit of a preview in Fedora24 because we don't actually have a lot of established XTG app applications available yet to try this out on but at least you can use this for running the latest nightly builds of GNOME applications and maybe we'll get a LibreOffice XTG app as well and all these items I mentioned about GNOME software are basically all about making it easier to find and install software on your system so it's about making it less important what the default applications are because we'll have an easy time finding others we still chip default applications on the workstation so we did a round of review of the set of applications that we installed with default and I think we did make some changes but I'm blanking currently on what exactly those are maybe you know I'm off the mic but yeah so basically we'll chip a different set of default applications because we don't want to shit un-maintained and that things that might have security holes in them alright there's some more items here we also try to make sure that there are many fantastic QT applications that out there look nice and well integrated in the workstation environment so we'll we'll chip a QT settings integration I don't know what is this class it's called QT GNOME platform in Fedora24 and I'm not exactly sure what it does but I think it basically makes QT applications observe the GNOME settings and this is kind of like a follow-on to like the Aguaida bridge theme that we had in the earlier slide that we also have a theme that kind of tries to make QT applications look nicely integrated and this is more for the settings and the last item here I haven't talked about GNOME Builder yet at all GNOME Builder is our it's an effort to write a nice UI for making software and really it's pretty focused on desktop applications desktop software but the focus will widen as the materials and in Fedora24 GNOME Builder will actually take the step from being just a fancy editor to being an actual IDE by letting you build something so beyond Fedora24 as I said initially that so far I think we've taken a fairly conservative approach to developing the workstation and I guess beyond Fedora24 we'll try to make some bolder steps the ones we outlined here we'll talk about them some more in the next slides what about the containerized bits or not alright so this one I'm going to talk about I know this is controversial and I love these days I kind of love embracing the controversy so third party software you've heard Denise earlier talking about different methods of proffering software through the distribution so the ability to have a workstation or a product that's going to be made up of containers one of the things that we're interested in in the workstation group is how are we going to open up to those types of formats some of the problems that we have distributing software can go away through other development that we've had so for example the ability for GNOME software to pull in metadata for search results without actually putting anything on your system that you may not be philosophically in line with so for example we know for fact that so you saw earlier 80% of the downloads that Fedora gives out nowadays are taken up by workstation we also know thanks to some mass polling in just general social media that about 50% of our users install Google Chrome right it's not there's no debate over this we know that about half of our users pull Google Chrome so they're comfortable with that and we understand that we have a particular free software alignment in Fedora that is not necessarily the same as our users and that the time has come where we need to stop trying to restrict their choice and instead give them the freedom to choose what it is they want and stop getting in their way so we're working with Richard and with Fesco and the council and other groups to come up with a way that third party software can work in a workstation while still giving people a way to understand what it is they're getting and make the informed choice of whether they want it so for example a Chrome user would easily be able to find Chrome and install it at the same time someone who does not want anything that's not completely free and open source would be able to avoid it just as easily as possible so if they see Chrome's there there may be other things available that hey here's something else that might suit your needs just as well yeah Matthew I was going to emphasize that if someone goes to Google software center it could say non free and then it could also have free software offerings right next to it it gives us the ability to connect users and since I have the mic so the point being that if people go to Google.com to pick up Chrome they get no message other than downloading Chrome whereas with software and of course this all has to be designed out and so forth I don't want to put the cart too far ahead of the horse but we have at least the potential to give them an indication of the fact that they're getting something non free and there might be alternatives available that might work for you but go ahead and get what you like so there are ways to show that I think in an elegant interface way so we have yet to get to that exact point but it is something that we will pursue so that discussion will happen maybe just a small addition there we already show web applications some web applications in Chrome software and as part of this effort we also make those more clearly so you really get the information to know what you're getting into when you install this thing I should also make the point third party software does not mean closed software exclusively third party software could also be software that's available in a coper repository here's another example one of the advances that we've made here is for OpenH 264 which is actually free open source software but it's available under a specific license that makes it difficult for us to offer but a vendor can offer it however we want to make sure that our users have trust with that software and so one of the ways we can help is by basically building it and signing it with Fedora's key and then the vendor will be able to offer it and of course when a person installs their system they want to be able to get to that and this way we can actually provide metadata to that codec when it's needed so that's gone through quite a long phase of sort of discussion and figuring out how we can make that work there's tickets and discussion that I'll be happy to point people to if they're interested after the talk so we're talking about the developer workstation so we actually also want to do something for developers and since containers are all the rage you could easily see it by looking at the schedule here we want to obviously support and improve our support for container development one aspect of this is that I mentioned our own XTG app there's some application containers and we'll support building those in a nice way and build them obviously but we also want to support and include tooling for other container technologies like Docker, comic and so on but I think nobody even on our working group is actually really an expert or is working in these technologies they're in the yard so we'd be happy for some feedback and for some suggestions from the field like what are the things that we should do or could do to make your life easier when working with containers on the workstation so I'd encourage you to let us know what changes would be helpful for this so this one bigger topic image based installation if you went to Colin Waters presentation on Friday you've seen some very powerful examples of what you can do when you combine OS 3 and RPMs I think this boundary between image based and package based technologies is kind of like the hottest area where you'll see the most interesting developments regarding to containers and in the future and of course we want to get in on this and benefit from it as the workstation we don't want to be left behind it's irrelevant I think Matthew had some words towards that as well he said atomic is the OS of the future so we want to be part of that and with that in mind we set ourselves the goal to have as an option an image based installation for the workstation and for Fedora 25 we hope to get out of this the same things that atomic claims and advantages for their image based installation basically we'll get a installable image that you can download and you'll avoid all of the problems and issues that can come from combining an unknown set of unknown package versions on the client system and hopefully have a much more stable and robust overall system for people to use and it will be easier to roll back something that RPM was never good at and OS 3 is supposedly really good at how big is the image and how big are the updates if you know anything about OS 3 the image will probably if you download it for the first time be pretty much the same size as your ISO is now it's the same content just shipped in a different form and for updates OS 3 works very similar to get just the delta of whatever changed in very smart ways you can actually maybe make updates a lot more efficient this way as well what else did I want to say here I was going to note that the write up is labeled atomic workstation but I want to be really clear that that is not going to be the name that we will have like eventually I think this is actually just going to be the workstation so this is just a way for us to refer to it as different than what we should have atomic workstation is basically the code name here for the project of defining what we want here there is a fairly detailed write up that you can go to and I wanted to stress that of course this is a fairly ambitious goal I think to reach 525 and of course we cannot make this as an all or nothing jump so traditional installs will obviously still be available and also we are hoping to enable what our PM OS 3 offers in so called layered package installation so even if you have an image based install and you need this one other package that is in the image you should be able to install that locally our PM OS 3 has pretty smart ways to do that it basically recomposes another image locally that includes this extra PM and supports that in a nice way alright just some other collaboration that is going to be going on in the workstation over this year you've probably heard Fedor Hubs mentioned in Matt's talk and hopefully you've heard about it if you've been around Fedor for a while this sort of juicing up of our ability to bring together applications and services in one place so that contributors have an easier way of working together also a way that presents the work that our communities are doing in a way that's more pleasant and it makes it easier for new people to get involved which has always been difficult this is an idea that's been kicking around at Fedor for years I think since the time I was FPL and I was talking with Luke Macken and he was sort of just drawing things on a piece of paper with him so we're really hoping that this is it really is time for this to happen now that we have great technologies like the messaging bus the Fed message bus that allows our apps and services to talk to each other also the developer portal I don't know if Peter Khracek is here but his team actually works on the Fedor developer portal we want to have a closer relationship with them so that when you install the workstation if you are a software developer that there is a fluid way for you to get up to date information and resources and the things that you need to get started and a lot of these developers are going to be experienced folks and they may not need those resources they know where to go upstream for their API documentation and things like that but we also know that a lot of developers coming in are going to be new right students are one of the subgroups that we look at for software developers and so giving them an easy way to find upstream documentation, giving them an easy way to find some tips and things that they need to get started is something that we hope to engage the developer portal folks with so the tie in between hubs and portal and between both of those and the workstation is going to be important going forward alright it's a challenge for me too, so challenges and you heard me mention this earlier I talked about the open H264 initiative to actually provide a specific kind of codec for folks but the biggest thing that we hear regardless of what form you go to regardless of where you are looking Facebook, Twitter, Google Plus, Ask Fedora any of the places where people try Fedora and then look for help by far the biggest difficulty and the biggest hurdle that people face is codecs and so this is again this is one of the reasons that in the workstation we are going to be looking to make that installation easier for people so that they can get the things that they want now in some way right the web browser vendors are kind of starting to make this easier for us especially when you think about an example like Google Chrome where basically you're getting all the support you're doing work there as opposed to bringing down random content and then using native applications to do it it may be that that essentially is a problem that's going to be solved for us but a lot of people still want to manage content on their own it's one of the drawing points for getting a Linux distribution at all and so we want to make sure that they are not inconvenienced further than other folks to be able to get the things that they need cohesive tools and this is important too right now I think Anome Builder is one of the best you know one of the best things out there to address this right we've had a we have a long history of there being lots of different tools to work on software and a lot of developers do prize that and we're not looking to take that away of course because we are looking for people to be able to install other packages on top of an atomic technology workstation instead of cohesive tools that actually feel like your operating system was sort of created as a thing and tested as a thing as one user experience is important so having more cohesive tools is something that we're trying to do and hardware experience so the point I wanted to make here is that for a long time people have been looking for something like a hardware compatibility list as you guys know that's an easy problem when you are say an Apple and you have to control sort of the end-to-end experience from the manufacturing all the way to the delivery of hardware and software we are dealing with and you know Josh Boyer who's up here in the front row from the Fedora Kernel team knows firsthand that we have to deal with a wide variety of hardware and it's basically an impossible job to try and be perfect everywhere but one of the things that we might be able to do is find a new vendor one or two vendors and find out if there's a way that we can ensure that Fedora is a first class experience on those hardware lines so that's something that we've looked into a bit already and we may be kicking that up a bit in the next year to see if we can find a vendor that actually gives that experience that we want that being said right now I'd say Fedora probably the best it's ever been at working everywhere reasonably well or better so hopefully that helps quite a bit in this area and finally getting involved so if you're interested in Workstation we do have an IRC channel there's a mailing list of course it's the list that we've used forever for desktop development in Fedora and finally you know again I can't be overstated that we get so much support from the folks in the GNOME project if people are interested in the technology that is going into a lot of these tools that we're using really the best place to get involved is upstream right and that benefits not just Fedora it benefits other downstreams as well so hopefully these are good ways to sort of crack that nut and I think with that that's the end and we can take some questions do we have any time for questions I've been it's beautiful yes Langdon so the question was is there is there any plan for users to be able to add in GNOME software metadata of their own well that's I mean that's a question for Richard probably he happens to be here so can I put you on the spot Richard I would say we're currently working on adding review functionality right so that you can like review software and send reviews maybe there's a way where we can collect this kind of stuff as well yeah so if it's a keyword that you're kind of searching for something that is an obvious keyword it makes sense to add it upstream and the question would be how do you find upstream so if you file a red hat Fedora bug hopefully the package maintainer would then forward it upstream and put it in the right place sometimes the application metadata is packaged in the SRPM rather than upstream in which case the packageer can just fix it for you we're also adding a reviews feature Fedora 24 so if you hopefully maybe we control some of that data for search results as well which is more user provided I'd say always try and contact upstream if possible and just a note so since I have an upstream and a package in Fedora I know for a fact that Richard actually sent out emails to let packages know that what they need to do to add that metadata so they are aware of it for sure at this point I think it's a start big time alright anybody else yes sir good question so the question is how would an atomic based workstation affect other spins actually probably very little because I don't foresee that this replaces current methods for putting together the operating system it would be additive now while in workstation if this works out I think that this is the way that we would like to go in the future it wouldn't prevent any other spins or other labs or any other piece of distribution from keeping the same legacy way of putting together a group of RPMs into an install image so it's additive and not exclusive I agree yes so hang on I'll come down and get the answer but the question was the automatic backlight features is something that was implemented in Kernel and here's our Kernel guy so there's two different parts there's a device driver for the actual ambient light sensor that is done in Kernel but then you actually need a user space to set policy right because we refuse to set policy in Kernel because what you find comfortable to view in bright or light or dark situations I probably don't so we need the Kernel driver and there are some the problem is like every other device on the planet there's multiple devices for that class of hardware right so there's tons of drivers and making sure they get loaded and then we need the GNOME stack to interface with those and set policy according to what you have selected I think that's all we have time for so thank you guys for coming and please stay tuned to the workstation it's going to be awesome