 Beth ydych chi'n gwybod llawer o'r ddweud yma o'r rhagor. Rydw i'r hyn yn gallu Ion 3 yr ar-daw, rydw i ymddych chi'n gweithio o Fosden, ac yn gallu'n gweithio'n gweithio yn y dyfodol, gael yma'r gwirio i'r gynghwyl i'r unrhyw o'r amser mawr oherwydd mae'r ddweud o'i wneud i gael gweithio. Felly, yn gweithio'n gweithio'n gweithio o'r ddweud yma the impact that the internet has had in society. If you're used to my presentation, I use a million dollar graphics for everything that I'm doing here. The structure of society for decades has been a structure which has been hub and spoke. It's been government in the middle with the citizens out there spoke having things done to them. It's been consumers, the consumer society. I always think it's a wonderful phrase. Cifffaiddio'r fünfod ar y gwanffwyr. That has been some for the last 25 years is doing that stuff. Right at the heart of what we've been doing has been this shift to a networked society, and the Free Software Foundation has been doing the same thing. In popular culture, in developer culture, has been making sure that the ability to work is not dominated in a hub and spoke way, but is operated in a meshed way. A dyna o'r цisioedd ymddangos cyfnig y modelen me'r pryd yn rhaid gwyddoedd, iddi'r pryd yn idei'r pryd mewn ar y wold mewn. Dyna yw rhaid gyda'r eich cyfnod i ddif矹? Nid oes y gwir i chi'n amlwg fel y dyma, rhaid i chi i ei wneud i chi'n ffantisiau! Mae'r mech ysgolwydau sy'n gwybod i'w cerddwyr ymwneud. Y dyfodol y byddol i'r cyfraffwyr yn yr ymwneud, mae'r cyfwyrd yn ei wneud i'w cyffredinol i'w peirwyr, a'r byd o ddweud o'r rhywun i'w cefnodau, ac i'w ddweud o'r pwysig i'w gwirio, a'u gyrsio'n gallu'n gweithio i chi, a'n gallu i'r cyfraffwyr i'w cefnodau. Mae ydych chi'n gweithio i'w cyffredinol i'w cefnodau. Y rai os ydych chi, y beg ydych chi un pethau hpog ystod yn ymweld i ysgrif yn cyhoedd yn eu gwir. Y ffordd o'n hyn o gweithio'r bod yn ymhawr yn ymweld i'r gweithio. Y feddyl yn gwir yn ymweld i'r ddesgwyl, mae'r peol yn ei cyfan ei holleg yn rhaid yn eu tyfnig yn unig. Mae'r peol yn ei holleg yn cyfan ei holleg yn y cyfan ei holleg yn gweithio'r lleif. the socialist involves having none of the smart people working on software in a closed room, competing against all of the smart people out on the internet producing the same kind of software faster and better. And I think I knew which business I would rather be in. So why is the Sun getting into free software at the moment? Well partly it's because of our history with free software. ond it's because we believe that the way that businesses do software is changing. When I got into the computer industry rather too long ago, the way that it worked was you bought a piece of hardware and it came with all the software you could ever possibly need. It was there on a punch tape in the bottom of the shipping crate if you could find it in the huge space of the computer. So you'd buy a computer with all the software you could possibly need and go deploy it and it would all be up and running and you would have paid for it at the time that you bought the computer. Software was paid for. The work of the laborers producing the software was compensated at the time that the hardware was selected. In the 80s that all changed and people started selecting software for business use separately from the computer that they were going to deploy it on. And they would then combine that software and that hardware to produce something that worked for them. And the time they'd pay for the software was at the time they chose it. Software companies invented this idea of a commercial licence. I've never yet met anyone apart from a software manufacturer that likes selling licences or buying licences. No software user ever wanted to buy a software licence. None of us wants to buy software. What we actually want is software that solves a problem for us. And what we would really rather be paying for is for having the problem solved. And with the rise of the meshed society with the availability of free software being created in open source communities we've been able to move to software market 3.0. In software market 3.0 you're able to select the software and assemble a solution that works and go deploy it. And it's entirely up to you what you pay for when. You no longer have to pay in advance. And so the business of being a software vendor in the 21st century is a business that is about making good software and unbundling the value proposition of software for your end users. So what people used to pay for was a licence to get a black box they couldn't look inside. And they would have an implied right to have all of these great things down here. Some code, the ability to install it, some documentation, maybe as much as a page, you know. Maybe some education, maybe a warranty, maybe a bit of insurance. Thing is that most of us didn't want all those things. Most of us only wanted some of those things. Well in a world of free software in a meshed society you actually only have to worry about what you need and it's your choice what you pay for. Who you hire to do things, what you buy in from vendors to do things. And so the software business of the 21st century that Sun is moving into is this software business of being able to demonstrate value to our customers and providing them with a service that they can pay for that will get their software running, doing the things they need, get the new features added, get the bugs fixed and have them paying for just what they want to pay for. We're not doing this out of a great sense of philanthropy and love for the world. This is just what's going to happen because software companies can't charge at the time of software selection anymore because we collectively have broken that business for them forever. It's no longer possible to force people to pay for software licenses because software is liberated and software is without charge as a result of being liberated. So what could upset all this? I just want to briefly mention this. There's been two earlier talks for those of you who got up late. There was a talk right at the beginning about software patents and then we've just had Jim talking about one laptop per child. On the subject of software patents, SON is one of many US companies that file software patents regularly and the reason that we file software patents regularly is the same reason that Americans buy guns. Americans buy guns because Americans buy guns and American corporations file software patents because American software corporations file software patents. If you don't, you are toast. So really we've got no choice but to file software patents. It isn't having software patents that's the problem. It's what you do with them that's the problem. So one thing I want to point out to you that you really need to understand in addition to the talk you heard earlier is that software patents are filed in parallel with development. When people in your community work for American software corporations those corporations are incenting them to file patents every morning. They're not getting them to wait to the end of the process look for the clever stuff and file patents on it. What they're doing is they're incenting them every morning when they wake up to file a patent. They're filing in parallel with development and that means that there is a very strong chance that if you have any corporate sponsored developers in your community that they are filing software patents on the work that you are using in that community. And you must be aware of this. It is happening in your community. The software patents are there and the reason that they are a problem is not because anyone is going to come after you personally and sue you as you heard earlier. The problem that happens there is that whole communities can be threatened by a threat to key sponsors in the communities. Now what happens with software patents is they fall into the hands of parties who would like to do things with them that are not community friendly. So let's say that I as a company am busily getting on contributing to free software filing patents at the same time because that's what corporations do. The reason you have kitty litter is because of what cats do. Software corporations file software patents. I'm busily filing the patents. I'm unlikely to be harmful to you. If, should it perish the thought, some company that has been filing patents go out of business, its patents are treated as assets in the open market. And the big threat to free software is what happens when the people filing in parallel in your community pass their patents to a hostile party outside your community. And that's the reason that we heard earlier that software patents aren't going to go away to the US anytime soon. And we also heard earlier that patents as a category in Europe are here for a while. I'm doing my best as I did two years ago with Mark Webbing from Red Hat to try and stop the software patent directive in Europe. But it's like a zombie. You know, every time you look around, you find it's up out of the grave and running down to the voting booth down in the European Commission. I spend my time over here trying to kill it off, but it just keeps on coming back. So what can we do? There's three things that we can do. One of them is to accept patent grants from patent holders and hold them in common in our community. Now this is good, but really low value. The reason it's really low value is because if you look at any software patent, software patents don't contain any useful information to developers. Software patents are designed to help lawyers know how to sue other companies when they infringe the patent. So a software patent is a list of things that by which you can know that someone is worth suing. There's no code samples in there. The flow diagrams are lame. The languages are cane. The patents are worthless. Trust me, I've read lots of them. So patent grants are great and I'm really grateful for the companies that have protected things like SAMBA with patent grants, but it's insufficient. What we actually need are two things. We need new software licenses like the GPL v3 that have strong language to handle patents in them. And we need to have a new approach to software standards that makes sure that if you implement a software standard like MP3 it's impossible for any party to prosecute a patent claim against that international standard. Those are the two things that we need to do. I'd encourage you in your hatred for software patents which I share with you to drive it into a positive treatment of software patents. Try and prevent applicability of patents in key areas. That's my advertisement for the day. Now back to a quiz for you. Here's a quiz. If you were to look at the source code in the Debian source code repository which company do you think you would find had written code in the Debian source code repository? Any ideas? Is it IBM? Is it Red Hat? Is it SCO? Well, as it turns out, SCO is number five on the list. It turns out that Sun is actually the majority corporate contributor to the software that's in the Debian repository. And Sun has contributed three times as much code as IBM and five times as much as Red Hat. This is from a recent European commission survey. And so the question remains why do you hate us? Just to give you some examples of what that code is. This isn't stuff that you don't want to use. This is stuff you're using every day. This is the accessibility framework in GNOME. This is Orca. This is the on-screen keyboard. This is the framework that IBM has then re-implemented as iAccessible 2 on Windows. This is the internationalisation code in Mozilla. This is openoffice.org. It's actually stuff... All the people who wrote openoffice worked for Sun. Trust me, I went and met them in Hamburg this week. So it strikes me that what's been going on for many years is there's been two ribbons of free software. There's been a ribbon of free software that has been going on in the commercial world and there's been a ribbon of free software that's been going on in the collective world that is represented here at Fozden. And so I'd encourage you to look beneath competitive behaviours at the actual behaviours of developers. I've got a bunch of developers that have come to Fozden this time to tell you about what they're working on like OpenJDK. I encourage you to go meet them and discover that whatever the competitive postures and the stupid messages executives give out actually there's real developers contributing real code and there are people who have already changed your life. Now, just to seal the two ribbons that are coming up, I'm announcing now that Sun has become a patron of the free software foundation. I think it's time for us to begin to tie off the ribbons of hostility between the old BSD worlds and the old GPO worlds and begin to realise that we have a great deal to gain by being united and working together. And I think that's the message that lies behind the OpenJDK. So let me show you a video here about Java. The word is free software license. The special thing about this license is that it's a copy left license. That is to say all versions of the program must carry the same license. So the freedoms that the GNUGPL gives to the users must reach all the users of the program. And that's the purpose for which I wrote it. It will be very good that the Java trap won't exist anymore. It will be a thing of the past. That kind of problem can still exist in other areas but it won't exist for Java anymore. I think Sun has well with this contribution have contributed more than any other company to the free software community in the form of software. And it shows leadership. It's an example I hope others will find. I want you to get the idea here that something big has changed. I couldn't imagine going to Richard's office three years ago and asking him to record a video where he said that the Java trap no longer existed and that Sun was a company that he encouraged other companies to emulate. If you could imagine that blew my mind completely to make that video. But something big is going on here. We're seeing a shift in society that is making it correct for software businesses to start doing free software the way that free software will be done. That's the change that's happening. So now to zoom in on Java for you. Java as a technology, as a community has been around for over a decade now. When Java was introduced it was licensed in a revolutionary way that meant that businesses all over the world started to embrace it almost immediately. It wasn't licensed using a philosophy that was compatible with free software. But it was made available on the release day with the full source code. I at the time worked for IBM rather than for Sun and in Hursley we picked up all of the source code to Java and we ported it to AIX and to OS2 by July of 1995 because all the source code was there. We didn't ask anyone's permission we just went and did it. Many many groups all over the world did that and proved to corporate observers that keeping the source code secret wasn't necessarily a competitive advantage. That experience I believe was the seed that then allowed Mozilla to break through and become a commercial commercially visible free software entity. We did that in 1995 and it succeeded far beyond Sun's expectations. Sun was just completely overwhelmed with demand. When you're a pioneer you often don't look over your shoulder to see what's behind you. You just keep on looking forward and trying to duck the arrows. If we'd looked over our shoulder a few times we might have realised that there was a free software constituency that we really ought to have been working with. It was done and it's taken a really long time to get to the place where we've realised we need to fix it. But we've realised that we need to fix it. There is a rich ecosystem already for Java that includes both commercial activities includes free software activities includes community activities and it's time to bring the ribbons together on Java as well. So last November I think it was we said that we were going to GPL Java. Now to give you an idea of what GPL in Java means in software terms just the Java SE the Java platform that gives you a programming environment that's the same on every platform just that code is around about 6 million lines of code. That's before you've accounted for everything else. It's a great big piece of code and it's taking some time for Mark Reinhold down here in the front row to see what's being done. And so what we did was we started out by just releasing the Java SE compiler and the hotspot virtual machine. I was very thrilled when that was released to immediately see people like Mark Villard down here and Dalibor Topic wherever he is and up there and Tom Tromey picking this stuff up and compiling it and trying to break it and trying to use it to test GCJ and doing creative things with it. That immediately started happening. So Java SE and hotspot are out already. We've also taken the full Java mobile and embedded platform and released that under the GPL under the name mobile and embedded and that's already out that's already very active that's already been ported to a number of new places and there's an interesting free software community growing around it. We're going to carry on with these code releases over the next few months in the spring I think that's about as precise as I dare be is in the spring they will have finished moving all the code over into a public repository and it will be made available under the GPL with the class path exception so that people can work on that public code base. The reason we're not just releasing it all at once is actually we're continuing to do business with this code. We continue to have business contracts and we're moving it from a closed repository inside some that's using something that actually predates Bitkeeper written by the same guy called Teamware and we're getting it out of there and into a public repository called Mercurial and we want to make sure that we can carry on fulfilling our commitments to our customers during that transition period so it's taking us a number of months to do it but Mark is definitely going to get it done by the spring, aren't you Mark? Yeah. We seem very confident down here so this is the timeline that we're on. We anticipate having a full buildable Java SE JDK JDK 7 down here somewhere in the spring and I'll leave you to work out where that line might actually be pointing and get the slide off the screen quickly. There's a few bits of the code that are encumbered in order to, when you write any piece of commercial software in a world that doesn't have free software in your mindset you sometimes go and acquire stuff from third parties and when you acquire it you don't think to get the right to give arbitrary unidentified third parties the right to create redistributable derivative works I mean no one even thinks of it because that's not what you're about and we didn't get those rights for in particular Java 2D the font rasteriser, the graphics rasteriser and the color manager 2D pieces of software and they're encumbered at the moment so when the JDK comes out in the spring it's going to have some binary plugs in it but we want to get rid of those as fast as possible and that's potentially where you come in because it may well be that, like Sven for example that you've been working on a color manager and we'd like to hear from you we'd like you to come and join in with this community because I believe that we can have a completely free Java in the fastest possible time if we get everyone working together on the same codebase just to complete the picture we've got all of Java SE under the GPL in the spring all of Java mobile is already under the GPL also all of Java EE is under the GPL we decided we would add the GPL license to the existing license on Java EE so that the story was complete now what this means is that you have available to you a complete stack of Java software which is free software under the GPL that you can do anything you want with and it stretches all the way from embeddable code for mobile devices all the way to enterprise code that you can use to program mainframes and at all points in between the key way that this software differs from other virtual machine environments you may have seen before is in the area of Java EE what Java EE does is it virtualizes or generalizes enterprise interfaces so when you use Java EE you're not locked into any particular vendor of databases or message curing systems or other enterprise facilities like you would be if you use mono.net for example you have a generalized abstracted environment which will work with any vendor and will work with any free software okay JCP yeah people asked us whether we were worried about compatibility in all this stuff one of the key selling points of the Java platform the thing that has made sure that there are over 5 million commercial developers working with it the thing that has made it be present on 2 billion devices is the fact, sorry 2 billion devices is that you can be pretty sure that the Java environment is the same in every place you find it inevitably there's going to be little differences here and there but broadly speaking the best way to get a piece of software that has a binary that runs anywhere is to use the Java platform and it's true Java compatibility that that works compatibility is insured by testing and the testing regime is going to remain in place as we move forward to the world of free Java that's going to mean that you can use the code to do anything you want with if you want to call it Java you'll still have to take a test we'll make that test available without charge to suitable non-profits we're going through a bit of a transition as a company at the moment and exactly how that testing license works out is a tricky question for us because we've actually got a bunch of people whose livelihoods depend on selling test kits and we have to find new jobs for them so we would really be pleased if you stick with us while we find new jobs for those folks but because in the interim phase there's going to be a point where we can't quite do things the way that we'd like to okay now I've done lots of talking there let's get some community voices in here first thing I'd like to do is I'd like to introduce you to Tom Marble Tom is son's open JDK ambassador and he's nervous about coming up here here we go Tom I did a dangerous thing I think last year and took Tom to Debconf in Mexico that was a lot of fun and he went native and so we decided we ought to move him off his day job you were doing something like a Java performance testing or something oh yes, performance automation and I've been sort of doing community related things with Java for the past year and going to Debconf was a great experience for me and one of the things that we did last year as we liberalized our license a little bit to make Java redistributable with distros and Open Solaris and Linux and so on and now this year of course we're going the full way with the GPL so when I just looked at Java on free software platforms it was in a pretty sad state to be honest with you son had spent a lot of its time making it work on Windows with an almost unhealthy focus on competing with a certain North Western American company and we'd forgotten about the free software platforms and we were still faithfully producing RPMs of the Java of the JDK and you needed to be a genius to install them and you needed to be a double genius to then make them run after you'd installed them and there were no packages that worked with the Debian packaging system and it was really a mess and the guys on a class path and the all the affiliated VMs were doing a bold job trying to patch up the hole that we were leaving but really it was necessary to get a new packaging system together so that we would be able to create that confidence and start writing it on the floor in Mexico well I did a little bit I really have to give most of the credit to Matias Closa who did a lot of the work with Debian so thank you Matias so tell me Tom how are we getting on with Open JDK is it going to be available sometime soon? I think the springtime assignment for real? for real for community governance? well this is one of the things that I wanted to talk about one of the things that's really exciting about joining the free software world for Java is that now we're going to be able to collaborate and in particular Mark Bwydard and I have talked a lot about ways that we can collaborate and Mark has a couple of sessions today on class path and the runtime rumble and what's coming for class path and so we're very excited to collaborate with the class path community and Open JDK and think of ways that we can grow together so that's today and then tomorrow we have an Open JDK session where we're going to talk about governance and we need your input because we want to have a governance model for Open JDK that works for everyone and is very participatory so we're going to have a discussion about governance tomorrow and a contribution policy and we also have some engineers here at the O2D hotspot the Java compiler and quality that are going to talk a little bit about what's cool with each part of Open JDK and we're really hoping that will become a lively interactive discussion on the technology that's cool that you can now access in the free world with Open JDK and then after that we have the dev jam where we have representatives from Debian, Red Hat, Gentoo, hopefully Suzy and other distributions to talk about packaging issues for Java on all of the distributions because once we solve the issues of packaging the JVMs, the libraries and the applications now Java can become an integral part of the tool chain for distributions and then we can do some really exciting kinds of innovations so that's what's coming. Great, so if you think we're screwing up at all tom.marble at son.com really? If you can't remember that, ombudsman at son.com will do just as well seriously, if you think we're screwing up I want to hear about it the first time that we're screwing up I want to hear about it at one of those email addresses and preferably not on the front page of a website somewhere so we've fixed a number of screw ups through those email addresses over the last year and make his life miserable if we're doing something wrong and buy him beer if we're not he mentioned Mark Villard Mark, do you want to come up and talk to us? So Mark is one of the heroes of free Java there's a few others around the room actually who Tom is hiding up there somewhere I think I've got them sitting there he's moved down here and there's a few other folk there's Dallibor up there really hiding at the back trying not to be noticed these guys have kept the hope of free Java alive through the years when Sun's management was doing its level best to be done and I didn't say that of course and we're really grateful to you for doing that how do you feel about OpenJDK is it ruining your life and making you miserable? it takes some adapting but luckily you didn't release everything yet so partly we are now in a how did Sven call it let's steal that cookie before they give it away so we're actually really working hard to be the first but then you released 1.6 and we're one release behind again but to be honest I think we are going to make your life a bit harder because half of our work is compatibility we so want to be the free thing that you can run any Java and if the Java Java is free then at least the compatibility part is taken care of and then we can really compete on innovating things and that's fun and one of the things you you won't like is of course that we're certainly going to make all that run with .NET and Mono but but we have been doing that and it will be fun to see can .NET Mono be a better Java than Java at least now there's a chance to prove that or disprove it and the same with GCJ we have a native cultural part and it wasn't always the fastest but at least it was the free one and now we also have to make it the fastest to be better and we have we're going to make sure that that will be available we have an AWT based on GTK Plus to the graphics based on Cairo which I think is interesting so and we're just going to talk well we have a lot of things that we can learn from you already about the way that you collaborate the way that you automate testing the way that you do all kinds of auto tools related things where we have our own strange and arcane build system that is going to take some adapting to and we can learn a lot from you in that process I hope so in the last decade the question of Java's freedom whether it could be used freely and made part of free software projects has been a crucial question Sun's policy of GPL in Java which we are celebrating now is an extraordinary achievement in returning program and technology to that state of freely available knowledge Sun has now GPL hardware designs Sun is GPL in Java that's an extraordinary vote of confidence in this way of sharing information and we in the free software world are very much pleased and very flattered to see Sun taking its own very valuable and very important products and agreeing with us that they will be more advantageous to Sun as well as to the rest of the community if they are shared under these rules that really was everything that I wanted to say to you here today I wanted to tell you that it's been a wild ride certainly for me in the last two years with Sun I believe that Sun is still a corporation and you should never turn your back on corporations and I know you won't so I know you're going to keep us honest but we honestly want to work with free software because we believe that our business is best served by working with everybody in the open room rather than by trying to get everyone into a closed room we believe that that's the future of the software business and we believe yes okay I'll admit it we believe we'll make more money by doing free software than all those other companies are going to do by doing their closed stuff and well we'd like to work with you on that and well you know I don't know how many of you are going to work on Sun's payroll I don't know how many of you are going to be on other people's payroll but we're moving into a future where we're able to synchronize the interests that we each have whether they'll be about one laptop per child and we didn't just randomly release the open firmware for one laptop per child I obviously actually asked me and I released it under BSD so they could use it and we didn't put out a press release because the only people who wanted it were them just in case you wondered we intend to pioneer a 21st century free software business and we want to do that in a way that helps you succeed at your goals as well so at any point that we screw up ombudsman at sun.com Tom Marble at sun.com Simon.fibs at sun.com write to us and tell us that we're screwing up and apart from that I look forward to collaborating and cooperating with you over the Java platform over Mozilla over Thunderbird and Lightning over all of the other packages GNOME and so on that we're working on together thank you very much for patiently listening and we've got time for some questions so don't go away Mark we have got time for some questions and do you fancy getting that guy up there who raised his hand with the microphone can you get to him? Anyone down the front to ask a question while that microphone is heading up there? My question is about dynamically typed languages I know that the J Ruby guys will hide last year by sun what is the commitment to getting dynamically typed languages running on the JVM and I think you better do it quickly because I think that North Western American company might be doing the same I think I know just them hiring a few people as well funny you should ask that because the guy who's job it is is over here in the front row this is Mark Reinholt he's the chief engineer on Java so we've definitely got sun sort of attitudinally has gone through this transition where we're definitely seeing Java as two things which is kind of what it's always been there's Java the language which is great for a bunch of stuff and there's Java the platform which is the VM and all the infrastructure and the libraries and Java the platform is about more than Java the language so not only did we hire the J Ruby guys but we're working closely with them there's going to be a JSR already is a JSR for a new byte code called invokeDynamic which is useless for Java totally pointless as far as Java is concerned but for scripting languages or other dynamically typed languages it can bring like an order or two magnitude performance improvement and so we're actively working on that with the J Ruby guys and other folks so Java the platform is definitely about a lot more than just Java the language so one of the things that I started 18 months ago was in our NetBeans tool was support for Groovy and for Geithan just Ruby that we're supporting there is one of this it's something I've been banging on about for 10 years 5 years at IBM and then 5 years at Sun is that there's a guy called Tolkstorff who's got a website with all of the languages that run on the Java VM there's something like 130 of them and we've finally got Sun to admit they exist and so we are now actively working on scripting language or dynamic languages or other languages that work on the Java VM I'm not sure I can think of very many languages that wouldn't work on the Java VM Question in the back I was very pleased and encouraged about your intentions and your ethical value systems that you mentioned earlier specifically in regard to Sun's patent portfolio unfortunately I'm not convinced that your intentions and values are necessarily shared by the directors of Sun and even if they are they are they have to do what their shareholders tell them and the shareholders can change overnight is there any intention within Sun to do with the GPL equivalent to its patents and that is to dedicate them to the public So that there's not an intent to do that The reason that we file the patents in the first place is because we are competing against a very big unconvicted monopolist in the north east of the US and a very big convictive monopolist in the north west of the US and those two companies we need our patent portfolio in such a way that we are able to use it to defend ourselves against them and a couple of other companies What I am keen for us to do however is to lock ourselves up in traps so that we can't exercise our patents against the community so that's what the patent non-assert covenants are about for example so we've made a covenant around open document format that says that whatever patents we've got we promise you that we won't exercise them against any implementation of open document format and that means that Sun and its heirs and the signs are unable to litigate against implementations of open document format and going forward you'll see us make more of those non-assert covenants in areas where we're working with the community but the way that the patent system in the US is set up there are no easy answers for how to both defend yourself against aggressive monopolists and unconvictive monopolists and how to also behave ethically and responsibly in a community and ultimately I think we need to together work out what the new ways of doing that are I talked a lot with the FFI folks 18 months ago and on from there it's still not reached an agreement about ways that actually work now there's ways that look good but working out ways that actually work in protecting us I mean we got sued by a patent troll that you'll be very familiar with a company called Kodak they bought a company that had bought a company that had bought a patent that related to object oriented technology and they took out an injunction against this over Java threatening to stop shipment of Java to anyone anywhere in the world which we thought was a really bad idea but we didn't have any patents we could fight them with and so we had to pay them 90 million dollars so that they would get off our backs even though we believed that their patent claim was worthless because in the US they could get injunctive relief against us and stop shipping our code they didn't have to prove a case they could simply say we're going to prove a case later so will you stop them shipping it while we prove it please and that's the situation that we have to defend ourselves against I hate it that it's that way and I want it to change I much more importantly want to make sure it doesn't happen on this continent because at the moment as you heard earlier we don't have the laws in place that make it happen here and I really want to make sure it doesn't happen here but in the US I'm sorry it would be irresponsible of us to dedicate our patents to the public domain but I'm very keen to do responsible things in connection with our communities thank you we've got questions we've still got five minutes there's one here in Simon there's a question somewhere over there Tom Mark, would you like to repeat the question is there any likelihood of multiple inheritance being added to Java the language that's the question I think the answer is no a different answer is hey you already have it with interfaces multiple implementation inheritance and another answer is you could always write a language that ran on the VM that had it but Mark you know the kitchen sink language that is based on Java C would the pets be accepted in a branch for the kitchen sink language for that where's Peter so one of the people we brought with us is a project so Peter van der Acha is I guess not here he's the Java C compiler lead at Sun he created another project on Java.net called ksl.dev.java.net this is actually an idea that James Gosling had it's the kitchen sink language so we open sourced Java C the compiler and now people are taking Java C and Remy forex is here somewhere he's been prototyping for declaring and accessing properties and stuff so people are going wild and it's great exploring random language ideas as the JDK7 ball gets rolling what language changes might be considered for that so that's what ksl is all about let me back up a little bit the thing about multiple inheritance it's not going to be added to Java because it's technically infeasible it doesn't mean it's a bad idea of itself it's just really really tricky to get right and people who have done it in programming languages so far at least in mind you haven't gotten it right but that's see me over beer or something and I'll talk more yes my name is Peter Enolton from the School Linux and Debian project and I'm really happy to be one of the people organizing the Debian later on my question is that when Sun is missing some pieces which has encumbered with the current Java and ksl already have one ksl ond will you actually pick it from Cloudbot? Mark I know the answer to that question but I'll let Mark tell you we can differ answers we well let's see I am not a lawyer so there's this whole contribution thing we can't just we can't just pick out random code out there and pull it in right it has to be contributed but hopefully we're going to be working with class path folks and it'll all be one fun code party filling the stuff in so I hope there's plenty of opportunity for coaching so I'll give my answer do you want to answer that as well Mark? Is that code going to end up in JDK? I'm not sure it's going into JDK but it's certain people will combine it and how precisely we figure out who is working on what is is going to be interesting of course you but that is why we are here and besides all the licensing there's the community and people being proud of their own codes I know I am so it will take some convincing to replace my code with code somebody who wrote which can never be as good as my code and probably they have the same feeling about some of their code so we'll work something out there so in essence there's no reason why it shouldn't go in there there are a few tiny problems in the way that the AWT in class path is architected is radically different to the way that the AWT in Open JDK is architected and so it isn't just a matter of picking it up and throwing it in there there is actually some heavy lifting to do to make it go in I think that's what you told me wasn't it? Yeah, it is our AWT is based on GTK plus and GTK plus has some slight changes in semantics with how things work and ability for some is a very big thing so keeping grid back layout working is an interesting problem for all of us actually just a quick update Simon's encumbrance slide was a little bit stale we actually have resolved the color management library encumbrance by incorporating I think it was a little CMS so that's actually done Igor who's sitting down here is from the 2D team and he's actually working on integrating free type in as a replacement for the proprietary font rasterizer so if you're interested in that topic you can talk to Igor we're still kind of scratching our heads over the whole graphics rasterizer thing and looking at Cairo and other stuff and that's a really hard one so we'd also welcome your input and help there so we're out of time and enjoy the conference