summaryrefslogtreecommitdiff
path: root/community/communication.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2008-03-25 09:58:09 +0100
committerThomas Schwinge <tschwinge@gnu.org>2008-03-25 10:01:33 +0100
commitc900e59dd3b1b34ff68c738a685d4652b2ab12b2 (patch)
tree7b8d7c5aff63124952ca9a8dcf7a8d3a566caa45 /community/communication.mdwn
parent8980716542d70597ea2659dfd52cd93d7057db6b (diff)
community/communication: Discuss matter in public.
Diffstat (limited to 'community/communication.mdwn')
-rw-r--r--community/communication.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/community/communication.mdwn b/community/communication.mdwn
index f5867bf4..ba16f6a5 100644
--- a/community/communication.mdwn
+++ b/community/communication.mdwn
@@ -16,6 +16,17 @@ possible.
The two key resources most often used for communication are the Debian and GNU
[[mailing_lists]], as well as [[IRC]].
+These are measures of communication that work (compared to, e.g., a one-to-one
+telephone call) one-to-many. It is important to not send email only to a
+single person, but in a way that several people can see your questions and
+reasonings. (There are exceptions, of course. Administrative stuff usually
+need not be discussed in public.) It often happens that -- if you send email
+only to a single developer -- someone is unavailable for some days and can't
+answer to your email, but another person could easily have done so. Also, when
+discussing matters in public, others can learn from it (while reading, or
+eventually even taking part in the discussions), transform the results into
+real documentation, etc. Efficient using of scarce resources.
+
If you're interested in keeping up with current events and taking part in
discussions, you'll want to join the [[mailing_lists/bug-hurd]] mailing list or
have a look at its [archives](http://lists.gnu.org/archive/html/bug-hurd/).