With FOSDEM 2016 done, it is time to concentrate on GSoC.
We see a lot of student submitting patches in order to ease the GSoC qualifications. Submitting patches and showing interest for the community are clearly a good start for being accepted. However we see many patches that are mechanical changes (search/replace) in the source, such patches shows little (if any) understanding of what development is.
A succesful patch, is one that shows understanding for the code. If a student shows (with a patch) understanding for how C++ works, it is a plus in my mind, whereas mechanical changes are actually a minus in my mind.
We are available to help, through email or IRC, so feel free to ping us, but please try to make quality patches. Sending multiple patches with the same error is not a GSoC qualification, but a single well thought over and implemented is the first step to qualify.
We look very much forward to GSoC and to mentor students who want to help make LibreOffice an even better product.
Let us together make GSoC 2016 and LibreOffice a period to remember.