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


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.

I just learned about gsc and thought that it was completely randomize
people working on a project that we give them because we are too busy to do
it. Which I guess is kinda true. I just did not think of our guys working
on it with them. which makes sense, someone on our side has to over see it
so that they understand the code and can compliment it without having to
read it line by line to figure out how to do so.

Ether way we are the design team and have no interest in what technology
the devs use.

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.