From: Peter Gregory <Peter.Gregory@cis.strath.ac.uk>
To: caml-list@yquem.inria.fr
Subject: OSR - Three Admin Questions
Date: Thu, 06 Mar 2008 12:51:15 +0000 [thread overview]
Message-ID: <47CFE8C3.7000108@cis.strath.ac.uk> (raw)
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?
3. How do we decide on a consensus for an OSR proposal?
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.
Regards,
Peter.
next reply other threads:[~2008-03-06 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 12:51 Peter Gregory [this message]
2008-03-06 14:59 ` Sylvain Le Gall
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=47CFE8C3.7000108@cis.strath.ac.uk \
--to=peter.gregory@cis.strath.ac.uk \
--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