From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: SC confidentiality
Date: Wed, 22 Nov 2000 05:25:00 -0000 [thread overview]
Message-ID: <10011221325.AA13910@vlsi1.ultra.nyu.edu> (raw)
On the other hand, there is some value in having the opportunity to
discuss delicate issues in confidence. In my experience, which is
very limited relative to a lot of the more senior SC members, there
are no technical dicussions -- almost all discussions are about things
like possible inappropriate behavior on the part of individuals,
policies for dealing with copyright assignment paperwork, strategies
for handling events that might cause confusion about GCC or the GNU
Project, and so forth.
I agree that a free and open exchange of ideas requires
confidentiality of those discussions. However, I think a lot of the
concerns that were expressed recently could be dealt with by having
the SC prepare a summary of the discussions leading to each
possibly-contentious decision including, when appropriate, which
people took which views if the decision was not unanimous.
next reply other threads:[~2000-11-22 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 5:25 Richard Kenner [this message]
[not found] <00112021562300.00259@hallo>
2000-11-20 14:58 ` Removal of V2 code Mark Mitchell
2000-11-21 14:14 ` Geoff Keating
2000-11-21 15:06 ` Mark Mitchell
2000-11-21 20:00 ` SC confidentiality Geoff Keating
2000-11-21 21:57 ` Mark Mitchell
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=10011221325.AA13910@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).