[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] A common policy regarding weblate bugs/improvements

Hi Sophi,
thank you for the answer. They are mostly minor improvements, so I'll
file them directly

On 12/13/19 10:10 AM, sophi wrote:
> Hi Milos,
> Le 12/12/2019 à 14:34, Milos Sramek a écrit :
>> Hi,
>> with the new hardware Weblate started to be pretty usable. Great! I've
>> spent some time with it and now and I can see some possibilities for
>> improvement.
> Great and thanks for your feedback :)
>> Do we have a policy how to file issues to Weblate? Just as individuals?
>> Or, do we as LO have some kind of "special relationship" with Weblate
>> which would make issues filed in the name of LO "heavier"?
> No special relationship for the moment. I think that if it small issues
> or enhancements, filling them directly make sense. If this is for a
> functionality or a feature and is a must have, then let's discuss it
> here before and see if we can join forces with Fedora, OpenSUSE and KDE
> to fund it.
> Cheers
> Sophie

email & jabber: sramek.milos@gmail.com

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/
Privacy Policy: https://www.documentfoundation.org/privacy

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.