 We have worked with Berlin authorities for a few months. The Berlin authorities expressed the wish of being the house of the document foundation because they feel that Berlin is increasingly a city with several open source projects. The problem that we had originally was that we wanted to have a foundation where members were able to be in control of the foundation, in control of the governance. The European laws about foundation made it a little bit difficult so we had to work out this specific problem with Berlin authorities and we have found a way of having both a foundation so to have what is called in Germany a Stiftung in terms of governance but a Stiftung where members are recognized and are able to express their wish by electing the board of directors, by electing the other bodies of the foundation. Of course we are not disrupting the model, we have adapted the model to the bylaws of the document foundation. We have changed slightly the bylaws but the Berlin authorities have been very open in accepting a different model from the past and a model that is more suited for two free software communities. No, the model is absolutely the same. What has changed and has changed a little bit are the numbers. For instance we initially wanted to have a board of directors of nine people and we went down to seven. This just because the ratio between the board of directors and members is more acceptable for the authorities. In the future we don't exclude the possibility of going up to nine but at the moment there are seven directors and three deputies and the membership committee which is a very important body of the foundation has five members and two deputies. The membership committee is key because it is the committee that approves membership applications. So of course it is a key role in growing the foundation. We have all the rules on the website but generally speaking who is already contributing and is already known in the community has really no problem in becoming a member. He has just to apply that is a formality. He has to send an email to the membership committee and it has to provide a few information but let's say that for people that is already working inside the community this information is pure formality. Just to say I'm active on PUTL for localization or I have committed some patches or fixed some bugs so you find my name on bugzilla and this is enough because the membership committee is looking into these domains to check. Of course if you've done less visible stuff then you have to provide more evidence of what you've done especially if you've done stuff at local level that we need some evidence. The problem is that it's not that we don't want members it's that we want to have a community of real contributors so members have to be contributors. Having members just for the sake of having members doesn't mean anything because the community is stable if people is contributing and this is something that comes from our previous experience where you are member contributing on a stable basis and you are member contributing on a very or total random basis and then it's almost impossible in this case to build a path for the future because you need people that tells you in three months I will be doing this and then you have to be almost sure they are volunteers of course but you have to be almost sure that in three months they will be doing what they have promised. Just being there for the sake of having a kind of LibreOffice address or a document foundation address is not our case we don't want that kind of guys that want to have just an email address and say I'm proud of being a member of the community they can be a member of the community anyway they can show a sticker on their laptop if they want but being members means becoming contributors. We have the stats but I would prefer not to talk about this we have commented so many times about why we think that the choice of the Apache license is not a good choice the problem is that the Apache foundation is respected we respect the Apache foundation a lot and the problem is not the Apache license per se is the Apache license applied to a product like OpenOffice because the integralism we can say of the Apache license is the fact that you cannot accept copy left software or copy left code inside the Apache license project is a strong limitation if you look at the software like OpenOffice because you have many modules who are GPL or they use a Mozilla public license and these are key modules sometimes in a software like an end user software for instance one of the most trivial examples are funds many funds are not licensed with a permissive license I would say that most funds are not licensed with a permissive license so you cannot embed those funds into the binaries while users and with users I mean an Office Productivity Suite users they are usually basic users they don't know how to install funds on their system you have to provide the funds embedded into the software and not providing many funds or providing only the funds with a permissive license is a huge limitation and this is just let's say the easiest example but there are other pieces of technology which are more technological than funds that provide a similar limitation and in many cases rebuilding a library or a module just for the sake of not having it with a copy left license in our opinion is a huge loss of time and it doesn't just make sense so the problem is not Apache Software Foundation it's not the Apache license it's the Apache license applied to OpenOffice.org if they have already been contributing to OpenOffice the switch or the collaboration is extremely easy we use the same system so we use a portal system, a portal server and we use many of the strings that were used for OpenOffice of course we have added our own strings because we have added menus and windows but most of the previous translation is going to work and adding the few strings that are missing it's just a few days of work it's very easy the community is extremely welcoming so if you have a problem you just write an email on the localization mailing list and you will find someone who is able to help you to give you hints on where to go to become immediately a contributor because people that were contributing to OpenOffice can become contributors in a matter of really hours so it's not anything complicated of course if you start from scratch you may not know Google you may not know how to localize but for instance if I look at the Italian project which of course I follow more closely because I'm Italian we have got something like 7-8 new localizers in the last few months just because they have started writing an email and the two leaders of the localization have been so quick in answering that people has felt at home and that is I think the most significant achievement the fact that you don't have to go through someone in a corporation to be recognized as a member of the project the project is recognizing members immediately there's no one like a community manager that tells you now you are a member of the community you become a member of the community by doing which is the most exciting thing for a free software project they are actually showing Michael Mixas showed yesterday a compilation of LibreOffice on an Android tablet it is a compilation the interface is missing so this means that the software runs on an Android tablet as it runs on a PC today the interface which is a touch interface has not been done so we are still missing part of the entire software but we have done most of it because the software compiles and runs we plan to work on the interface shortly so our plans were to release a product at the end of 2012 or early 2013 I would not change those days just to be safe but I think that we might be ready for the next LibreOffice conference which is going to be in September-October time frame so before the end of the year with a product actually released but let's say that to be safe we say end of 2012, early 2013 we will be on Android and we will be on iOS immediately after of course we are looking at the user interface with a lot of attention we have a group of people working on that the issue on that side is that in order to change the user interface you have to make the software more modern is what we are doing at the moment so it's not just a question of applying a new user interface it's a question of changing graphic library behind of making the user interface more integrated with the software for instance it looks like the API doesn't allow to have the lower bar with the information and of course you need to develop APIs that allow you to put this kind of information like for instance number of characters we have now the number of characters but it is on a separate windows because it is impossible to provide this information on the lower bar so before changing the look of LibreOffice we need to add some features we need to clean some more libraries we need to change some more libraries it is something that we are doing we will continue to work on that but I don't think we can anticipate when the interface is going to change we will probably change the interface with version number 4 which is still not on the release schedule so it's going to be in early or in mid 2013 but we don't want to do something just for the sake of doing something when we change the interface LibreOffice will become a different product the interface is not enough you have to add features and you have to make the interface different of course the work that we are going to do on Android will help the change in the interface because although it's not going to be a touch interface on a PC but you have to make it more natural as an interface and therefore the work you do for Android or for tablets will help in improving the interface but before you can apply that to a PC interface it will take time unfortunately we come from the ten previous years were completely static in terms of interface and you cannot change the interface in one year after ten years of standing still on the interface it takes some time