[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [eclipse.org-architecture-council] Bug mail to the architecturelist?
|
Hi Jeff,
I think we discussed this on our last meeting before you
joined. Adding the mailing list on CC was meant as a test
balloon. The original goal was to find more flexible ways
of communicating.
If we find it disruptive to see bugzilla's on the EAC list,
there is a couple of things we can do:
(1) Close the mailing list against bugzilla mails again.
Ask EAC members to "watch" the EAC bugzilla user instead.
(2) Keep current setup, but once an initial bug is received
on the EAC list and acted on by somebody, manually remove
the mailing list from CC (and replace by an eac-inbox
virtual user for instance).
Personally, I like the possibility that "everyone" can send
to the mailing list by means of filing a bug. I agree though,
that once a discussion ongoing on bugzilla, the extra mails
to the mailing list are redundant and likely disturbing if
their volume increases.
While everyone could employ E-Mail filters at their leisure,
I guess that the pattern of "first Mail to the list, followup
on bugzilla only" is possible only by manual interaction
according to (2) above.
Let's discuss this in our meeting later today.
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx]
> On Behalf Of Jeff McAffer
> Sent: Thursday, September 11, 2008 3:17 PM
> To: eclipse.org-architecture-council
> Subject: [eclipse.org-architecture-council] Bug mail to the
> architecturelist?
>
> Recently there seem to be a number of bugs with the arch list being
> added to the cc list. I may have missed it but was this something we
> decided to do?Personally I find it quite disruptive.
>
> Perhaps if there is a bug that may be of interest to the arch
> group, a
> message could be sent to the list and people can CC
> themselves if they
> are interested.
>
> Jeff
>
> On Sep 11, 2008, at 8:02 AM, bugzilla-daemon@xxxxxxxxxxx wrote:
>
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=246945
> > Product/Component: Community / Architecture Council
> >
> >
> >
> >
> > --- Comment #4 from Ed Merks <Ed.Merks@xxxxxxxxx> 2008-09-11
> > 08:02:17 -0400 ---
> > Oisin,
> >
> > I've been around the block enough times to have also heard all the
> > things
> > you've just said. Clearly these legal issues are endlessly
> > fascinating. I can
> > say that based simply on the hour I spent yesterday with the IP
> > Advisory
> > Committee. :-P
> >
> > Obviously commercial vendors building on top of Eclipse
> technology are
> > massively important; hence the policy document Mike pointed
> us to.
> > One aspect
> > to keep in mind though is that there are commercial vendors who
> > provide
> > software services and don't actually care about the clause you
> > pointed out. If
> > their customer wants to use Hibernate, they'd like to provide
> > software and
> > services in support of that. It would be nice to broaden
> Eclipse's
> > base
> > without compromising any part of the commercial stack.
> >
> >
> > --
> > Configure bugmail:
> https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
> > ------- You are receiving this mail because: -------
> > You are on the CC list for the bug.
> > You are the assignee for the bug.
> > _______________________________________________
> > eclipse.org-architecture-council mailing list
> > eclipse.org-architecture-council@xxxxxxxxxxx
> >
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architect
> ure-council
> >
> > IMPORTANT: Membership in this list is generated by processes
> > internal to the Eclipse Foundation. To be permanently
> removed from
> > this list, you must contact emo@xxxxxxxxxxx to request removal.
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architect
> ure-council
>
> IMPORTANT: Membership in this list is generated by processes
> internal to the Eclipse Foundation. To be permanently
> removed from this list, you must contact emo@xxxxxxxxxxx to
> request removal.
>