 Alright, so I'm JP, JPR, from the OpenSUSE and GNOME project, and gonna talk to you a little bit today about OpenSUSE and GNOME. So, first question a lot of people comes to people's minds is, is GNOME really important to OpenSUSE? OpenSUSE has traditionally been a KDE desktop, that's where people can be KDE distribution. I think there's a couple of important facts. One is that GNOME makes up quite a quarter of OpenSUSE users, about one-third install GNOME as part of a dual install. And when you add that up, that's hundreds of thousands of users that are installing GNOME and OpenSUSE. I also think that GNOME for OpenSUSE is an area for growth inside the traditional user base for OpenSUSE. It's somewhere that Ubuntu users can seek refuge from or that kind of thing. I think it's also important, Will's talk, Will and Dirk's talk is before I talked a lot about how KDE, we have a lot of KDE, we're the biggest KDE contributors upstream. We also make a lot of upstream contributions in GNOME. And because of this, we're probably the only distribution with significant upstream contribution and user bases in both major desktops. I don't think Ubuntu has this, but Ubuntu, I don't think Fedora has this. And that makes this a distro for just about anyone, especially when you include the fact that we also have WindowMaker, XFCE, all that kind of stuff. We have options for everybody. So the OpenSUSE GNOME community. So first of all, yes, you've heard right, there is an OpenSUSE GNOME community. It's sort of been around for a while. As I mentioned, we've had lots of users, but we didn't really have any sort of presence in the community in the OpenSUSE community over the first year or two of its inception. About a year ago, we created a mailing list. We had some IRC, did a little bit of vlogging, kept a very low key. There was, you know, maybe 10, 15 people would hang out on the channel. Those of us that worked on, you know, internal to Novell would hang out there and try and talk a little bit about things we could. About six months ago, after the 10.3 release, started to try and build up that community a little bit. We had some external people that we knew, and we also had some internal people from Novell. And it was at this point we started doing things like creating Wiki, trying to get more decision making done in the community, having IRC and things like that. So the people that are involved in the OpenSUSE GNOME community, what are they doing? They're doing a lot of things. Things you'd expect. We do a lot of work upstream, not as maintainers, but as, you know, just contributing, creating international cloth to our panel, working on a package kit to get the zip back in. Network, we did a whole black and network manager work, worked on GBFS, which is a new piece of the platform in GNOME 222. We're also maintaining a whole load of packages upstream. So Tom Boyd, control center, GNOME panel, GNOME session, across a whole bunch of different maintainers. We also do a lot of work to work on integration with OpenSUSE, similar to what KDE does, you don't need to create a gash to decay or people in the community have. The Jeep Reader, the thing that the first time you log in you see. We've done things that are more just desktop agnostic like Pops Auto config, so I don't know if you know now, but if you plug in a USB printer in 10.3, just about 99% of the time it will actually configure it all for you on both desktops. Things like codec downloads now, trying to make it easier to pull codecs down. Things like that, things have worked on. We've also started trying to contribute to the OpenSUSE infrastructure. We've written a number of plugins for OSC, attributed patches to OSC, which is the Build Client for Build Service, the local Build Client, and just referring to the hack week that we had, we had someone, Rodrigo Boyd, who worked on a Build Service back client, similar to the KDE one. Aside from development, the hacking is a lot of soft activity or non-development activity that we do. So it's simply bug reporting from people in the community, reviews. We have bug reviews and triaging. We'll do that. We have bug fixing weeks where we just say we're going to fix a whole bunch of bugs in this area. Packaging days. We do this project-wide, so KDE people, the GNOME people, a whole bunch of people contribute to this. We help people figure out what they can package, how to package, how to get things into the Build Service, how to contribute. Upstream patch reviews. We take a lot of our patches that we do, changes, bug fixes, try and push them back upstream properly so they get integrated in the next releases upstream to contribute it back. We have a number of repositories like GNOME Community, GNOME Stable, we have Unstable, where we can try and push the new versions of GNOME Unstable and the stable and unstable versions of GNOME for older distributions so you don't need to try the new ones without having to upgrade your kernel and all the worries that that brings. And then simply support in the community. So people answering questions, trying to help people out. So in six months, we sort of got into this spot where we have a number of contributors, both internal to Novel and external to Novel, which is good. We've built an IRC channel that we probably get somewhere between 50 and 60 people, which is great. We have a mailing list, we have a usable Wiki now that we can read and find information. So a lot of this stuff. So we've sort of built the basic infrastructure now. We took care of a lot of bugs in 10.3 that didn't get a lot of attention before the release. We have been working on 11.0. And we have a few next goals that we want to get to. We want to keep pushing more decisions into the community. Right now still sometimes get things decided internally by Novel people. It's not quite the right way to do it. We want to push even more out so that people can contribute and give their comments and see where we're going and also help out themselves. And we really want to build that next to our community. So a look at community building is sort of like you want to build a core, core contributors, usually some developers. You put another group around them, which is sort of what we've got now. You know, the first level people that talked to the developers directly and have helped out building up the community. And on top of that, you just want to keep layering more and more people and grow it over time. And there's a few sort of easier ways for people to get involved. Things like support. People can simply answer questions on mailing lists and stuff. That frees up time for more development or feature improvement by others. Translations is a big one. In terms of translations, we probably need a system known as SUSE to do translations, upstreaming them a bit better, enable the community to be able to submit them via the web, things like that. And then just packaging. When you look at something like Ubuntu's packaging ecosystem, that's something that you really want to replicate with Disgro. You want lots of packages everywhere. Everything that anybody can think of. And we have a really great tool for this in the Build Service. It's a really, really excellent tool that doesn't just do for open SUSE, but does it for all distributions. And you want to take that and move it forward. And for the open SUSE Economic Community, I think we'd like to move more, doing more contributions, engagements, project-wide. So I talked about the translations as one. I mentioned packaging. We're involved in the community packaging day, that are all-wide. And of course, the ever-popular FOSDAF activity. So how do we get there? That's sort of a goal, that's a high-level goal. But where do we want to go with that? So, Build Service Availability. Going forward, Hulu talked about it in his talk yesterday about community repositories. We're making them options to be enabled as default, or we're going to want to expand our package sets that way. So, GNOME on stable GNOME stable are there. They're not as updated as frequently as we'd like right now. So we'd like to make sure they're more up-to-date, make sure they're building on more older distributions, make them a lot more usable for people, make sure the migration path works so that we install GNOME stable and update to 11.0. You know, you don't have a lot of problems, things like that. And also we want to grow the GNOME community piece. So, I mean, this is really, the GNOME on stable, the GNOME stable are really the core packages, the packages that ship on the core of the Suze distro. But there's a whole load of packages out there that people want access to that aren't appropriate for the core distro, or for space considerations, you don't want to fit in, or whatever. So, I'd really like to grow the GNOME community repository. The guy who maintains it for us right now was Rick Walter, James Oakley, who also is the planet Suze maintainer. So, he's been taking lead in trying to get packages reviewed in there and making sure they meet standards, things like that. I mentioned earlier about the translations. I know that Fedora people, for instance, want to talk to us about the trans effects, the Debian's using that. I don't know if that's the right solution, but somehow it'd be nice to enable people to give us translations, but not trample on upstream. A little background of that. So, one of the messy things about translations, like use something like Rosetta from Ubuntu, there's no real way to get those translations upstream without trampling all translations upstream. There's no sort of way to review them, have the upstream review them, and take them in. So, it'd be nice to be able to contribute to something like that and build that up. Live CD decisions. The presentation before, Dirk kind of got cut off, but he saw that you saw some of the twisting and stuff that people have to do to get these live CDs because you have to try to find a balance between what people want installed by default and what you can actually fit on a CD. So, there's a couple of people in the community who are starting to look at what we can put in the live CD and what decisions we can make there to what to cut. And we really love feedback from this because we can sort of guess what applications we use, but we can't really guess what everybody's using. One decision that was talked about recently was, and I know the KDE team dropped this, but we're thinking of dropping it too, which is the GIMP by default. People use the GIMP, but how much do they use an advent of photo apps and everything, EOG, F-spot, that kind of thing? A lot of people are just using that now. So that's the kind of decision we need community feedback on to figure out if that's the right way to go or not. More direct testing, responsibility. It would be great if we could form specific hit squads or bug hit squads, like these are the guys that are going to test laptops and just pound the heck out of this for a long time, or these are the guys that are going to test accessibility. For instance, we have a couple guys that are really involved in accessibility right now. You know, build-to-grade integration. Upstream and GNOME, there's something called the Build Brigade that, I don't know if he's not here, but Rodrigo is involved in, Rodrigo Moya. They build packages for a couple different distros, but they have problems because they need separate machines for each thing, but we have a really great thing here, so we should be able to do this way and create CVS snapshot builds of all, up GNOME for all these various platforms and drive people to the build service in OpenSUSE. And then just, you know, Google Summer of Code every year. You know, we got one of the, one of the best contributors I think we have externally is the guy named Ricardo Cruz who came in through this program. He started working, who did the HGTK, is this Google Summer of Code project. And what's he working on now, Michael? Looking for open office? He's actually still a standing contributor to YAST, he's still developing for YAST right now in the community. So how can you contribute? So you saw a whole load of things in the previous slide that nobody can work on. It's important to note, I think, that no contribution you can do is too big or too small. You know, I just put a sample of various people that we have in the community. And everything, every little thing that's done is something somebody else doesn't have to do and gives an opportunity for somebody to do something new and exciting in the distro or integration or feature or something. So like Captain Magnus writes, just writes our meeting agendas on the wiki and we have a guy who prepares the meeting transcripts afterwards and we have Ivan Z, who's actually a mono contributor upstream but he comes to our bug weeks and just goes, hey, I'm gonna fix three or four bugs. I'm a student. This PSP250 guy who's been using SUSE for like 10 years or something and he just came, showed up on our bug day and started triaging bugs for us to review them. This guy, I don't even really know who he is, but if you have anything to do with open SUSE bugs, you've probably seen him reporting bugs. The man runs factory constantly and just reports bug after bug after bug after bug. You know, Sidor, who's also out there who's sort of a copies XGL fusion expert guy and also involved in the LTP LTSP packaging for open SUSE and helped us package false audio. Ma, who's back there, is our king packaging dude. Federico, Minnet, Katero, bug days on and on and on and whatever you can think of here to improve your distros, something you want to hear about. So how do we communicate? I mentioned earlier about the Wiki, the mailing list, the IFC so the Wiki is here that's the lead-in to all things GNOME and open SUSE. A lot of information there about packaging, repositories, meetings, bug days, all that kind of stuff. We have a mailing list here open SUSE GNOME, not open SUSE. Sorry should be open SUSE.org you can find it on the mailing list page. IRC, we're in this channel open SUSE GNOME on IRC we have weekly meetings although occasionally we skip one like we skip one for hack week and we skip one for pause time this week. But we also have included in that we have theme meetings so we like to invite people from other teams to come in and talk about their area of expertise and how it relates to the desktop. So we've done this with a number of things like Bluetooth, Steph and Cypher came and talked about that, we're networking, we had Tambadingo who's our big contributor to network manager upstream going to talk about that and Helmut Shaw who works on K Network Manager things like that. So that's sort of an overview of the community going to talk a little bit about the features and stuff that are coming in open SUSE 11 from GNOME First big thing is sort of the user love aspect which you get to see end user visible at the end there's a really cool synchronization tool called conduit it's maintained by a guy named John Stauer upstream there's a lot of cool stuff we'll have a lot later but it synchronizes basically sort of abstracts everything and it can sync to or from a whole bunch of things it's got back ends for open sync so when the open sync device has an avahi so you can sync between two machines on a local network it will sync from anything local but it will also sync to the web so it can do things like sync your evolution calendar to google calendar it can sync your f-spot photos to picasa, facebook and smug mug or whatever that one is Phenograo it's a really nice vnc tool it's able to use heavily for qa and testers G's which is funky penguins, true love and it's cross to bear trying to get webcam grabbers to work it's just a cool little photo photo booth type app the international clock so that was in open susay 10.3 but that was a nice sort of upstream success story so we wrote the international clock originally for sled 10 sp1 but a year ago but a lot of other distros really liked it so i think butu took it and also red hat took it and they expanded it and they added a bunch of things and we merged it all back together upstream for genome 222 it has a couple cool attributes too it has policy kit integration so we'll talk about in a little bit the weather integration and stuff now that was in in 10.3 it's also the only clock upstream now so it's the default for everybody we've been a lot of bluetooth improvements all over the stack from the lowest points in the stack to the bluesy stuff all the way up the stack to the applets and things like you know phone manager one kind of cool thing now is you really don't need the yaks module anymore to do bluetooth in fact i think they're going to drop it for everything except the server they're going to keep it for any customers but so it's pretty nice that's what they've done is they de-buss enabled the underlined demon and so you can tweak it all from your user output and it just changes everything for you on the fly we have a big vehicle update so we shipped the 2.0 series in 10.3 we're shipping the 0.3 series in open suze 11 it's got a lot of nice memory improvements, new back ends they rewrote the thunderbird back end so that it isn't a memory thing like that evolution there's a few nice usability enhancements in evolution, there's also been a bunch of memory reduction in evolution, the biggest usability enhancement is probably the they got rid of the intrusive error dialogues now so they just you don't get a bunch of error dialogues popping up when you have network errors things like that avahi, although avahi is not something specifically user visible so what we're seeing now is a lot of integration with avahi in various applications so I mentioned Vanagre before which you can actually find VNC server, Vino which is the remote desktop sharing thing in Ganon actually we'll advertise over avahi now and you can find VNC components over through avahi the conduit I mentioned earlier will find other machines to sync to so you can sync say your home directory or your gconf settings and it will find them peer to peer over the network a whole lot of other stuff Daniel Gala did a talk yesterday actually on all the various integration points for avahi oh it's today so come see his talk today and then later we'll show you many many things actually Beagle has a new feature now too where it can search for other machines on the local network finding avahi all kinds of stuff like that accessibility integration so I've talked about this at the time but it kind of sucked but we really didn't know a lot of us don't really know how accessibility works or how people use it and we shipped it and it was kind of broken in a couple of spots but these two guys thankfully came to the rescue and joined the community Susie Rocks and Dara who are big users of that technology and he'll keep us honest there we shipped a bunch of fixes there but there's a bunch of new a lot of accessibility work going on upstream and you can actually hear some more about it in Michael Meeks' talk in an hour or two about all the accessibility that's going on work that's going on platform-wise there's a few changes we made very low level change with GBFS which NOVFS was the virtual file system layer that we used in Nautilus and a lot of apps used to get remote streams so GBFS is replacing this Hans Petter who's back there can answer all your questions about this they worked on it upstream but basically it's much lower on the stack now it has a very nice fused integration now so whenever you mount anything with modelists or whatever it will get exported as a fused share as well which solves a lot of problems things like third-party things and AcroRead or things like that that really didn't speak NOVFS we'll just be able to grab it from a local directory now no problem if you're those who don't know what fuses fuses are files files for users files for the file systems that users use and basically gives you a POSIX system so it's just as simple it looks like a regular file system that users use a policy kit and console kit so this is kind of an interesting one so both of these actually shipped in 10.3 but they're not really used anywhere or very rarely, I think they're used for a couple of things like mounting it's not really exposed anywhere but policy kit actually will get us to what some people think of as rootless admin or if it's useful for that kind of thing and what it is is actually it's a more granular permission system for things that you do on your system so for instance for mounting now mounting is always for a while now in OpenSUSE you take a USB stick you plug it in and that'll work if you have any internal partitions that aren't mounted at boot time you can't mount them right or you have to become root in order to mount them it breaks down those two options and allows you to set up a bunch of permissions saying that I'm JPR, I can mount internal drives without any without root the reason this is cool is because you can just ship a bunch of default policies one of the pushbacks in this model has always been the server guys always get worried about well if you destroy a root what are we going to do but this you just ship different configuration files server guys can keep their can keep their root prompt and for regular end users we can really start to give them more granular permissions like you can give users permissions to add local printers and to install packages from trusted repos if we use something like package kit but not install packages from untrusted repos or install or mount external or internal partitions the other part of this here is console kit which solves another somewhat related problem which is user sharing in the same machine what happens right now is when you have something like you go to mount something there's basically a race condition because you plug in the key and if you've got two users on there whoever gets to it first gets to mount the USB key what console kit does is it adds the concept of active session it uses works of acts to figure out what the active session is and it can then you can do things like only let the active session mount the USB key or if you do things like switch between users and one user is playing say music in Banshee or something and you switch to the other user it can take away the permissions to the audio device from the other user because it knows it's no longer the active session and give it to the new user there's a bunch of accessibility work as I mentioned earlier hopefully I can demo this one because this one's a little easier to understand as you see it and GDM which is actually a discussion point for us so they did a lot of work on GDM actually to integrate with the policy kit and console kit and a lot of this stuff the new GDM is not going to be shipped in good old 222 but we still may ship it anyways and it's going to be ahead of 11 11-1 and probably SLEE-11 so what else, that's drag integration so we shipped the ASCII K by default on GNOME for the first time in 10.3 it went over reasonably well except for the package selector people were really disappointed about the package selector and that it was much weaker in functionality than the QT one so Ricardo Cruz who I mentioned earlier has actually done a bunch of work and you can do things like taboo packages and stuff now in the ASCII K hopefully that addresses one of the big issues Gbreeder will probably do some small improvements there Compi's Fusing Configuration still seems a little too hard to me we also want to think about whether or not we want to turn this on by default that's another thing we'd like community feedback on turn it on by default if your hardware supports it so we want to make this a couple pieces of this so there's two main parts of configuring Compi's Fusion one is once you've got a run-in configuring the plug-ins and whatever the opacity and you probably want two interfaces the very simple one and the very complicated one for people who want to really care about like spring constants and the wobbly windows things like that and then the first half is the one that's really the weaker part setting up the hardware you know GNOME XGL setting or enabled disabled kind of does this but it's not very good it's not very user friendly it's not across it's kind of no specific some of it so none of that's good so we'd like to clean that up and the other thing we're working on we'll probably blog about it is a package kit so package kit is a project started by this guy Richard Hughes who actually just got hired by Red Hat but basically what it is is an update or a package management system agnostic package manager so what you do is write plug-ins for each of the specific ones like young or smart or whatever and then package kit has a UI up for it right now the main UI it has a command line tool there's a GNOME UI there is a Q package kit as well but it's not nearly as well maintained right now so no package kit so what we did was we wrote a zip back end for this and we've been working with Duncan McVicker Pretz team who's the head of the ASC team and one of the students that he has student's name Stefan Haas yeah Stefan Haas and Scott there has been working on it too the idea being here is I think we can do some really neat integration stuff it's not let me caution you it's not the whole ZMD versus zip thing that was in 10.1 or 10.2 because package kit uses zip so it's all the tools that are mixed so it's just like using zipper versus end versus the ASC package manager it's just one more interface I don't know if Duncan is demoing this while we're here but you can ask him for a demo it's pretty nice it works really nice with the new SAT solver the SAT solver interface which is lightning fast if anybody use zipper you know the refresh speeds and the repos and stuff but the new stuff is let me put it this way I went to refresh my repos I had to run it five times because I didn't believe it was actually refreshing my repos there's a whole bunch of stuff it's not really KDE so I called up the desktop smorgasbord interestingly the spell checker in an open office found us and put in the oombots and everything for it so I clicked on it so Compi's XGL I mentioned there's a whole load of improvements coming there it's getting XRander 1.2 support it's got tons of new plug-ins you can see it on the demos of the suze booth downstairs for both KDE and GNOME XRander 0.7 which is already in the alphas of what I know some couple key things here there's some new howl enhancements that allows it to auto-attack UMTS cards and it supports going to be supporting UMTS cards in the next month or two so this means all the broadband cards you can get in Europe and stuff you'll be able to get network anywhere PPP support is part of that wired 802.11x support which is a lot of people so it has profile information so you can do things like actually have wired and DHCP wired connections and have them differently depending where you are Firefox 3 I hadn't realized that we'd made this decision I proposed it originally or Wolfgang Rosenauer did on the list and Kulo seemed to have made it officially yesterday in his presentation without telling me but we're going to ship this this has a lot of nice accessibility improvements it's got offline API support all kinds of things like that we'll ship OpenOffice 2.4 as well we have a large OpenOffice team at Nobel that does things like make that fancy transition if you saw the little Prashan thing that I showed off and a whole bunch more stuff you know general release notes hundreds of bug fixes dozens of scores and new features and we just have for ourselves we have a few ideas so questions I think I'm down to like 8 minutes or something any questions so far very complete apparently good so demo let me see if I have time to show a few of the things so I mentioned policy kit so I need to run this this is the new one there's a slightly different command on 10.3 what we have here is a list of basically services that are exposed over D-Bus so you can see things like here mount fixed drives policy kit itself you're allowed to set up who can read remote and grant rights for the new clock applet you can set the time zone this way so you can check if you have permissions or not and even actually for the new pulse audio stuff you can get real time access to the pulse audio device if you're given the question on the clock applet that seems backwards to me why isn't that like all creator stockpile system clock set type is that does the name of the dimension relate to the tool which is doing the configuring or does the name of the why isn't that named after the system clock is that what the clock is what that is setting because this is actually the thing that does the setting here is actually comes from no panel okay so that's how the tools it's a healthy tool basically the way it works is you make a D-Bus call and the D-Bus call gets authenticated with policy kit and then it calls through and activates whatever's underneath it would be nice if we could make some of that tool so that we're only maintaining one because we want to do the same thing okay so that would be a good your website could be a free desktop spec or something if you wanted I don't think it's how in this case you can go on here so this is just a sample app that's here but basically what you can do is you can go up here to the prom Decade and it will let you I'm authenticating as myself you can note but this can give me a root privilege of access to run something as a root command underneath this is all controlled by just a simple XML file with sort of matching and you can say who can get this or groups can get such and such or you can keep you can ask the person's password like the Mac does when you do administrative functions and it maps one user on to an administrator you can have it keep passwords for sessions or for all time one of the ways we're using this now is you go over here you can set the time zone now so when you move between cities now you just go and set it it will ask you one time for authentication and then you're done with what I mentioned is the syncing tool so I set up a simple one right here so tomboy nodes you can make this a two way sync you can do whatever you want and all you have to do is say sync a nice group and it will send my tomboy nodes into evolution memos you can see here all the types of data sources that it has so one interesting thing to do is something like using fspot a pane you want to send your things to post but if you also want to send them to the casa and to flicker as well you can set up something like that you can pick a tag in fspot and it will ship everything over to these three and keep the sync for you I mentioned earlier so the network thing so you can set up actually a network so you can say I want to put these actually here's a good one gcomp settings across to the network you can see right here this is a conduit exposing a service over a vahee you can pick this up on another machine and keep your gcomp settings the same for your files or whatever you want but also did I mention oh the connection editor so we have this guy I don't want the latest ui on this one that's a little better what you can do is things like here you can now set the ns servers manually set your IP addresses all things you couldn't do in the older network managers there's another dialogue for doing the u mts cards things like that part of the work actually in network manager 207 although you can't do it from the ui yet was to allow more than one interface to be out so that's kind of nice for people who really need more complicated things it also leads the way to be able to do connection sharing I'm turning on time Is there any questions you can answer? Yes With the conduit things are if I was to just write about developers able to conduit site versions tasking release them into service evolution tasks yeah it's pretty straightforward the codes are managed pretty well upstream it's all in Python so it's a Python module and you can just basically define you basically subclass something right and implement a bunch of methods and you have syncs and sources so like you can you just pipe something you can say I can accept these types of data and you can map types of data and it'll figure out that you know you can map files to photos and put them on Flickr things like that so Does that answer your question? Yeah Any other questions? I'll be out at the open Tuesday booth so if anyone wants to see more of the demo I have more stuff to demo but I'm running out of time so cool alright thanks for watching