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


Hi Hassan,

the same is true for this project as replied for the other [1]. First you have to prove your 
skills. 

The topic is discussed at Bugzilla in tdf#99669, tdf#37932 and tdf#92902 as stated in 
http://pad.documentfoundation.org/p/UX-GSoC_Ideas #5. The design team will start to flesh out the 
needed features when the project is likely to go live. Your mentor would be Thorsten Behrens 
co-mentored by Jan Holesovsky, he is known as Thorsten on IRC, Jan is kendy.

It's great to see your interest in UX topics. But you can apply only for one project. So choose 
wisely. :-)

Cheers,
Heiko

[1] Other topic was the Navigator 
http://nabble.documentfoundation.org/GSOC-17-Navigator-tt4209840.html

On 03/08/2017 03:09 PM, Hassan Ali wrote:
Sir,
  I am interested in working on Block Diagram feature  for google summer of
code. Kindly brief me about the project so i can start working on it as
soon as possible.

Regards,
Hassan Ali


-- 
Dr. Heiko Tietze
UX Designer
Tel. +49 (0)179/1268509


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