On Monday 10 January 2005 02.13, Cameron Blackwood wrote:
> "Brian G. Peterson" writes:
>   | The solution to this has already been discussed.  This is a discussion
>   | list not a notification list.  If you want notification, set up a watch
>   | that mee your requirements on Bugzilla.  Bugzilla will email you, and
>   | those who want discussion list without extra notifications can still
>   | have one.
>
> It seems to me:
>   *  there is a want for such a list from a number of people
>   *  it can be done via bugzilla
>
> maybe im just lazy, but the next step doesnt seem to be
>   *  (if new gentoo user who missed _this_ discussion) discover that
>      there is no announce for yet to be closed bugs
>   *  individually set up bugzilla to do it.
>   *  (repeat n hundred times)
>
> the logical solution seems to be:
>   *  set up a [EMAIL PROTECTED]
>
> I guess Im wondering what stops this happening again in 6 months with
> all the people who have joined after this disussion finishes (given
> that the list's function isnt clear) and then suddenly go 'hey....'.
>
> And also if it is sane to have a number of gentoo users all perform
> the same operation in the bugzilla when there seems to be a need for a
> single list that:
>   *  gets posts from bugzilla
>   *  noone else can post to (suggestion, announce on the new list, any
>      discussion here)
>   *  is an offical '@gentoo' list
>
> In that way, we add a single new list with a clear reason for
> existing, satisfy a lot of people and dont effect this group in
> any way except maybe to get some more secuity discussion.

I'm a fairly new gentoo-user, and I subscribed to this list thinking:
"Great, I'll be notified if something really serious, like a kernel root 
exploit, happens!". I understand now that this is not the case, but that many 
like me thought it was, or are wishing it were.

"[EMAIL PROTECTED]" like Cameron describes it is 
exactly what I was looking for. If technically possible, please create it!

Thanks,
/Johan

--
[email protected] mailing list

Reply via email to