is the draft E-Mail which I proposed sending to Eclipse.org-committers,
our new bugzilla CC abilities. Feedback is welcome, and I
finalizing the draft in our meeting tomorrow.
Announcing the EAC bug component
for discussions and questions:
you may be aware, the EAC is staffed by appointed members
the most senior committers in the entire community,
as well as
representatives from each PMC and strategic member.
can now leverage this combined wisdom in the following ways:
a bug against the Eclipse Foundation / Community /
Architecture Council component. All EAC members will
get notified and answer the bug as appropriate.
E-Mail address on CC of an existing bug. All EAC
members will get notified and comment on your bug
What should be the scope of discussions initiated with the EAC?
Think of it as a means of "escalation". Any question that you'd
a mentor's advice on can be brought to the EAC's attention.
questions like "How do other projects..." - it doesn't
to be limited to technical questions, in our opinion
organizational issues just as much. We especially appreciate
ideas or suggestions that might be interesting on a broader
many cases the EAC may not answer your question directly, but
you in the right direction; your bug's log will keep the history
Q: How does
this relate to the existing cross-project-issues-dev mailing list and
A: We consider the cross-project-isses
component as a tool for
day-to-day work coordinating between
projects, especially those
that are on the release train (Galileo). The EAC
bugs can be more
fundamental, broader in scope, or with a longer time
Q: Is this going to scale?
A: We'll see,
it is an experiment for now but we're very much looking
getting involved in the questions, ideas or suggestions that
you may have.
Senior Member of Technical Staff, Wind
Management Project Lead, DSDP PMC Member
eclipse.org-architecture-council mailing list
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.