 Well, it started in 2001 when I joined some of the guys in Brazil that were interested into bringing OpenOffice at that time for Brazilian Portuguese, then I got involved with the community in Brazil and I started to help them to translate the software for Brazilian Portuguese. Since then I got slowly involved much more and more into the OpenOffice community. We also developed the community in Brazil. We even founded an NGO in Brazil to give us legal shelter for the Brazilian community. We also had an issue with the names of OpenOffice back to 2007 because the name was Trade Market in Brazil. We had to change the name of the community and the NGO and we called it BROffice. Back in 2010 with the appearance of LibreOffice it was a natural move to bring BROffice inside LibreOffice and after that we abandoned the BROffice brand and we stayed with the LibreOffice brand and my participation in this activity was not only by one of the founding members of the Document Foundation so basically we continued the work of translating and keeping the software updated to the latest releases. So the activity in Brazil is quite intense in the last decade. Today I am coordinating the documentation for LibreOffice. It's an interesting job because I think that in my personal view it's not a product that the Document Foundation should be considering as a collateral to the software and also what is important is that documentation is also an easier way for non-skill developers to participate in the project. So at the moment we are making a way to make it easy for non-developers to really contribute into our documentation. We built the question and answer forum which is the Askbot. We also created a documentation specific website. The two are linked now with the software so for the user it's now very easy to get to the documentation and we have plans to make it easier and more dynamic the help content that we have in the software. So modernization of the software, of the help content, creation of a specific website for easy access to the documentation and also an active and dynamic question and answer forum for the user. So the idea is to bring LibreOffice more close to the user and let the user more comfortable in using the software. So far what we have detected which is interesting is that there is a strong demand on documentation on Calc and Writer. These are the two models that are very well used and people seem to lack the availability of an updated guide for these two software. So this will open us a very interesting perspective in the next six months to twelve months to address this demand that is already there. Yeah it's a good point because one of the things that in the last six months we had is people approaching the documentation team and say I want to help how do how do how can I start helping the documentation. So when they decided that they want to build a new page on the help it's so hard for them to jump into XML and write things and test and build and compile and such and such that I decided to give to the to the newcomers the idea of please write a page in a document like Writer with this with this content that has to be this this and this topics that you will fill with your experience on a specific feature that you're writing about. So people wrote about the the subject and then sent to me and then I take the content and I transform it to a help page. It takes a lot of time it takes for me I am skilled in the in the issue but it takes for me about five to six hours to really finish a help page by hooking into the code. So this is not acceptable I mean it has to be more easy. The idea is to since we have this very old technology that was built for 10 years ago it's time now to modernize it. So let's let's look again to the contents of this XML and let's try to make it more easy for the user. So why an XML is not not needed anymore because basically what you use is to display contents it's not to you don't use the the feature of XML to exchange information it's just display. So if it's just display let's go for HTML then if you come if it's possible to go to HTML then you have an enormous amount of tools that helps you to edit HTML in an easy way. You have online editors you have offline editors it's much more easy what you see is what you get. So let's start to build an environment to make it easy for the user to or to the volunteer to jump in the the health system and correct updates or even create new pages in the health system and this this is a project I would like to carry in 2017 in order to get the users and the newcomers in a in an easier way to contribute because you see one of the interesting approach is that people that wanted to write are young professional writers and this is I am I graduated into a professional documentation and then I would like to exercise can you help me so this is a good way to get people that has more than quite an amount of skills and wants to exercise with us so it's a good opportunity for them to create their own resume by contributing into our project. Yeah the language barrier is definitely one of the most the greatest issues that we have to have these people contributing to TDF. I can tell you because I am almost kind of official translator for even the community and people really are scared to communicate in English and this this this is a real issue. The point is it's not that easy we really need to have some key persons in the country that can really be sort of leaders on on the local community but it's it's a it's a it's an important approach to not let the leader be a kind of a small emperor and to to shape the community on his own wishes which is not good so it's very very important to always open the the communication between the document foundation and the individual it's important not to have people in the middle to unless it's for just for translation it is important to develop a local open source events to get these people to gather it's important also to find a project and get people involved in the project say for for example translation we in Brazil we have a weekly meeting hang out through hang out with seven to eight people and we talk about issues on translation and documentation so that keeps the community I mean at least the team very close together we have a face-to-face we know we can look at at the face which is also very important for building synergy and we keep this meeting regularly even if the amount of subjects is is small because people we discover that really people like to communicate they really like to communicate and and they also are very proud to be part of a team so if we if we can build a team that has an interesting mission and it's it's good for their own their own developments then you have a winning team for open source