[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipse.org-architecture-council] [Bug 250317] Improve disseminating information from EMO top-down
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=250317
Product/Component: Community / Architecture Council
--- Comment #3 from Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> 2008-10-09 13:18:47 -0400 ---
One question is, IMHO, what really is the information that EVERYBODY needs to
know. I'm not in favor of overloading people with stuff they rarely need.
That's one advantage of a hierarchical setup. Committers need to know enough IP
for their daily work, and need to know that they can ask their project lead if
in doubt about anything special. Taking my own project as example, here is what
I have created for my committers a while back:
http://www.eclipse.org/dsdp/tm/development/committer_howto.php
When making them committer, I tell them that this is what they need to know,
and they can ask me for help at any time.
Project leads need to know enough to lead their project, and that they can ask
their PMC if in doubt. PMCs need to know yet a bit more, and ask their Mentor
who in turn asks the EMO.
In terms of "Material to read", I think that Bjorn and his team have done an
outstanding job in re-organizing this recently, and I really like the Wiki
entry point on http://wiki.eclipse.org/Development_Resources -- it's basically
organized exactly that way, separated by personas and what they need to know.
What's currently missing, IMHO, is a "push" medium to bring changes to the
attention of those people who need to knwo about those changes. That's what
currently seems un-organized.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
