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


Hi,

My name is Gülşah. I'm senior at Onsekiz Mart University. My department is
computer engineering. My ircnick is gulsahkose.

I am a GNU/Linux user for four years. I’m interested in C++, C  and Python
programming languages.  I develop my projects by using git. I have a github
account (https://github.com/GulsahKose/). I am the developer of
pebble-remote project. This project provides manage your Libreoffice
Impress  presentations with Pebble smartwatch. Project’s address:

https://gerrit.libreoffice.org/gitweb?p=impress_remote.git;a=tree;f=pebble;hb=HEAD

and project’s web site following

www.pebbleremote.com

I want to be a real LibreOffice developer. I can learn quickly. I'm
experienced in working remotely. I know how to use git well. My 88 patches
accepted into linux kernel while opw application process. You can find my
patches following link:

https://patchwork.kernel.org/project/opw-kernel/list/?submitter=90411

I’ve made speechs about my projects, place of women in computer sciences
and free software 10 times at different events . I mentioned LibreOffice a
lot on this  speechs.

I have sent a patch to bug#89756 and pushed master (
http://ci.libreoffice.org/job/lo_gerrit_master/1385/).

I'm looking for another bug can fix it now. I want to work on the job
-Implement EPUB export filter- .

Best regards
-- 
*Gülşah Köse*
*about.me <http://about.me/gulsahkose>*

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.