Differences between revisions 4 and 5
Revision 4 as of 2006-03-16 11:12:35
Size: 3393
Editor: ?SteffenJoeris
Comment: work on format
Revision 5 as of 2006-03-17 18:50:30
Size: 3448
Editor: JuliaWierich
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
servers itself. There are also the admins of the servers.
You get in contact when you enter the project or when you request new
rights, e.g. upload rights.
servers themselves. There are also the admins of the servers.
You get in contact if you enter the project or if you request new
rights, such as upload rights.
Line 17: Line 17:
This is the group which decides about sponsoring for travel costs or
developer gatherings. Write them if you want to get sponsorship for a
This group decides about sponsoring for travel costs or
developer gatherings. Contact them if you want to ask for sponsorship for a
Line 29: Line 29:
archive itself, the CD creation and moving packages between the test archive itself, the CD creation and for the movement of packages between the test
Line 41: Line 41:
make sure that it builds on every architectures. For that they make sure that it builds on all architectures. In order to achieve this, they
Line 43: Line 43:
It is their job to make sure there is a running Debian-Edu/Skolelinux It is their job to make sure that there is a running Debian-Edu/Skolelinux
Line 52: Line 52:
The bug reporting and their fixes are managed by the The bug reportings and their fixes are managed by the
Line 54: Line 54:
The structure and coordination of these bugs is part of the work of the
Bugzilla team. They can also increase or decrease the urgency of bugs
and assign someone to them. Their goal is it to keep the number of bugs
The structure and coordination of these bugs is part of the Bugzilla team's work. They can also increase or decrease the urgency of bugs
and assign someone to them. It is their goal to keep the number of bugs
Line 58: Line 57:
care/focus on specific bugs. care for/focus on specific bugs.
Line 67: Line 66:
(Debian Edu Security Announcement). They look after the DSAs and (Debian Edu Security Announcement). They look after the DESAs and
Line 69: Line 68:
upload packages with security fixes and an high urgency to all pools. upload packages with security fixes and a high urgency to all pools.
Line 77: Line 76:
The goal of this team is to always provide up-to-date HowTos for
installation and administration. For that they coordinate their work
The documentation team is responsible for providing up-to-date HowTos for
installation and administration. For that goal they coordinate their work
Line 87: Line 86:
This part is very important for Debian-Edu/Skolelinux. There are some The team maintainance is very important for Debian-Edu/Skolelinux. There are some
Line 92: Line 91:
The debian-edu-install package is the installation one. The debian-edu-install package is the installation part.

This guide gives an overview about the existing teams in Debian-Edu/Skolelinux.

drift

This is the commitee which is responsible for new accounts and the servers themselves. There are also the admins of the servers. You get in contact if you enter the project or if you request new rights, such as upload rights.

Members: Petter Reinholdtsen, Morten Werner Olsen, Ragnar Wisløff

styret

This group decides about sponsoring for travel costs or developer gatherings. Contact them if you want to ask for sponsorship for a special part of your debian-edu related work, for example a flight to a developer gathering.

Members:

ftpmasters

These people maintain the archive system. They are responsible for the archive itself, the CD creation and for the movement of packages between the test and more stable pools.

Members: Morten Werner Olsen, Martin Zobel-Helas, Holger Levsen and

  • Steffen Joeris

architecture porters

Debian-Edu/Skolelinux will be available for three architectures (i386, powerpc and amd64). The porters take care of every package and make sure that it builds on all architectures. In order to achieve this, they coordinate their work with the specific maintainers. It is their job to make sure that there is a running Debian-Edu/Skolelinux version on all of the three supported architectures.

Members: Martin Zobel-Helas and Holger Levsen

Bugzilla team

The bug reportings and their fixes are managed by the Debian-Edu/Skolelinux Bugzilla. The structure and coordination of these bugs is part of the Bugzilla team's work. They can also increase or decrease the urgency of bugs and assign someone to them. It is their goal to keep the number of bugs to a minimum, therefore they can advise the other teams to take special care for/focus on specific bugs.

Members: Frode Jemtland

Security team

The Debian-Edu/Skolelinux security team announces the official DESA (Debian Edu Security Announcement). They look after the DESAs and bring security fixes into the distribution. They are also allowed to upload packages with security fixes and a high urgency to all pools.

Members: Finn-Arne Johansen, Morten Werner Olsen and Steffen Joeris

Documentation team

The documentation team is responsible for providing up-to-date ?HowTos for installation and administration. For that goal they coordinate their work with the other developers.

Members: Klaus Ade Johnstad

Team maintaining

The team maintainance is very important for Debian-Edu/Skolelinux. There are some base packages within the distribution which are always team maintained and under subversion control. Mainly there are three packages debian-edu-install debian-edu debian-edu-config All developers are responsible for these packages. The debian-edu-install package is the installation part. For organizing the installer this package does the job. The debian-edu package is the meta package of Debian-Edu/Skolelinux. This package decides which package should go onto a Debian-Edu/Skolelinux system by default. The debian-edu-config package preconfigures the Debian-Edu/Skolelinux system directly after the installation. For that it uses cfengine2. In order to work on the configuration it is neccessary to bring the changes into this package.

Members: All developers