Debian -->
TOC linked  toc  Full Text scroll  EPUB epub  PDF portrait pdf  PDF landscape pdf  ODF/ODT  odt    A-Z  Document Manifest  @
<< previous TOC next >>
< ^ >

Debian Constitution

Constitution for the Debian Project (v1.3)

[Prefix]

1. Introduction

2. Decision-making bodies and individuals

2.1 General rules

3. Individual Developers

3.1 Powers
3.2 Composition and appointment
3.3 Procedure

4. The Developers by way of General Resolution or election

4.1 Powers
4.2 Procedure

5. Project Leader

5.1 Powers
5.2 Appointment
5.3 Procedure

6. Technical committee

6.1 Powers
6.2 Composition
6.3 Procedure

7. The Project Secretary

7.1 Powers
7.2 Appointment
7.3 Procedure

8. The Project Leader's Delegates

8.1 Powers
8.2 Appointment
8.3 Procedure

9. Assets held in trust for Debian

9.1 Relationship with Associated Organizations
9.2 Authority
9.3 Trusted organisations

10. A. Standard Resolution Procedure

10.1 A.1. Proposal
10.2 A.1 Discussion and Amendment
10.3 A.2. Calling for a vote
10.4 A.3. Voting procedure
10.5 A.4. Withdrawing resolutions or unaccepted amendments
10.6 A.5. Expiry
10.7 A.6. Vote Counting

11. B. Use of language and typography

Metadata

SiSU Metadata, document information

Manifest

SiSU Manifest, alternative outputs etc.

Debian Constitution

Constitution for the Debian Project (v1.3)

Debian Project

copy @ Debian

Debian Constitution

Constitution for the Debian Project (v1.3)

7. The Project Secretary

1. Takes votes amongst the Developers, and determines the number and identity of Developers, whenever this is required by the constitution.

2. Can stand in for the Leader, together with the Chairman of the Technical Committee.

If there is no Project Leader then the Chairman of the Technical Committee and the Project Secretary may by joint agreement make decisions if they consider it imperative to do so.

3. Adjudicates any disputes about interpretation of the constitution.

4. May delegate part or all of their authority to someone else, or withdraw such a delegation at any time.

141

The Project Secretary is appointed by the Project Leader and the current Project Secretary.

If the Project Leader and the current Project Secretary cannot agree on a new appointment, they must ask the Developers by way of General Resolution to appoint a Secretary.

If there is no Project Secretary or the current Secretary is unavailable and has not delegated authority for a decision then the decision may be made or delegated by the Chairman of the Technical Committee, as Acting Secretary.

The Project Secretary's term of office is 1 year, at which point they or another Secretary must be (re)appointed.

146

The Project Secretary should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Developers.

When acting together to stand in for an absent Project Leader the Chairman of the Technical Committee and the Project Secretary should make decisions only when absolutely necessary and only when consistent with the consensus of the Developers.

TOC linked  toc  Full Text scroll  EPUB epub  PDF portrait pdf  PDF landscape pdf  ODF/ODT  odt    A-Z  Document Manifest  @
<< previous TOC next >>
< ^ >

SiSU

Output generated by SiSU 2.0.5 2010-03-26 (2010w12/5)
SiSU Copyright © Ralph Amissah 1997, current 2010. All Rights Reserved.
SiSU is software for document structuring, publishing and search,
www.jus.uio.no/sisu and www.sisudoc.org
w3 since October 3 1993 ralph@amissah.com

SiSU using:
Standard SiSU markup syntax,
Standard SiSU meta-markup syntax, and the
Standard SiSU object citation numbering and system, (object/text positioning system)
Copyright © Ralph Amissah 1997, current 2010. All Rights Reserved.

GPLv3

SiSU is released under GPLv3 or later, ‹http://www.gnu.org/licenses/gpl.html

SiSU, developed using Ruby on Debian/Gnu/Linux software infrastructure, with the usual GPL (or OSS) suspects.
Better - "performance, reliability, scalability, security & total cost of ownership" [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libré.
Get With the Future Way Better!

SiSU search:





SiSU


The Wealth of Networks - How Social Production Transforms Markets and Freedom

Yochai Benkler

2006


Free Culture - How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity

Lawrence Lessig

2004


CONTENT - Selected Essays on Technology, Creativity, Copyright and the Future of the Future

Cory Doctorow

2008


Free As In Freedom - Richard Stallman's Crusade for Free Software

Sam Williams

2002


Two Bits - The Cultural Significance of Free Software

Christopher Kelty

2008


The Cathedral & the Bazaar - Musings on Linux and Open Source by an Accidental Revolutionary

Erik S. Raymond

1999


Free For All - How Linux and the Free Software Movement Undercut the High Tech Titans

Peter Wayner

2002


Little Brother

Cory Doctorow

2008


Free Software Foundation - FSF