caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Collin Monahan" <cmonahan@fame.com>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] Newbie list
Date: Thu, 13 Sep 2001 12:29:04 -0400	[thread overview]
Message-ID: <000401c13c71$344654c0$f54258c0@CONSULTING2000P> (raw)
In-Reply-To: <20010913172414.D2677@chopin.ai.univie.ac.at>


As a newbie my opinion is that I'd be more likely to post questions to a
second list than here with one list. Even though when I asked questions
before I felt quite welcomed.
Collin Monahan

-----Original Message-----
From: owner-caml-list@pauillac.inria.fr
[mailto:owner-caml-list@pauillac.inria.fr] On Behalf Of Markus Mottl
Sent: Thursday, September 13, 2001 11¤24
To: Alan Schmitt; Frank Atanassow
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Newbie list


On Thu, 13 Sep 2001, Alan Schmitt wrote:
> We did this for the enlightenment lists, because some developers were 
> getting bothered with all the newbie questions
[snip]

Your experience seems to indicate that we should try out creating a
specific list for newbies. It's probably to the better for all sides:
newbies won't be afraid of joining this list and asking "stupid"
questions (only unasked questions are stupid, IMHO), and more
experienced developers won't get distracted while discussing more
hard-core issues.

On Thu, 13 Sep 2001, Frank Atanassow wrote:
> I might subscribe to the newbies list and answer questions myself. The

> reason I want a separate newbie list is that I can unsubscribe from it

> when I get busy without missing the other discussions and 
> announcements.

Though I guess that many people use mail clients with threading
capabilities, it still seems better to have separate lists: this way one
could automatically sort mails from both lists into different folders
and thus prevent cluttering one's inbox (or caml-list inbox). When I
don't have time to answer basic questions, I'd simply not look at the
caml-newbie folder. It's difficult to resist, when all mails go to the
same folder (I am not very disciplined ;) ...

Regards,
Markus Mottl

-- 
Markus Mottl                                             markus@oefai.at
Austrian Research Institute
for Artificial Intelligence                  http://www.oefai.at/~markus
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ:
http://caml.inria.fr/FAQ/ To unsubscribe, mail
caml-list-request@inria.fr  Archives: http://caml.inria.fr

-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-09-13 16:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 12:49 Frank Atanassow
2001-09-13 13:19 ` Markus Mottl
2001-09-13 14:35   ` Alan Schmitt
2001-09-13 15:24     ` Markus Mottl
2001-09-13 16:29       ` Collin Monahan [this message]
2001-09-14 14:20         ` Felix Terkhorn
2001-09-13 15:03   ` Frank Atanassow
2001-09-13 18:32 ` Mike Leary
2001-09-14  5:22   ` Alan Schmitt
2001-09-14  6:40   ` Sven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000401c13c71$344654c0$f54258c0@CONSULTING2000P' \
    --to=cmonahan@fame.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).