Project Plan For Dash, Tools for Committers and members, version 1.0
Introduction
The Dash project currently does not produce an Eclipse plug-in and thus does not have a traditional release cycle. Dash currently produces tools for committers that are deployed on various eclipse.org servers. These deployments are done incrementally, often daily, whenever new functionality is needed. We roll these deployments up into monthly milestones for reporting.
The Dash project is divided into two parts: Dash and Dash-prime. Dash is the open source project and Dash-prime is the closed, internal-to-the-Foundation, code base. Even though the Dash-prime code base is closed, the planning, discussions, and bug activities are open. Thus this project plan covers both Dash and Dash-prime.
Release Deliverables
The Dash project delivers server software running on eclipse.org servers (Commits Explorer and Ganymatic). The Dash-prime team is also responsible for an internal Foundation application deployed on eclipse.org servers (Portal).
Release Milestones
| M1 | 4/30/2008 | April milestone |
| M2 | 5/31/2008 | May milestone |
| M3 | 6/30/2008 | June milestone |
| M4 | 7/31/2008 | July milestone |
Target Environments
Ganymatic runs on the build.eclipse.org server and requires Java 5.0 and Ant 1.7.
Commits Explorer runs on the dash.eclipse.org server and requires a current version of Apache, PHP, Perl, and MySQL.
Foundation Portal runs on the portal.eclipse.org server and requires a current version of Apache, PHP, and MySQL.
Internationalization
None of the Dash deliverables are internationalized.
Compatibility with Previous Releases
Themes and Priorities
The Dash project is not a traditional Eclipse project in that it is in support of the Eclipse committers and member rather than in support of adopters and users. Thus the Dash project has a somewhat different set of Themes and Priorities than those defined by the Requirements Council.
Clean the Graffiti
Cleaning the Graffiti is reducing the backlog of small bugs against the Dash and Dash-prime tools. The goal is to have committers feel happy about the portal (it's doing what they want) and to believe that the portal team is responsive to their requests (it's going in the right direction). We want the Dash tools to be a benefit of Eclipse committership and not a burden.
- Committed
- [Clean the Graffiti] Add "email me my password" to portal login page [188005] (target milestone: June 08)
- [Clean the Graffiti] Problem with mails sent by the Portal [228705] (target milestone: May 08)
- [Clean the Graffiti] Managing Documentation Requirements When Committer Changes Employer [202950] (target milestone: May 08)
- [Clean the Graffiti] Lat/Lon parsing in the portal [227462] (target milestone: May 08)
- [Clean the Graffiti] Unclear how to set "Project Web Site" on project summary page [217342] (target milestone: May 08)
- [Clean the Graffiti] CVS data gets listed out of sequence [215293] (target milestone: May 08)
- [Clean the Graffiti] "non-epl" keyword misleading [196570] (target milestone: June 08)
- [Clean the Graffiti] Updated subscriptions when committer email address changes [204485] (target milestone: June 08)
- [Clean the Graffiti] Portal pages encoded with Big5 causes rendering issues [231185] (target milestone: ---)
- [Clean the Graffiti] pmc action requirement not clear [206255]
(target milestone: May 08) - [Clean the Graffiti] Allow different mailing lists for decommitterization requests [227354]
(target milestone: May 08) - [Clean the Graffiti] Reminders for out of date meta-data addresses to project leads [227859]
(target milestone: ---) - [Clean the Graffiti] spacing is inconsistent in portal's view of project meta [215294]
(target milestone: April 08)
Manage Committers
Managing Committers is our theme for provide teams and team leaders tools to manage their committer populations: adding new committers, removing inactive committers, managing file permissions, etc.
- Committed
- [Manage Committers] Committer Deactivation Requests Via Portal [211921]
(target milestone: April 08) - [Manage Committers] Portal interface for removing a committer [199502]
(target milestone: April 08) - [Manage Committers] "Committer Emeritus" status [222350]
(target milestone: ---) - [Manage Committers] Give PMC members access to decommitterization tool [227356]
(target milestone: April 08) - [Manage Committers] Nominations should require known address [229120]
(target milestone: ---)
- [Manage Committers] Committer Deactivation Requests Via Portal [211921]
Make The Portal More Of A Home
The portal is very useful as it is. But it could be much more. It is currently mostly a workflow facilitator helping project members walk the development process etc. But given that most of the content is driven by a database or two, there are many more possibilities that would make it more attractive as a landing page for committers.
- Committed
Improve the Experience
As the portal handles more of the workflow for our committers and members, it could become cluttered and slow. We plan to improve both the user interface and the infrastructure to avoid that.
- Committed
Submission System
We're moving the formerly bugzilla-based EclipseCon submission system to a portal-based system. This change will enable the submission system to integrate with more of our databases, thus improving the user experience for speakers and attendees, as well as reducing the server load for generating web pages.
- Committed
- [Submission System] Allow logins to the Portal using Bugzilla accounts [224210]
(target milestone: 2008-Q2) - [Submission System] Add 'Submission' Component [229485]
(target milestone: May 08) - [Submission System] Contact Address component needs to allow committers to tie a Bugzilla account to their committer account [227669]
(target milestone: ---)
- [Submission System] Allow logins to the Portal using Bugzilla accounts [224210]
Other
Features and bugs that we plan to address in the next three months that are not yet categorized into a theme.
- Proposed
- Need a couple more "How tos"... [202198] (target milestone: June 08)
- Help wanted / getting started section on standard project information pages [226944] (target milestone: June 08)
- Notify project teams of new approved versions of third-party code they use [205085] (target milestone: June 08)
- Performance monitoring for the portal itself [204585] (target milestone: July 08)
- Link graduation process page to other process pages [218090] (target milestone: June 08)
- Identification of Similar Requests Currently Pending [205241] (target milestone: June 08)
- Change schema checker entirely drive by the table dump [217787] (target milestone: July 08)
- Portal process/checklist for release reviews [207107] (target milestone: May 08)
- Project calendar url on standard project info page [227857] (target milestone: May 08)
- Database rebuilding needs to remove unused tables or swam.php breaks [229986] (target milestone: July 08)
- Add explain link [177218] (target milestone: June 08)
- Webmaster component should have link to Foundation DB and show Provisioning info [203844] (target milestone: July 08)
- Identification of New Release of Previously Approved Version of Code [201846]
(target milestone: May 08) - Compare the committer-only and non-committer versions of the Guide to Legal Docs [227464]
(target milestone: May 08) - Standard project plan format [215301]
(target milestone: May 08) - Questions in Portal Resulting in Keyword Population [201843]
(target milestone: May 08) - Refactor components to separate classes from factories [204838]
(target milestone: July 08) - Member Access to Employee Committer Lists [206684]
(target milestone: May 08) - Webmaster needs edit privileges [206795]
(target milestone: May 08) - Send HTML emails (or combo text/HTML) [188992]
(target milestone: June 08)
