Akademy/2013/ConflictResolution

< Akademy‎ | 2013
Revision as of 17:11, 12 July 2013 by Valoriez (talk | contribs) (Created page with "After 15 years of KDE, our community is now one of the largest in the open source world. Sadly, our problems have scaled just as much; but our processes to deal with them didn...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

After 15 years of KDE, our community is now one of the largest in the open source world. Sadly, our problems have scaled just as much; but our processes to deal with them didn't.

In this BOF we want to address this problem by establishing new ways to deal with conflicts in our community. We will be looking at defining a process to deal with violations of our code of conduct and how we can discourage such activities without hampering constructive criticism.

This session is mainly aimed at mailing list, and forum moderators and IRC channel operators, but everyone interested in improving communication within KDE is welcome to join.

Primary focus for listowners and Chanops will be prevention. Only once their most important efforts to cool the discussions and channel the discussion into productive conversations have failed, do CoC enforcements begin.

What procedures do we follow once these first-line efforts have failed?

When should you call in the Community Working Group (CWG), and how does one do that?

What can the CWG do? Should this role expand to "enforcement"?

What is the role of the e.V. Board?


Content is available under Creative Commons License SA 4.0 unless otherwise noted.