Skip to main content

Notice: This Wiki is now read only and edits are no longer 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 Redesign 2011"

Line 1: Line 1:
 +
This effort is being tracked by [https://bugs.eclipse.org/bugs/show_bug.cgi?id=243223 Bug 243223].
 +
 
=Problem Statement=
 
=Problem Statement=
 
Current infrastructure (i.e. The Developer Portal) is inadequate.
 
Current infrastructure (i.e. The Developer Portal) is inadequate.
Line 17: Line 19:
  
 
There are several other options that have been considered, including a handful of Eclipse-based solutions (which would allow us to "eat our own dogfood"). After careful consideration, however, we have determined that we do not have the resources to implement these solutions.
 
There are several other options that have been considered, including a handful of Eclipse-based solutions (which would allow us to "eat our own dogfood"). After careful consideration, however, we have determined that we do not have the resources to implement these solutions.
 +
 +
{|  border="1" cellpadding="2"
 +
|+Technology comparison
 +
|- style="vertical-align:top;"
 +
!   !! Language !! In-house Resources !! Community Size !! Comments
 +
 +
|- style="vertical-align:top;"
 +
! Drupal
 +
| PHP
 +
| 5
 +
| 100,000's
 +
|
 +
* Is deployed by 1,000's of organizations
 +
* Hundreds of plug-ins available to leverage in favour of writing custom code
 +
** Integration with Facebook, Twitter, etc.
 +
 +
 +
|}

Revision as of 10:32, 20 July 2011

This effort is being tracked by Bug 243223.

Problem Statement

Current infrastructure (i.e. The Developer Portal) is inadequate.

Multiple, separate data sources.

Portal is separate from the the resources being managed. Requires a context switch to use. Most committers have difficulty (or outright refuse) to make that context switch.

Some management tasks are spread out. Specifying a description for a project, for example, requires that an HTML file be created in the project directory (requires CVS check-in), and then the specification of a URL in the portal. Very difficult to maintain. Very separated from where and how the description is used. As a result, descriptions tend to be poorly specified, and maintained.

Too much information is not included in or managed by the portal. Project proposals, review documentation, IP logs, are all separate.

Technology Choices

Project management is essentially a document-management and workflow problem. Several solutions exist in this area.

The Eclipse Foundation currently uses Drupal for Eclipse Marketplace, Eclipse Live, and the EclipseCon Website. Several Eclipse Foundation employees are already well-versed in Drupal development, and finding temporary resources with the necessary skills in the local area should be relatively easy and cost-effective. Drupal is based on PHP, a language that is known to most of the Eclipse Foundation staff, and is currently in wide deployment by the Eclipse Foundation.

There are several other options that have been considered, including a handful of Eclipse-based solutions (which would allow us to "eat our own dogfood"). After careful consideration, however, we have determined that we do not have the resources to implement these solutions.

Technology comparison
  Language In-house Resources Community Size Comments
Drupal PHP 5 100,000's
  • Is deployed by 1,000's of organizations
  • Hundreds of plug-ins available to leverage in favour of writing custom code
    • Integration with Facebook, Twitter, etc.


Back to the top