Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 185572 - As the proctors no longer exist the code of conduct needs an update
Summary: As the proctors no longer exist the code of conduct needs an update
Status: RESOLVED FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Project-specific documentation (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Donnie Berkholz (RETIRED)
URL: http://www.gentoo.org/proj/en/council...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-16 19:00 UTC by Roy Bamford
Modified: 2008-11-20 17:04 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roy Bamford gentoo-dev 2007-07-16 19:00:58 UTC
Consequences

Disciplinary action will be up to the descretion of the proctors. What is a proctor? A proctor is an official charged with the duty of maintaining good order. If discplinary measures are taken and the affected person wishes to appeal, appeals should be addressed to the Gentoo Council via email at council@gentoo.org. To prevent conflicts of interest, Council members may not perform the duties of a proctor.

If you perceive a breach of the Code of Conduct guidelines, let the proctors know. Though they will also be watching many of the public mediums for any problems, they can not be expected to catch everything.

The proctors will attempt to resolve the problem by talking to involved parties, potentially issuing warnings if appropriate. If the problem repeats itself, there are various options open to the proctors, including temporary or permanent suspension of a person's ability to post to mailing lists, removal of Bugzilla access, or in more severe cases suspension of developer privileges. Any action of this sort will require consensus from at least three proctors. 

Reproducible: Always

Steps to Reproduce:
1.read the description above
2.
3.

Actual Results:  
The document refers to a dead project

Expected Results:  
None

See the logs of the council meetings of 14 June and 12 July 2007
Comment 1 Ferris McCormick (RETIRED) gentoo-dev 2007-10-02 13:01:48 UTC
Council owns this document.  Do they wish to assign it to devrel?
Comment 2 Christian Heim (RETIRED) gentoo-dev 2007-11-01 21:29:03 UTC
Assigning to council till they figure things out.
Comment 3 Doug Goldstein (RETIRED) gentoo-dev 2008-10-21 20:06:09 UTC
I'm in favor of assigning this responsibility to devrel.
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2008-10-23 20:16:25 UTC
Devrel: Please provide a patch to http://www.gentoo.org/proj/en/council/coc.xml to reflect how it's now being enforced.
Comment 5 Donnie Berkholz (RETIRED) gentoo-dev 2008-10-25 08:51:13 UTC
Also see http://archives.gentoo.org/gentoo-council/msg_2c580204c3651365ab945922c5561fa5.xml for a patch Jim Ramsay (lack) posted.
Comment 6 Doug Goldstein (RETIRED) gentoo-dev 2008-10-27 14:47:32 UTC
Looks good. Let's get it applied and close out this bug.
Comment 7 Doug Goldstein (RETIRED) gentoo-dev 2008-11-13 20:25:05 UTC
jmbsvicetto will discuss this with the other members of devrel to get this resolved.
Comment 8 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2008-11-16 03:14:05 UTC
We've discussed this amongst ourselves and agreed with applying lack's patch to the CoC doc.
I'm reassigning this bug back to Donnie as he requested.
Comment 9 Donnie Berkholz (RETIRED) gentoo-dev 2008-11-20 17:04:29 UTC
Applied, thanks!