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


Hi,

I'm planning a similar sprint for LibreOffice bug fixing, but mainly aiming
for maybe Chinese or OOXML to ODF conversion problems since they're what we
mostly need in Taiwan.  Also we'll find some students who are interested in
developing (but not necessary in LibreOffice).

I'll update you if we have more progress in this event.

Franklin

-- 
Sent from my phone
2016/6/15 下午5:11於 "Heiko Tietze" <tietze.heiko@gmail.com>寫道:

Hi all,

I prepared a blog post with the intention to find more people doing
easyhacks. The idea is that we have tickets that require not much
coding skill. But even this might feel as a hurdle. When we find
people for the graphical only task it could be a first step.

Please read the (really short) draft at


https://docs.google.com/document/d/1lgAD-aE54IswyAwg6yJ6MeTstCjznPvQR1nV_R95OXs/edit?usp=sharing

I'm open to all comments and refinements. For convenience I draft blog
post in Google Docs. The final posting will be on
http://design.blog.documentfoundation.org.

Cheers,
Heiko


-- 
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
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.