[
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
Dave Carver <d_a_carver@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |d_a_carver@xxxxxxxxx
--- Comment #1 from Dave Carver <d_a_carver@xxxxxxxxx> 2008-10-09 13:12:00 -0400 ---
If there are general things that every committer should know, then a couple of
suggestions:
1. The Foundation should have the Committer information not only in the Wiki,
but also as a PDF that is sent to all new committers after their final
paperwork is approved. It'll contain the latest information about the
development process.
2. Project Leads or PMC should have a document that outlines the development
process and procedures for their projects. As each eclipse project has free
reign basically to choose what ever development methodology they want within
the bounds of the Eclipse Developement Process.
The issue I experienced when I started as a new committer, was that
documentation wasn't readily available. If you go to a new job, you usually
get a bunch of paper work to read the first day or so.
As for how to handle the information in multiple formats...my suggestion would
be DocBook XML files but I'm biased that way. The information then could be
translated to Wiki Pages, PDF, HTML, Word XML, etc.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
