From b9fc7edad79b044ee557332eba48789380bad5e7 Mon Sep 17 00:00:00 2001
From: Dave Abrahams Email discussion is the tie that binds boost members together into a community.
-If the discussion is stimulating and effective, the community thrives. If
+If the discussion is stimulating and effective, the community thrives. If
the discussion degenerates into name calling and ill will, the community withers
and dies.Boost Discussion Policy
Acceptable topics
@@ -41,24 +41,25 @@ will let you know.
Prohibited behavior will not be tolerated. The moderators will ban +
Prohibited behavior will not be tolerated. The moderators will ban postings by abusers.
Personal insults, argument for the sake of argument, and all the other behaviors which fall into the "flame war" category are -prohibited. Discussions should focus on technical arguments, not the +prohibited. Discussions should focus on technical arguments, not the personality traits or motives of participants.
Attacks on third parties such as software vendors, hardware vendors, or any -other organizations, are prohibited. Boost exists to unite and serve the +other organizations, are prohibited. Boost exists to unite and serve the entire C++ community, not to disparage the work of others.
Does this mean that we ban the occasional complaint or wry remark about a -troublesome compiler? No, but be wary of overdoing it.
+troublesome compiler? No, but be wary of overdoing it.Discussions which stray from the acceptable topics are strongly discouraged. While off-topic posts are often well meaning and not as individually corrosive @@ -66,7 +67,7 @@ as other abuses, cumulatively the distraction damages the effectiveness of discussion.
In addition to technical skills, Boost members value collaboration, -acknowledgement of the help of others, and a certain level of politeness. Boost +acknowledgement of the help of others, and a certain level of politeness. Boost membership is very international, and ranges widely in age and other characteristics. Think of discussion as occurring among colleagues in a widely read forum, rather than among a few close friends.
@@ -83,7 +84,7 @@ Re-read your message before submitting it.Apply social engineering to prevent heated technical discussion from degenerating into a shouting match.
Avoid Parkinson's Bicycle Shed. Parkinson described a committee formed -to oversee design of an early nuclear power plant. There were three agenda +
Avoid Parkinson's Bicycle Shed. Parkinson described a committee formed +to oversee design of an early nuclear power plant. There were three agenda items - when to have tea, where to put the bicycle shed, and how to -ensure nuclear safety. Tea was disposed of quickly as trivial. +ensure nuclear safety. Tea was disposed of quickly as trivial. Nuclear safety was discussed for only an hour - it was so complex, scary, and technical that even -among experts few felt comfortable with the issues. Endless days were then +among experts few felt comfortable with the issues. Endless days were then spent discussing where to put the bicycle shed (the parking lot would be a modern equivalent) because everyone understood the issues and felt comfortable discussing them.
Revised 24 September, 2001 +
Revised 10 October, 2001