irc nickname: mesutcan (mostly on #debian, #gnu, #pardus, #pardus-devel at

xmpp: /

address: Canakkale Onsekiz Mart University Bilgi Islem Daire Baskanligi Terzioglu Kampusu 17100 Canakkale, Turkey

I'm currently a 3rd grade computer engineering student at Canakkale Onsekiz Mart University in Turkey. I'm interested in compilers and operating systems. Also helping free software projects.

Me and my roommate coded a version control system written in Java using Test Driven Development.[1] I'm a developer at Pardus Linux. I'm currently maintaining 65 packages at Pardus Linux. I was in a team who ported Pardus Corporate 2 to 64 bit and I'm still in a team called as COMAK: bringing other window managers (other than KDE since Pardus is KDE-based distro) to Pardus Linux. Such as Fluxbox, LXDE, XFCE, Enlightenment, Gnome, Gnome3. I've released Fluxbox based Pardus (like fluxbuntu) and managed releasing jobs and other things like writing requiring scripts for server-side or devepoling (packaging scripts in this team. You can found them in my git repository [5] (the repo named as general). Also making packages for the COMAK. Now, COMAK project is turned into a Community Distribution Project (Pardus Linux based).

Next year we are planning to port GNU/Hurd to Pardus Linux. And boot system with GNU/Hurd. After that remove all non-free packages or anything from Pardus. This project is also exciting

I'm also working on Pardus' Package System, ?PiSi. It is written in Python and it has also an API named as pythonmodules to build python extensions which is under actionsapi . Now, I'm working on a patch to make packages from scm's and multi repository support. (overlay repository)

Now, I've sent a patch to bug#585357. I'm trying to fix some Debian bugs related to python modules (like converting from dh_pycentral to dh_python2 to understand Debian Packaging with Python Modules well. (i know packaging python modules from Pardus Linux which distribution I made some python module packages for) I've been using Linux Distros since 2002. I'm currently using Pardus Linux and Debian GNU/Linux. I've used Slackware, Fedora, Redhat, Mandrake, ?SuSe, FreeBSD, ?OpenSolaris, Ubuntu.

I was interner at Pardus Linux last year. I've done 2 projects[2][3] (both are written in Python) and write a blog[4] what I've done. Also have a git repo at github for personal jobs etc [5]. I think documentation is very important in this projects. I love researching. I'm writing blogs in Turkish but now I'll write it in English.

I also interested in Debian packaging (and made some packages but not professional) and now translating Debian New Maintainer's Guide's and Debian Social Contract's never versions.






Writing a tool which is to automate building Python extensions for all Python Versions. Also it supports tests from other build systems such as distutils, autotools, scons etc.

This tool will be included in Python package. With this tool Debian Developers, Debian Packagers or who want to build package can be easily build python extensions. With its supporting all Python versions feature, it will be very easy to packaging them.

Developers can easily build python extensions for every python versions for Debian.

This project is about writing a tool to build python extensions for all Python versions (supported by Debian at the time). I think an important thing about this project is using only standart library and having no dependency. And it comes with Python package. The project should support testing in modules if available for each build system (such as distutils, autotools, scons)

And I should create a patch for CDBS and dh sequencer which will replace other Python snippets with my project.

Also I fix the bug #538978

Following the Google Summer of Code Timeline:

I Think I can finish the project about 2 months. I can start working after I learn my proposal is accepted.(April 26)

April 26 - May 24:

It is a study period, its time to understand what I will do. Learn how building python modules works. What did other distributions do about that? What are other problems ? And dive into Debian packaging (still working on it but I think I need more)

May 24 - June 10

Start coding. Firstly my aim is writing a tool which is only builds Python extensions for only one version. (probably current version)

June 11 - July 1

My tool will build Python extensions for all Python versions. Maybe there will be some problems about some packages or something like that but that one won't be serious. Write a plugin for build systems (i think first one it will be autotools) to run tests for all Python versions.

June 6 - July 13

Write documentation and make tests. This is very important. I will (and should) write a good documentation and write something like blog to tell everyone what did i done step by step. And for bugless code I should make tests.

July 13/14

Submit mid-term evaluation.

July 15 - August 9

Write other missing things about program. Write all plugins for build systems to run tests. Create a patch for CDBS and dh sequencer for replacing Python snippets with this project's (python-multibuild) calls.

August 9 - August 16

Improve documentation and tests. Scrub the code. Test the tools everywhere possible.

I've currently no other summer plan. Only Google's Summer of Code.

No. No school exams or something else.

I want to be a Debian Developer, if I can be a developer during the GSoC, I'll do (contribute) more things to Debian. Maybe orphaning packages, fixing bugs or something like that.