Here is the second part of the Eclipse Way.
Planning is a blueprint for the next release. The component team defines the plan of the component to be developed, and then the management committee (PMC) develops the original project plan. In the plan, there are always some we can do and what we want to do. Planning each quarter will be updated to reflect the progress of the project, the new entry, etc. This plan finally finalized before formally released.
Risk Assessment As early as possible to point out high-risk projects and projects with many dependencies. Develop a schedule that will be removed by this item if needed. This approach reduces the risk of other projects.
Collective Ownership Weekly, the Management Committee (PMC) will gather again. All component team leaders and PMC members will have a conference call. The meeting will be released in the developer's mailing list. Establish a dynamic team to solve the problem in the intersection of the component. If possible, let the team members face to face.
The APIs are released on time, but must ensure the integrity of the system architecture. Sustained high quality API.
APIS First (APIS First) Feedback Early Feedback Violation Standards in the API. The reason is very simple, and the work of work does not necessarily mean that its API is allowed. When defining a new API, at least one of the users must be involved here, the better.
I still recommend watching the original text on eclipsepowred.org. I always feel that translation is not very appropriate.
