Updating the DebConf committee delegation

["Chris Lamb " <lamby@debian.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Developers,

This email updates the delegation for the DebConf committee. As an
adjunct text, the only two changes should be:

  - appoint at least one DebConf committee member
  + appoint at least one DebConf team member

… and:

  - Jonathan Cristopher Carter
  + Jonathan Cristopher Carter <jcc>

The previous delegation may be found here:

  https://lists.debian.org/debian-devel-announce/2017/01/msg00003.html


DebConf Committee
=================

I hereby appoint the following developers as members of the DebConf
Committee:

- - Jonathan Christopher Carter 
- - Daniel Lange 
- - Lucas Nussbaum 
- - Dider Raboud 
- - Stefano Rivera 

The delegation is not time-limited. It will be effective until further
changes by present or future DPLs.

Task Description
================

1) Bid Process

The DebConf Committee serves as an institutional memory of DebConf.
As such, it is in the best position to review proposals. More
specifically, the DebConf Committee is responsible of the following
tasks:

- - make final decisions about who will organize DebConf;

- - define a set of goals to fulfill to ensure a successful DebConf;

- - appoint at least one DebConf team member that will mentor the
  newly selected bid team until DebConf is held.

In order to reach a final decision in the bid process, the DebConf
Committee is highly invited to take input from the wider Debian
community.

In the absence of mentors, DebConf Committee members are expected to
help selected teams to reach their goals.

2) Mentorship of DebConf teams

The appointed mentors are expected to:

- - help the team in establishing appropriate structures and decision
  mechanisms;

- - advise the team and share their experience of DebConf organization;

- - monitor the progress of DebConf organization and ensure that the
  defined team structure and decision-making processes remain
  functional and sufficiently efficient to ensure a successful
  DebConf.

3) Decision-making process

As last resort, the DebConf Committee can override specific decisions
in the context of DebConf organization. The Committee should not take
any decision until efforts to resolve it via consensus have been tried
and failed.

This special power should be left for extreme cases, e.g. when a
decision taken by the DebConf organizers is perceived by the DebConf
Committee as creating serious risks for the organization of DebConf or
for Debian.

Votes by members of the committee to appoint a mentor or to override
specific decisions of DebConf teams are made public. In order to avoid
dead-lock situations, the DebConf Committee appoints a Chair. The
latter has a casting vote.


Regards,

- --
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlu819UACgkQHpU+J9Qx
Hli/VA/+LkAk9CjTTN192mGaG9/5vvqqVAmnvaeFYPGAVK93+jkYjqj5hGWgS4lL
5vX99qthiCb9uppc2s9bqarbao2LL2HKQg7lMSdM6XSfDXp56cfZpFZ3vOLqCv+h
yoZjszgaTAGE2wYTrAPi1HFlyLmkPaNxJhWmiDCF2wUl1ZnXUyMJXAmx6CwzbOcQ
U6o0zMoU8UVlHXfWW6IBBg0+Ip0jEnFTIYAUE+G3S1CcG7W/pd4+v1tEEYZvWIPb
7bgGbfbzzbELJ8MgxThZKDbNV60NrA1TwNVFsnSvRWGf7rXm/h+7gOHlefxNC3Ro
6FuL5Sybrbt0YzanIPY3bOIU2Al0BTj8gbR2K/3QUzHu6yg0AuagNU8rOA34Gk7z
KLtVjYwQQdE5w8LjAtnrKDoYDW+LrA42+yFJxGP5vYnwbaiDIeGIHLxmAVeKZTkv
EHhs0XSTmWW6x2BOEv0PgxjoA22LTHKo5ixOir3BthmdqCqWK9bkbpDy+BDY4qYQ
8YN6oRuxoJrMVzlYcf4HXjOrbAtarGa/IgPqZQC91jMEYnNfLbCJ5mVvdtM8H7LP
fT0CqTB4P9GoXPgMEKezi/43WrUad5Qz+u1CzT2s94jffQPw48/BJ8ekCqKNQ9TV
UCeu3iX6Eam5xjpUXzn4Xl6QLDZi62s5mR8O3nX/c5Xm6yoqnLA=
=ZKUi
-----END PGP SIGNATURE-----