Project Dash is a place where the community itself can collaborate on tools for community awareness and collaboration in support of our ultimate objective of committer quality and cooperation. The Commits Explorer and the Foundation Portal are the two current major efforts of Project Dash. We would expect that common build infrastructure and tooling will eventually be added. (See also the project info page.)
The Dash and Dash-prime projects organize their work in themes. We don't have "releases" in the traditional shrink-wrap sense because we release our tools to the committers incrementally, as often as we need to. This "release" schedule can be as often as three or four times a day.
Clean the Graffiti
Clean 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.
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.
Project Dash is the open source team and Dash-prime is the closed source team. Dash-prime implements server-side tools for the Eclipse Foundation on behalf of the larger Eclipse community, but for privacy and security reasons, the Dash-prime tools are not open source. However, the same Dash project team works on both the open and closed sides and thus these project pages and plans cover both efforts.
Note that even through the Dash-prime source is closed, the project planning and tracking and progress is all open: we plan and discuss and argue and file bugs that all can monitor.
Current Dash Efforts
- Commits Explorer - Who, What, Where & When of Eclipse Project Commit Stats
- Foundation Portal - The Member/Committer Interface with the Foundation
- Ganymatic - Building a Better Coordinated Release Train
Here are the bugs we plan to fix/new features we plan to implement in each of the following milestones: