What kind of works a developer interested in?

Pardus Linux Distribution developers have different roles in the project. A developer has one of these roles or more at the same time. A developer also can take a new role according to his experience.

Package Maintainers

1. Maintain the package according to repository and package rules.
2. Control, analyse, resolve and fix the bugs that reported on Bugzilla
3. Follow and read the technical lists and websites about the maintained package
4. Follow and read the other distributions plans about the maintained package.
5. Be in contact with the upstream of the maintained package.
6. Before merging the package to relavant repositories, make functional and installation tests.
7. Follow the security related bugs from Bugzilla and be in contact with Security Supervisor.

Component Supervisor

• Every component and subcomponent has a component supervisor.
• If a subcomponent has not a supervisor, one up component supervisor is also the supervisor of it.
• The last decision about the component is given by main component supervisor.

Roles

1. Control the package maintainers under his supervised component:

   The control is concerned with above instructions:

   • Are the updates acceptable for package and repository rules?
   • Is package maintainer dealing with related package bugs?
   • Are the packages merged before given deadline?

   If the package maintainer is not responsive for a long time, supervisor should:

   1. Deal with the unmaintained package. (package update, maintenance, merge, bug fix)
   2. Describe the package maintainer status. (retirement, military duty and other private issues)

2. Move packages in the component and decide whether the package is suitable with the selected component.

3. For the orphan packages under his supervised component:

   1. Control orphan packages and list them
   2. Maintain orphan packages for a while
   3. Allow temporarily maintenance of the orphan package for an other maintainer
   4. Find maintainer for orphan package.

4. Join the new package review process of the packages under his supervised component.

Software Developer

1. Take into account the new feature requests and prepare a requirement list in consultation with the lead developer
2. Design the software that will be implement and prepare design documentation.
3. Implement assigned part of the software and prepare their unit tests.
4. Prepare the user guide and technical documentation
5. Control, analyse, resolve and fix the bugs that reported on Bugzilla
6. Maintain the packages that are required for the software

Lead Developer:

1. Analyse, manage and plan all the life cycle of the project
2. Take into account the new feature requests and prepare a requirement list in consultation with the related developers.
3. Give timelines of the project in consultation with release manager and product manager.
4. Organize and coordinate the developers under the project.
5. Review bugs related to the project and give related severity and priority levels.

Last Modified Date October 26, 2011

Author:Semen Cirit