Alan Coopersmith wrote:
>
>
> - if not using the Sun internal bug database directly (as bugs.os.o
> does now), then the ability to have Sun employees easily clone bugs
> from the internal db on a bug-by-bug basis, to migrate data from the
> traditional Solaris bug db. I'd rather see this as a simple tool
> anyone with access to the Sun bug db can use, so we can split the
> load of migrating the data and deciding which parts are clear to
> export among hundreds of people - give each a subcat or list of a
> few dozen bugs at a time, and use the power of the masses to make
> easier work of the impossible-to-automate process of determining
> which data is truly confidential and which isn't.
>
Okay, so I'm not on OGB, but I'm going to voice an opinion anyway. :-)
I think that the bug database needs to reside outside Sun. And I think
that it should not be duplicated into a private database inside Sun.
Otherwise Sun engineers will continue to just use the internal db and
not participate externally.
Sun's bugster will need to stay around for various reasons, but there is
no reason for it to be necessary for continued use by Solaris engineers.
This does mean some headache for those engineers which have to work on
internal only products (e.g. hardware bug tracking) _and_ also on
OpenSolaris bugs But I think they'll manage.
-- Garrett
