On Thu, 12 Apr 2007 09:54:23 -0600
Jim Ramsay <[EMAIL PROTECTED]> wrote:
> I personally prefer the first option here, but others think full
> public transparency would be nice, and after ${time_period} most of
> the info on -core isn't nearly as 'sensitive' as it is when first
> posted.

If something's supposed to be transparent, it shouldn't be on -core.
And, conversely, if something's on -core, it's not supposed to be
transparent. Opening up -core just makes it harder to handle those rare
cases where things really are required to be restricted.

There's also the issue of whether this can legitimately be made
retroactive. As Ned already pointed out, some developers only posted
things to -core because they believed that it was not public.

Instead, why not look into reducing the amount of traffic on -core?

-- 
Ciaran McCreesh

Attachment: signature.asc
Description: PGP signature

Reply via email to