Barış Metin <firstname.lastname@example.org>, A. Murat Eren <email@example.com>
Translation: M. Palaja
Proofreading: Shane Shields, Gorkem Çetin
Abstract: This document describes what a developer should know and do to join the process of project development Pardus.
In this document we will explain how you can contribute to the support of Pardus Linux, developed following the structure of the Pardus project, and what are the requirements to be a developer Pardus . Although we speak of the development model for Pardus, we that these requirements can be applied to almost all distributions.
You can see the web pages for further information required Pardus to other documents, instruments and services. The pages can be reached.
What is a developer?
In short, it is not wrong to say that the project aims to achieve two objectives. As with any deployment, including the required operations, we intend to collect and prepare the software infrastructure that allows to achieve this goal and support it, as well as technology which form the core of the distribution.
The term "developer" we mean not only those who write programs, but also those that perform each operation. We know that to complete a software project you have to work in each area, such as documentation, bug control, visual materials, translations, etc.., In addition to programming. Pardus also need everything.
How can I start?
First, it is a good idea to follow the current projects. To do so the best thing is Observed for some time as a process proceeds. It May be useful to subscribe to email lists accessible from the web pages of Pardus, and follow the discussions, the current steps, bug reports, bug fixes for proposals, and study the published documents.
Following the Described methods can help in the development. You can add your comments and your Proposed Solution to testing the software bugs, or you can report new bugs you detect. You can help to Develop innovative technologies and add new features, or you can support a process of transition to Believe That You is not working (or working too slowly) and speed it up. In all this, You Should Always Be in communication with other developers. As with all operations Involving more than one person, we must know Each Other.
Can be summarised as below our needs:
=== Pengembangan software dan debugging ===
Anda dapat membuat tersedia untuk pengetahuan Anda dalam pengembangan perangkat lunak dengan bantuan dari sumber dan membantu dalam tim pembersih bekerja di bidang teknologi inovatif ini dapat memberikan informasi yang terbaik pada bantuan yang mereka butuhkan.. Dapat membantu e-mail daftar untuk mencapai Pardus.
Anda dapat merevisi bug Anda melaporkan untuk changeand pengambilan keputusan bersama oleh pengembang lain melakukannya dan - jika pekerjaan sebelumnya sudah digunakan - menggunakan ruang "test" yang tidak menyebabkan kerusakan mereka.
====== Komunikasi Ini akan selalu menjadi keputusan yang bijaksana untuk memiliki orang lain berbagi keputusan Anda, serta kemajuan dan perubahan - bahkan kecil -. Anda membuat Untuk melakukan ini, Anda dapat membawa pengembang baru - yang selalu diperlukan - untuk orang yang sedang Anda kerjakan , Anda dapat berkolaborasi dengan pengembang untuk melanjutkan lebih cepat cara itu jika Anda memerlukan bantuan di masa depan solusi akan ditemukan lebih cepat, karena pengembang lain tahu apa yang Anda akan mendapatkan. untuk komunikasi Anda dapat menggunakan e-mail daftar, mempersiapkan dokumen. atau informasi yang Anda akan menambahkan perubahan yang Anda buat.
Request for accession of new developers
There is always room for new developers. You too can become an official developer Pardus. The prerequisite to accept the responsibility of being a new developer is not always enough, but we are thrilled to accept new developers and delegate new responsibilities. For details, read on ...
Who can apply?
Anyone who works for Pardus and accept the responsibilities described in this document can apply as a new developer. The main channel of communication is e-mail lists. To accept the application will be assessed and determining the applicant's work style. To do this you can choose a suitable job for you and work on it before applying. By sharing the work with other developers allows them to review and make your acquaintance.
For example, it may be a good starting point to work with the software already present in the repository, patches and proposing new solutions, examine and test new solutions proposed by others and report your results.
How do I apply?
Simply send an email to with firstname.lastname@example.org indicated:
- * 1. the object you're working on developing
- * 2. other topics on which you want to work
- * 3. email address / user name you used to bug-tracking system
- * 4. your areas of specialization
- * 5. if possible the name of a developer who knows your work and face contact
You must include your user name and the ciphertext (created with htpasswd) of your password for your email. This allows us to add such information if it is requested an identity check.
Create a password with htpasswd ==== ==== You can create username and password using the htpasswd program and attach the resulting file to your email. To do this use the following command:
$ Htpasswd-c password_file user_name New password: Re-type new password: Adding password for user user_name
You'll get the "password_file" to be attached to your email.
Create a password with perl ==== ==== Use the following command:
perl-e "print crypt ('yourpassword', 'xy'), \" \ n \ ";"
This creates only the password in the email you must also specify the user name that you intend to use.
==== ==== Create a password with python Use the following command:
python-c "import crypt; crypt.crypt print ('password', 'xy')"
Even in this case will only get the password. Indicates the user name in the email.
Pardus in the development process through a system of control Subversion. This is an open source tracking system, a development framework that allows developers of different applications to work together without the worry of damaging the mutual work. Thanks to that individual processes of development can be traced back, you can see the changes and get them back to their original state.
At the moment there are two in the structure of Pardus Subversion repository.
Pardus === === Repository Pardus is the repository where you keep i products developed within the project. All the software developed for Pardus is maintained within this repository.