There is currently a discussion going on about removing our Facebook group in favor of a regular page. If you want to join the discussion, we look forward to your comments!
So, it is here again! The wonderful time of spring. Projects that were lucky enough to be selected by Google look for talented students. And students that care enough about open source try to find a matching project. LibreOffice was selected as a mentoring organization for Google Summer of Code again this year. And today, it is the first day when students can submit their applications. We would like you to convince you that LibreOffice is indeed the best choice for you if you are a student looking to impact the open source scene in a permanent way.
LibreOffice empowers you!
LibreOffice is a project of many volunteers and paid developers. Whether you are employee of one of the many companies that contribute to LibreOffice, or volunteer representing yourself only, you are handled in the same way and only your capacities dictate what you can and cannot do. It is not unusual to find a volunteer contributor being part of decisions about technical directions of the project.
The code you will produce during the summer will be going directly to the LibreOffice git repository. We always do our best in order to see student’s work integrated in the next big release.
Participation in Google Summer of Code with LibreOffice is good for your career!
Some of you might remember that last year we had several extremely successful Google Summer of Code projects. Two of our successful students are currently employed working on free and opensource software as a direct consequence of their participation in the program. Eilidh McAdam implemented a Visio import filter that is one of the flagship features of LibreOffice 3.5. Eilidh has been employed by Lanedo before she even was able to complete her PhD degree. Miklos Vajna worked in 2010 on RTF export filter and in 2011 on RTF import. As soon as he finished his studies, he was hired by SUSE to work on LibreOffice.
This is not always the case of course, but they were neither the first nor last to find paid opportunities in the project.
Wide choice of projects and mentors
Our GSoC Ideas wiki page is containing more then 40 different proposals in each and every corner of LibreOffice code-base. From import filter for Microsoft Publisher file-format to support of sqlite in LibreOffice Base, from hacking on collaborative feature to performance improvements in Calc, everybody can find the shoe for her feet.
LibreOffice project is full of dedicated mentors that know how to work with people that don’t share with them the room next door or even the same timezone. The community is friendly and welcoming.
How to apply
Convinced? We hope so. So, here is how to proceed.
- Present yourself. Since we don’t know you we want to know some bits like your name, education, email, nickname on the LibreOffice IRC channel.
- Prove that you want to get involved into LibreOffice. In order to check this we require students to complete one of the Easy programming tasks on the Easy_Hacks page (or part of one if that EasyHack is a selection of separate tasks), though the dead-line for this isn’t hard but needs to be somewhere before the end of the selection process. This means that each student who wants to have chances to be picked for a LibreOffice project will need to build the whole application, fix a bug and submit the patch to the development mailing list. See the Development page for more infos on this.
- Explain what you want to achieve. Provide detailed informations on the project you want to work on and the use cases. The better you described it the better it is for us. It is best to base your project on one of our Ideas that come complete with friendly mentors to help you.
- How do you plan to achieve it?Provide us the following:
- An estimated schedule for the summer (including any potential conflicts you could have like courses, exams…)
- Technical details on how you want to implement it. The more sensible details you provide the easier it will be for us to check that you understood the problem and difficulty.
- Why should we choose you? Give us all the reasons for choosing you. Any past open source hacking is interesting us as well as your hacking and socializing skills.
LibreOffice community is looking forward to an enjoyable and productive summer with you.
It looks like the communication between myself and Iain did not work in the proper way yesterday evening (European time), because a couple of significant inaccuracies have crept in the text of the article:
1. The Document Foundation will probably announce a ROADMAP for LibreOffice OnLine sometimes in late April or early May. A ROADMAP and not a PRODUCT, and this should be absolutely clear. At the moment, there is no reason to expect a change in the previously announced release timeframe: “sometimes in 2013″.
2. The Android port is under way, but is the PORTING of the code to be around 80% (and not the CODING, which is still below 50%). The Android port is not a simple endeavor, and it will ask for a lot of CODING efforts once the PORTING has been completed. One of these efforts is a new touch interface, which is – by itself – a huge development effort. This is the reason why TDF will not be in the position of making ANY announcement about LibreOffice on Pads – including a roadmap – before 2013.
I hope this clarifies the issue.
After closing down the poll, counting carefully and checking back with our kind venue sponsor, the next LibreOffice HackFest is now scheduled for the weekend April 14-15 in Hamburg, Germany.
Please find more (but still incomplete) information in our wiki:
Looking forward to see many of you there!
The Document Foundation was announced on September 28, 2010. So far, it has been an umbelievable ride, especially under the development point of view. Our core development team has managed to attract close to 400 new developers, and has achieved a large number of the ambitious goals set on that date. We still have quite a long way to go, but LibreOffice 3.5 – due next week – will be the very first release showing TDF “development directions” not only to geeks but also to end users: a leaner and cleaner office suite, packed with new features. If you happen to be in Brussels for FOSDEM, you are warmly invited to join our DevRoom in Building H or walk by our booth on the first level of Building K.
The following infographic offers a preview of the data we will be announcing and commenting during our workshop.
You can download a PDF or a JPG of the infographic, for printing or publishing on your website or blog. From now on, we will update it on a monthly basis, adding more numbers as soon as they will be available.
TDF announces the first LibreOffice 3.5 bug hunting session to improve the quality and stability of the best free office suite ever
The Internet, December 21, 2011 – The Document Foundation (TDF) announces the first LibreOffice 3.5 bug hunting session, to be held in a virtual environment on December 28 and 29, 2011. Volunteer bug hunters will gather on the Internet from the five continents to spot software problems of the upcoming new major release, featuring a large number of improvements and new functions, in order to make LibreOffice 3.5 the best free office suite ever.
Participating is easy, and fun. Details are available on the wiki of The Document Foundation (http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1), where is also possible to find a comprehensive list of LibreOffice 3.5 new and improved features (http://wiki.documentfoundation.org/ReleaseNotes/3.5).
All you need is a PC with Windows, MacOS X or Linux, and LibreOffice 3.5 Beta 2 (which can be downloaded from http://www.libreoffice.org/pre-releases), plus a lot of enthusiasm. Filing bugs will be extremely easy, thanks to the help of several experienced people who will be around to help users and supporters with tips, on the QA mailing list (email@example.com) and IRC channel (irc://chat.freenode.net/libreoffice), from 8AM to 10PM UTC on both days.
A second LibreOffice 3.5 bug hunting session will be organized – following the same pattern – in mid January, immediately after the release of LibreOffice 3.5 Release Candidate 1.
The first bug hunting session has been organized by LibreOffice QA team, and coordinated by Rainer Bielefeld and Cor Nouws. At the end of the two days, Rainer and Cor will award the title of Bug Hunting Hero to the individual who has been able to spot the highest number of bugs, report them correctly and file them on BugZilla (http://wiki.documentfoundation.org/BugReport).
The Internet, October 4, 2011 – The Document Foundation (TDF) publishes some details of the security fixes included with the recently released LibreOffice 3.4.3, and included in the older 3.3.4 version. Following industry best practice, details of security fixes are withheld until users have been given time to migrate to the new version.
RedHat security researcher Huzaifa Sidhpurwala identified a memory corruption vulnerability in the code responsible for loading Microsoft Word documents in LibreOffice. This flaw could have been used for nefarious purposes, such as installing viruses, through a specially-crafted file. The corresponding vulnerability description is CVE-2011-2713,”Out-of-bounds property read in binary .doc filter”.
LibreOffice 3.4.3 also includes various improvements to the loading of Windows Metafile (.wmf) and Windows Enhanced Metafile (.emf) image formats that were found through fuzz testing.
LibreOffice developers have developed some additional security patches and fixes. These are part of a general set of development improvements which are reflected in the overall quality and stability of the software. Most LibreOffice 3.4.3 security fixes have been developed by Caolan McNamara of RedHat and Marc-André Laverdière of Tata Consultancy Services.
“Working on fuzzing LibreOffice import filters has been a great experience, and I am glad I could contribute in securing the computing experience of millions of users,” said Marc-André Laverdière, Scientist, TCS Innovation Labs, Tata Consultancy Services, Ltd. “Working in cooperation with the TDF development team, we have found and fixed serious security and crasher bugs.”
All users are recommended to upgrade to LibreOffice 3.4.3 as soon as possible, in order to benefit from the improved security of the office suite. LibreOffice 3.4.3 can be downloaded from http://www.libreoffice.org.
ODF 1.2, the document format adopted by LibreOffice, has been approved as an OASIS standard. Although we are still waiting the formal OASIS announcement, there have been a dry email by Chet Ensign and a more enthusiastic post by Rob Weir who provide several details about the story. Amongst the TC members who have contributed during the process, Rob lists two TDF founders – Thorsten Behrens and Charles Schulz – and an extremely active and well known LibreOffice core developer: Kohei Yoshida.
Standard document formats are key for liberating the user from the lock in of proprietary formats. ODF has been developed by OASIS based on OOo document format, and is now supported by most personal productivity software and many other computer programs. TDF is committed to supporting ODF and contribute to its development. ODF will be one of four main topics at the upcoming LibreOffice Conference in Paris.
In case you are having troubles accessing the LibreOffice website, you might be affected by this problem: http://www.hetzner-status.de/en.html#98