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


Hi,

Le dim. 8 avr. 2018 à 04:20, Olivier Hallot <olivier.hallot@libreoffice.org>
a écrit :

Hello Sophia

Glad you and others liked it.

The Foundation Manifesto includes "to an open and transparent
peer-reviewed software development process where technical excellence is
valued"

TDF will not spare efforts to appreciate all contributions by the
community. Lowering barriers to code contributions is critical to the
Foundation mission.


Breaking others work like builds and translation workflow is not what
exactly TDF values I hope...


And thanks for the patches. Much needed. All of them being reviewed and
tested by committers.


Patches adding spaces in a string for an index? Again I don't see how
adding a lot of work for contributors will help them to contribute. There
are a lot of typo in the new help content that should be corrected before
and not just pushed as is, expecting to be corrected by translators. Asking
more and more to them will just push them away as it's already the case for
several languages. Sorry but I'm really not happy by this dangerous move,
consequences are too high for the moment.
Cheers
Sophie


Kind regards
Olivier

Em 07/04/2018 16:04, Sophia Schröder escreveu:
These are great news! Love it!

Exactly what I was asking about a day before in one of our IRC channels,
b/c I was clueless about how to use gerrit properly.

I uses the opportunity to commit my first patches (only whitespace
cleanups for now)
to gerrit in time of our Hackfest / German Community Meeting in Hamburg.
So yes, it works! :-D

What would be really really good were a) a review of course and b) an
jenkins/ci buildbot for help
for mistakenly merge patches which break master or branches in cases of
backport.

Am 06.04.2018 um 03:15 schrieb Olivier Hallot:
Hi L10N Community! Breaking news!

Help pages can be edited directly in gerrit, all editions done in your
browser.

This means that edition of textual XML is possible with automatic
generation of a patch submitted to gerrit. Therefore, English source
help files can be edited or corrected directly in master and with
security and peer review provided by TDF security infra.  Such
capability will be extremely handy for ad-hoc correction of typos and
linguistic mistakes we often do in English, as the LibreOffice project
is developed by many non-English native speakers.

This capacity will let help writers a direct access to patching without
having to download and build LibreOffice and its help. Although the Help
XML knowledge is still need to correctly write a help page, some of our
skilled NL leaders and translators can now fix typos directly, without
passing by the lengthy process of reporting typos, building help and
more.

Please see a tutorial on editing help source files in our wiki page:

https://wiki.documentfoundation.org/Documentation/GerritEditing

Happy help page fixing !

Cheers


--
Olivier Hallot
LibreOffice Documentation Coordinator
Comunidade LibreOffice
Rio de Janeiro - Brasil - Local Time: UTC-03:00
http://tdf.io/joinus

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be
deleted


-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.