From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: OSR - Three Admin Questions
Date: Thu, 6 Mar 2008 14:59:04 +0000 (UTC) [thread overview]
Message-ID: <slrnft01lo.tll.sylvain@gallu.homelinux.org> (raw)
In-Reply-To: <47CFE8C3.7000108@cis.strath.ac.uk>
On 06-03-2008, Peter Gregory <Peter.Gregory@cis.strath.ac.uk> wrote:
> Hi all,
>
> I've been following all of the OSR discussion with great interest. I've
> currently got three questions about it though:
>
> 1. How is delivery of our "community ocaml" going to work?
>
> 2. Sadly I couldn't make the Paris meet, are there going to be followup
> meetings?
Maybe next year. It will depend on people who are interested that this
meeting happen again.
>
> 3. How do we decide on a consensus for an OSR proposal?
>
Sometimes ago, i propose to put the OSR on vote at a certain date. The
answer was something like: "better use the IEEE (or W3C, don't remember)
way to do: talk until a consensus happens".
> Personally, I think the answers to these questions are linked. A system
> that I would like to see is something like: a community release every
> six months, meetings a couple of months before release, final decisions
> made about which suggestions make the release decided in the meeting. I
> think it would be better to decide in a face-to-face setting which
> proposals are best, as a mailing list just leads to endless forking of
> conversation and drift from original topics.
>
This could be an idea. I am not sure that people can end up with a
solution however -- even with a meeting face to face. To my mind a
solution like "put everything there (including test + kind of build
system), if it builds and pass all the test, this is good for release".
If something fails, just remove it. If a lot of things fails, don't
release.
Regards,
Sylvain Le Gall
prev parent reply other threads:[~2008-03-06 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 12:51 Peter Gregory
2008-03-06 14:59 ` Sylvain Le Gall [this message]
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=slrnft01lo.tll.sylvain@gallu.homelinux.org \
--to=sylvain@le-gall.net \
--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