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


Hi Stefan,

Sorry for not replaying earlier.

The problem is this, icon designers use SparkleShare with github and they usually leave scratch 
files and uncompleted work there because SparkleShare functions like Dropbox, and the other problem 
we'll have to give newcomers push access to fdo as soon as they ask to join.

If we want to move Sifr to fdo, we've to make an easy way for newcomers to get push access to Sifr 
folder (only) and we've to make sure they can use SparkleShare or similar with fdo.

Regards,
Ahmad Harthi

________________________________________
From: Stefan Knorr [heinzlesspam@gmail.com]
Sent: Thursday, June 12, 2014 05:08 PM
To: Ahmad Hussein Al-Harthi; Issa Alkurtass; Norah A. Abanumay; Tin Man; Design List
Subject: Re: Sources for Sifr icons

Hi Ahmad, Issa, Norah,

can any of you comment on this issue?

Ping,

Astron.

On 15 May 2014 17:59, Stefan Knorr <heinzlesspam@gmail.com> wrote:
Hi all,

it seems like we need to discuss the direction of Sifr a little. Specifically,
there seem to discrepancies in the amount of icons between the Sifr
folder in LibreOffice's core repo and the one in Sifr's own repo on
Github.


How can we best make sure that _all_ source SVGs (and all
exported PNGs) are available from the same source?


(Some developers have lamented the fact that Sifr was started outside of
freedesktop.org. Since Sifr is now part of LibreOffice proper we should probably
reconsider if we still need the special repo and why[1].)

Astron.



[1] The original reason was (iirc) for it to be easier to involve people
  scared of fdo but who already had Github accounts -- I think we did not
  completely fail on this aspect.
  The other original reason was that we did not like to push the theme in too
  quickly and have some time to prepare it ... well, that reason is now gone.
Warning: This message and its attachment, if any, are confidential and may contain information 
protected by law. If you are not the intended recipient, please contact the sender immediately and 
delete the message and its attachment, if any. You should not copy the message and its attachment, 
if any, or disclose its contents to any other person or use it for any purpose. Statements and 
opinions expressed in this e-mail and its attachment, if any, are those of the sender, and do not 
necessarily reflect those of King Abdulaziz city for Science and Technology (KACST) in the Kingdom 
of Saudi Arabia. KACST accepts no liability for any damage caused by this email.

تحذير: هذه الرسالة وما تحويه من مرفقات (إن وجدت) تمثل وثيقة سرية قد تحتوي على معلومات محمية بموجب 
القانون. إذا لم تكن الشخص المعني بهذه الرسالة فيجب عليك تنبيه المُرسل بخطأ وصولها إليك، وحذف 
الرسالة ومرفقاتها (إن وجدت)، ولا يجوز لك نسخ أو توزيع هذه الرسالة أو مرفقاتها (إن وجدت) أو أي جزء 
منها، أو البوح بمحتوياتها للغير أو استعمالها لأي غرض. علماً بأن فحوى هذه الرسالة ومرفقاتها (ان 
وجدت) تعبر عن رأي المُرسل وليس بالضرورة رأي مدينة الملك عبدالعزيز للعلوم والتقنية بالمملكة العربية 
السعودية، ولا تتحمل المدينة أي مسئولية عن الأضرار الناتجة عن ما قد يحتويه هذا البريد.


-- 
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.