/[gentoo]/xml/htdocs/proj/en/glep/glep-0007.txt
Gentoo

Contents of /xml/htdocs/proj/en/glep/glep-0007.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (show annotations) (download)
Mon Nov 10 19:03:31 2003 UTC (11 years, 1 month ago) by g2boojum
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +3 -3 lines
File MIME type: text/plain
Marked GLEPs 4, 6, and 7 as "final".

1 GLEP: 7
2 Title: New ombudsman position
3 Version: $Revision: 1.3 $
4 Last-Modified: $Date: 2003/07/28 18:54:42 $
5 Author: Grant Goodyear <g2boojum@gentoo.org>
6 Status: Final
7 Type: Standards Track
8 Content-Type: text/x-rst
9 Created: 6-Jul-2003, 28-Jul-2003
10 Post-History:
11
12
13 Abstract
14 ========
15
16 This GLEP proposes that we extend the current proposed management
17 structure by adding a position of Ombudsman that would fall under
18 devrel, qa, and pr. An ombudsman is one who has been assigned to
19 *impartially* investigate complaints and settle disputes.
20
21 Motivation
22 ==========
23
24 Given the impressive numbers of both Gentoo developers and users, it is
25 inevitable that there will be occasional clashes between developers and
26 managers, developers and developers, and developers and users. Right
27 now there is no mechanism to prevent such disputes from escalating out
28 of control.
29
30 Specification
31 =============
32
33 One developer (and one backup) will be appointed as ombudsmen. This
34 positions should be far from a full-time job. It would appear as part
35 of the devrel, qa, and pr projects (inasmuch as qa and pr both involve
36 developer-user relations). Infrastructure requirements are an
37 ombudsman.gentoo.org web page and a ombudsman@gentoo.org e-mail
38 alias.
39
40 Rationale
41 =========
42
43 One traditional method (circa early 1800s in Sweden, apparently [#RIT]_)
44 for managing disputes is to have an impartial individual whose job it
45 is to investigate complaints and mediate settlements. A quick search
46 on Google [#GOOGLE]_ reveals numerous government agencies, universities,
47 and industries that employ official ombudsmen. The key requirement for
48 an ombudsman to be effective is support from management and trust from
49 users and developers -- the ombudsmen must be considered by all to be
50 reasonably impartial.
51
52 Backwards Compatibility
53 =======================
54
55 No conflicts.
56
57
58
59 References
60 ==========
61
62 .. [#RIT] http://www.rit.edu/~022www/defhis.shtml
63
64 .. [#GOOGLE] http://www.google.com
65
66
67
68 Copyright
69 =========
70
71 This document has been placed in the public domain.

  ViewVC Help
Powered by ViewVC 1.1.20