One of the lessons O'Reilly learned was that the original code wasn't "modular" enough. There are some bloggers who would be willing to adopt some parts of the code but not all of them. For example, many would agree with O'Reilly's advocacy of taking responsibility for your words -- but not with disallowing anonymous posts. Indeed, there are certain situations in which permitting anonymous posts can be a good idea, though the ability to post anonymously can also lead to the rude behavior that is all too common in some parts of the web.
Here are the original seven points of Tim O'Reilly's proposed Blogger Code of Conduct.
- Take responsibility not just for your own words, but for the comments you allow on your blog.
- Label your tolerance level for abusive comments.
- Consider eliminating anonymous comments.
- Ignore the trolls.
- Take the conversation offline, and talk directly, or find an intermediary who can do so.
- If you know someone who is behaving badly, tell them so.
- Don't say anything online that you wouldn't say in person.
The modularized version of the Blogger's Code actually lists ten modules. While many are the same as those listed here, it also includes "Do no harm," "Encourage enforcement of terms of service," "Keep our sources private" and others. Some of the modules are restatements of the ideas listed above, and may cover more than one idea.
There is also an alternate version of the Blogger's Code of Conduct on the wiki site (http://blogging.wikia.com/wiki/Alternate_Code_of_Conduct), which is based on the Gentoo Linux code of conduct. Another proposal suggests a "scale of conduct" rather than a blogger's code, with a draft scale that looks like this:
- No Holds Barred -- anything goes at the risk of legal intervention.
- Raw Meat -- no explicit death threats, but ad hominae permitted.
- Robust -- no ad hominae, but mild abuse permitted.
- Civil -- no abuse, but vigorous debate permitted.
- Text Book -- only proven facts, with scholarly opinion permitted.
Debate about the code and its elements is likely to be ongoing. In the next sections I'll discuss the code itself in greater detail and look at some of the issues it potentially raises.
No comments:
Post a Comment