caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: michaelgrunewald@yahoo.fr (Michaël Grünewald)
To: "Bünzli Daniel" <daniel.buenzli@erratique.ch>
Cc: caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] [OSR] Exceptionless error management
Date: Wed, 06 Feb 2008 09:45:43 +0100	[thread overview]
Message-ID: <86zluexyko.fsf@Llea.celt.neu> (raw)
In-Reply-To: <9A13D5E1-E455-4019-B0BA-D8D7DD4CE49E@erratique.ch> (=?iso-8859-15?Q?=22B=FCnzli?= Daniel"'s message of "Tue\, 5 Feb 2008 11\:26\:00 +0100")

Bünzli Daniel <daniel.buenzli@erratique.ch> writes:

> Le 5 févr. 08 à 11:12, Vincent Hanquez a écrit :
>
>> looking at the page, I find a proposal (beginning), and a lots of
>> people
>> disaggreeing at the end.
>
> I agree with this I think it should be moved to a "rejected proposals"
> section. When I find some time I will add a preamble explaining why it
> was rejected.

Although it did not meet a consensus, the proposal might still be
useful. Developpers should be able to claim at the beginning of a file
or in their projet's documentation:

 ``We adhere to conventions described in PAPER, regarding
   exceptionless error reporting.''

The benefit from doing so, is that it helps having coherent code
(users can report that parts of the code break proposal, etc.).

So ``rejected proposals'' sounds a bit pessimistic to me, we could
have four sections (or even more):
 1. proposals (for discussion);
 2. recommendations (proposals that met a large success);
 3. options (proposals that did not met a large success, or are not
      intended for large audience, but are still a useful reference
      because they are adhered to in some code);
 4. attic (proposals that do not fit in the first three, maybe because
    they have been rejected).

(The vote mechanism should then only apply to publications in 2.)

By the way the title of your proposal is informative about the problem
you are giving a possible answer, but it do not give a word about the
solution. I think it should, beacuse discussion on the page show that
there exist(?) other strategies than the one you describe.
-- 
All the best,
Michaël


  parent reply	other threads:[~2008-02-06  8:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:55 Bünzli Daniel
2008-01-31  9:57 ` [Caml-list] " Till Varoquaux
2008-01-31 11:01   ` Bünzli Daniel
2008-01-31 14:09     ` Andrej Bauer
2008-01-31 14:16       ` Michael Ekstrand
2008-01-31 19:28         ` David Teller
2008-01-31 19:59           ` Michael Ekstrand
2008-01-31 20:05           ` blue storm
2008-01-31 20:03       ` Bünzli Daniel
2008-01-31 20:25         ` David Teller
2008-01-31 20:40           ` David Teller
2008-01-31 21:16           ` Bünzli Daniel
2008-01-31 21:31             ` David Teller
2008-01-31 21:35           ` Jon Harrop
2008-01-31 22:01           ` Christophe Raffalli
2008-02-01  7:27         ` Michaël Grünewald
2008-02-01  7:47           ` Bünzli Daniel
2008-02-01 10:50             ` Till Varoquaux
2008-02-01 11:31               ` Bünzli Daniel
2008-02-01 15:59                 ` Vincent Hanquez
2008-02-01 18:37                   ` Bünzli Daniel
2008-02-01 19:43                     ` Vincent Hanquez
2008-02-01 16:04                 ` David Allsopp
2008-02-01  8:31 ` David Teller
2008-02-01 12:19   ` Yaron Minsky
2008-02-05 10:00 ` David Teller
2008-02-05 10:12   ` Vincent Hanquez
2008-02-05 10:26     ` Bünzli Daniel
2008-02-05 11:06       ` Vincent Hanquez
2008-02-05 13:46         ` Jon Harrop
2008-02-05 11:36       ` Frédéric van der Plancke
2008-02-06  8:45       ` Michaël Grünewald [this message]
2008-02-08 13:09         ` Bünzli Daniel
2008-02-05 14:12     ` David Teller
2008-02-11  8:12 ` David Teller
2008-02-11  9:09   ` Bünzli Daniel

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=86zluexyko.fsf@Llea.celt.neu \
    --to=michaelgrunewald@yahoo.fr \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).