Minutes of the MC meeting on March 28th

[Søren Hansen]

We had an extra call on Friday, March 28th due to lack of quorum on
Wednesday.

In attendance were:
soren (Soren Hansen)
dholbach (Daniel Holbach)
persia (Emmet Hikory)
geser (Michael Bienia)

Absent:
nixternal (Richard Johnson)

The agenda:

1. Getting a general procedure for problematic behaviour in the MOTU team.
2. Update on process for granting Membership separately from MOTU.

Ad 1: 
Each member of the MC was previously asked to look at the whole process
around Kmos. Only persia had managed to put this into writing, so this
formed the discussion.

We identified the following issues with the handling of the Kmos issue:
 * Everything took too long. Ideally there should be clear timeframes
   for responses and activities.
 * Reporting: The lack of response by LP to the limitation was never
   made public.
 * Policy: The (successful) disciplinary action was not turned into
   approved policy.
 * Lack of role definition: It was not always clear to all
   participants when something was an MC statement vs. a personal
   statement by someone who happened to be a member of MC (Call minutes
   help).                                                          
 * Too much responsibility on too few hands.

We agreed on the following general process for handling issues in the
MOTU community:

Process for handling dispuptive individuals:

1) People experiencing disruption should engage in private or peer
discussion with the individual causing disruption to resolve the
issue.

2) If the above is insufficient, the matter should be raised to the MC
as a request for resolution of a dispute.  MC will assign one or more
members to mediate the discussion and attempt to resolve the issue.

3) If the above is insufficient, MC will call for comments on the
issue to the community, seeking feedback on whether the disruption is
considred general or personal by the community.  Note that any of the
accused, the accuser, or the assigned MC member(s) may determine that
the mediation was insufficnet, or is not making progress.

4) In the presence of significant agreement that the disruption is
general, MC will appoint a supervisory team responsible for
supervising the individual accused of disruptive behaviour for a
period of two weeks (subject to extensions due to holidays, release
churns, or similar).

5) Based on the feedback from the supervisors, the MC may take any or
all of the following actions:

A)  Request that the individual continue the good behaviour
demonstrated during supervision
B)  Request that the individual cease participation in Ubuntu Development
C)  Make a request to the TB for review and possible loss of upload privileges.
D)  Make a request to the CC for review and possible loss of membership

The MC's role in this process will be one of coordination, and actually
enforcing the decisions will be up to:

 * IRC ops + IRC council in case of #ubuntu-motu.

 * The bugcontrol team in case of Launchpad.

 * The ML moderators (currently a subset of the MC) in case of the
   ubuntu-motu mailing list.

nixternal volunteered to turn this into into a wiki page shortly.

Ad 2: Deferred until next MC call due to loss of quorum.

-- 
Soren Hansen               | 
Virtualisation specialist  | Ubuntu Server Team
Canonical Ltd.             | http://www.ubuntu.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/motu-council/attachments/20080401/ea4d03c0/attachment.pgp