|
|
| (34 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | In 2011, the Eclipse Foundation began a new effort to replace the existing project management infrastructure--which includes the Developer Portal--with a new unified infrastructure with the intent to make project management activities more consistent and generally easier for all involved.
| + | The EMO has moved this content to the [https://www.eclipse.org/projects/handbook/#pmi Eclipse Project Handbook]. |
| − | | + | |
| − | Themes of this effort include:
| + | |
| − | | + | |
| − | * ''Improved consistency''. Configuration/data-driven project web presence, direct linkage between releases, reviews, and plans. Information--including basic project metadata, project plans, and release review information--is captured and retained in a consistent (and easily leveraged) data-based format (rather than in multiple documents in arbitrary formats).
| + | |
| − | * ''All-in-one-place''. Committers are able to edit information in place on the project information pages. Text/information in one place with links in another is eliminated where possible. Comments and discussion related to reviews, elections, etc. are connected directly to the item being discussed.
| + | |
| − | * ''Get started faster''. By default, projects are provided with a data-driven website that includes consistent links to project releases, reviews, downloads, etc. Projects can opt to override the default and provide their own customized web presence.Setting up a project presence is a matter of configuration, not PHP programming against proprietary APIs.
| + | |
| − | | + | |
| − | ==Links==
| + | |
| − | | + | |
| − | *[[Project Management Infrastructure/Development|Development]]
| + | |
| − | *[[Project Management Infrastructure/Technology Choices|Technology Choices]]
| + | |
| − | | + | |
| − | ==Overview==
| + | |
Latest revision as of 15:32, 18 May 2023
The EMO has moved this content to the Eclipse Project Handbook.
