Michlmayr Managing Debian
Upcoming SlideShare
Loading in...5
×
 

Michlmayr Managing Debian

on

  • 1,307 views

 

Statistics

Views

Total Views
1,307
Views on SlideShare
1,307
Embed Views
0

Actions

Likes
1
Downloads
9
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Michlmayr Managing Debian Michlmayr Managing Debian Presentation Transcript

  • Debian Organisation
  • Index
    • Introduction
    • Debian Hierarchy
    • Roles in Debian
    • Teams in Debian
    • Debian's Infrastructure
    • Joining Debian
  • What do you think?
    • Around 20000 packages
    • +1000 developers
    • Cathedral-like or bazaar-like organisation?
    • One project leader?
    • Several leader-like figures?
    View slide
  • Debian Organisation
    • Including Comments on:
    • Managing Debian
    • by Martin Michlmayr, 2003
    • and
    • The Debian Constitution
    • http://www.debian.org/devel/constitution
    View slide
  • Debian Hierarchy
    • Debian has a flat hierarchy
    • Everyone has the same rights
    • This requires a meticulous application process
    • There is the exception of Debian Officers
    • Everything is in the Debian Constitution
  • Roles in Debian
    • The Developers
    • The Project Leader *
    • The Technical Committee *
    • The Individual Developer
    • Delegates appointed by the DPL
    • The Project Secretary *
      • * these are officers
  • Roles in Debian
    • Individual Developers
      • Decisions regarding their work
      • Propose General Resolutions
      • Propose themselves for DPL
      • Vote general resolutions and leaders
      • They are volunteers
      • They may be banned by Delegates
  • Roles in Debian
    • The Developers
      • Appoint or recall DPL
      • Amend the constitution
      • Override decisions made by DPL, Delegates or Technical Committee
      • Issue, supersede or withdraw documents
      • Make decisions about property
      • Appoint a new secretary
  • Roles in Debian
    • The Project Leader
      • Official representative of the project
      • Talks, presentations, building good relationships with organisations
      • Manage the project, coordination and communication with Delegates
      • Chosen in an election for one year
      • http://www.debian.org/vote/2003/platforms/tbm
  • Roles in Debian
    • The Project Leader
      • Appoint Delegates for specific areas
      • Lend authority to other Developers
      • Make any urgent decision
      • Make any orphan decision
      • Together with SPI, decide about property and money owned by Debian
  • Roles in Debian
    • The Project Secretary
      • Appointed by DPL and the last PS
      • Conducting votes
      • Standing in for other Officers
      • Interpreting the constitution
  • Roles in Debian
    • The Technical Committee
      • Technical disputes, 4-8 members
      • Decide any matter of technical policy
      • Decide technical matters where Developers' jurisdictions overlap
      • Any person may require them to delegate a decision of his own, or seek advice
      • Overrule a Developer
  • Teams in Debian
    • Several teams formed naturally
    • Clear areas, mostly technical
    • To join, just show technical skills and willingness
    • Teams are staffed with knowledgeable and enthusiastic participants
    • This leads to a level of peer review and excellence widely held with respect
  • Teams in Debian
    • Quality Assurance
      • Maintains orphan packages
      • Searches for inactive maintainers and buggy packages
      • They can take away packages from maintainers, despite no one gave them power for this. They established authority by doing it
  • Teams in Debian
    • FTP Masters
      • Debian's software archive
      • Adding and removing packages
    • Listmasters
      • +150 mailing lists
    • Debian Admins
      • debian.org machines
      • Testing machines for different architectures
      • General infrastructure: web, FTP...
  • Teams in Debian
    • Web and Translations
      • Debian's web pages
      • Translation to other languages
    • Security Team
      • Tracks security issues in released packages
      • Publish advisories
      • Provide patches
  • Teams in Debian
    • Release Management
      • Coordination of new releases
      • One Release Manager
      • Several Release Assistants
    • New Maintainer
      • The Debian Account Manager
      • The NM Front Desk
      • Application Managers
  • Teams in Debian
    • Policy
      • Guidelines for the integration of packages
    • Legal
      • Decide whether a license can be regarded as a Free Software license
  • Debian's Infrastructure
    • Open, solid and does not rely in third parties => key for success
    • There is however debian-private
    • What do you think about this?
    • Amazing case study for GSD
    • http://www.debian.org/devel/developers.loc
    • Very well organised and set up
  • Debian's Infrastructure
    • The Mailing lists
      • +150 mailing lists
      • debian-user (different languages)
      • debian-devel
      • debian-announce
      • debian-security-announce
  • Debian's Infrastructure
    • IRC
      • irc.debian.org
      • #debian
    • Bug Tracking System
      • Maintainers receive bug reports
      • It links reporters and maintainers in a two-way fashion
  • Debian's Infrastructure
    • Package Tracking System
      • All kinds of information about packages at one spot
      • Dependencies, bugs, source code...
      • http://packages.debian.org/stable/shells/bash
  • Joining Debian
    • Non-developers can
      • Maintain packages through a sponsor
      • Create or review translations
      • Create or improve documentation
      • Help maintain the website
      • Help with handling bugs
      • Be an active member of a sub-project
  • New Maintainer Process
    • The NM Process is part of the QA
    • Will you have time?
    • Will you have the skills?
    • Have you been involved lately?
    • The whole process takes very long and is really strict
    • Do you think this is really necessary?
  • New Maintainer Process
    • Check Debian's philosophy
    • Identity verification (key signed)
    • Skills and experience (sponsor)
    • Test of knowledge about Debian
    • Enough free time and commitment
    • Find an advocate
    • Fill the application form