Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Project Management Infrastructure"

(Replaced content with "The EMO has moved this content to the [https://www.eclipse.org/projects/handbook/#pmi Eclipse Project Handbook].")
 
(35 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 captured and retained in a consistent (and easily leveraged) data-based format (rather than 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, etc. is 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.
+

Latest revision as of 15:32, 18 May 2023

The EMO has moved this content to the Eclipse Project Handbook.

Back to the top