Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

 the dev team even has little control over this
because this is apart of the Google summer of code, which meas that someone
not apart of our dev team is going to write it.

Hmm, this is not really accurate. I don't see it as we would have a
clearly delimited "dev team" (with presumably some fixed
conditions/rules/process to invite/accept new members). It's more like
we accept any patch that seems even remotely useful, doesn't break
stuff and nobody objects violently to, and if you keep doing good work
you will get direct commit access.

GSoC students are definitely supposed to be part of the "dev team".
(Sure, they might choose to cut down on their contributions after GSoC
is over, but the purpose with GSoC is that they stay attached to the
project, as far as I understand.)


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.