caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Stefano Zacchiroli <zack@upsilon.cc>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OSR] Standard syntax extensions ? - voting
Date: Fri, 25 Apr 2008 00:16:11 +0800	[thread overview]
Message-ID: <20080424161611.GA23787@aquarium.takhisis.invalid> (raw)
In-Reply-To: <1209052182.6180.35.camel@Blefuscu>

On Thu, Apr 24, 2008 at 05:49:42PM +0200, David Teller wrote:
> * which syntax extensions do you use so often that you consider they
> should be part of the language ?

Thanks for raising this up again.

I'm not going to make my nominations with this post, but rather a
methodological suggestion. Mailing lists are good to discuss things, but
not for deciding; they usually work for that when one solutions can be
arguably proven better than the others. In our case I fear that the
thread can diverge.

What about the following 2 phases:
1) prepare a list of nominations, maybe as a page on cocanwiki
2) vote on them using a Doodle poll

Of course, since we are a do-ocracy and you are doing the work, the vote
will be by no mean constraining; but I assume you are interested in
collecting the desire of the community, otherwise you wouldn't have
started this thread in the first place.

I think that a wiki page + a vote can give us they same feedback you
could have got on the list, and we will avoid tons of AOL messages :-)

Just my 0.02€
Cheers.

-- 
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org}  -<%>-  http://upsilon.cc/zack/
(15:56:48)  Zack: e la demo dema ?    /\    All one has to do is hit the
(15:57:15)  Bac: no, la demo scema    \/    right keys at the right time


  parent reply	other threads:[~2008-04-24 16:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 15:49 [OSR] Standard syntax extensions ? David Teller
2008-04-24 15:52 ` [Caml-list] " John Whitington
2008-04-25  8:22   ` Richard Jones
2008-05-01  7:45     ` Richard Jones
2008-04-24 16:16 ` Stefano Zacchiroli [this message]
2008-04-25 15:15   ` [Caml-list] [OSR] Standard syntax extensions ? - voting David Teller
2008-04-26  0:16     ` Stefano Zacchiroli
2008-04-24 16:41 ` [Caml-list] [OSR] Standard syntax extensions ? Martin Jambon
2008-04-24 17:02   ` Jon Harrop
2008-04-24 20:53     ` Berke Durak
2008-04-25  8:24       ` Richard Jones
2008-04-25 16:59         ` Berke Durak
2008-04-25 17:31           ` Gerd Stolpmann
2008-04-25 17:38           ` Richard Jones
2008-04-25 10:33       ` Andrej Bauer
2008-04-25 15:32     ` David Teller
2008-04-24 17:05 ` Dario Teixeira
2008-04-25 13:57   ` Peng Zang
2008-04-25 15:04     ` David Teller
2008-04-25 16:11       ` Peng Zang
2008-04-25 20:37 ` Arthur Chan
2008-04-26  7:41   ` Richard Jones
2008-04-26  7:53     ` Till Crueger
2008-04-26 21:32       ` Arthur Chan
2008-04-27  6:58         ` Andrej Bauer
2008-04-27 14:14           ` Christopher L Conway
2008-04-27 17:41         ` [Caml-list] " David Teller
2008-04-27 17:44       ` David Teller
2008-04-25 22:25 ` Mike Lin

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=20080424161611.GA23787@aquarium.takhisis.invalid \
    --to=zack@upsilon.cc \
    --cc=caml-list@yquem.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).