On Mon, 18 Dec 2006, Richard Lowe wrote:
[redirecting to website-discuss]
Andrew Pattison wrote:
What about creating a "public comments" field and showing that on b.o.o?
The existing "comments" field would be kept for private stuff, and the new
"public comments" field should be used as the default unless the info you
are
typing must be kept confidential. That way you keep the old stuff that must
be kept closed confidential, but all new stuff that can be shared with the
wider community *is* shared.
This is effectively what bugs.sun.com does. The "Comments" there are (I'm
told) entirely disconnected from their namesakes in BT2 (which if true, would
cause the opposite problem...)
This, and many other things have been suggested previously (separate notes,
flags per-note indicating confidentiality, etc, etc).
The last real discussion of fixing things such as this was in the "New
Release of B.O.O" thread which bounced between both here and website-discuss,
and really ended nowhere beyond a "We're still thinking about how to fix it"
kind of summary.
Internally, we've asked folks to put as much as they can in the "description"
field of the bug, since that is what is shared publicly in all of our databases.
CRTs have also been told to not accept an RTI that only has "See comments"
as its description, so hopefully this will improve over time.
On the bugtracking backend, we've certainly discussed a flag per note
entry on whether or not the information could be made public, and having
a "public" mirror of the database (so frontends like "b.o.o."/sunsolve/etc
could just share their entire database view). Right now, that work is
not happening due to lack of funding, but it is on the list of improvements
we really want.
Valerie
--
Valerie Bubb, http://blogs.sun.com/bubbva
Solaris Security Technologies, Developer, Sun Microsystems, Inc.
17 Network Circle, Menlo Park, CA, 94025. 650-786-0461
_______________________________________________
opensolaris-discuss mailing list
[email protected]
