- Describe in more detail what the goal of Buildship is.
- Provide links to the GitHub repository
- how to use install Buildship
- how to use build Buildship
- how to help out with Buildship
- Provide a link to Bugzilla bug tracking.
- Describe the layout of the Downloads section (milestones, snapshots).
We currently do not provide a lot of information, links, etc. on eclipse.org.
Provide an Oomph model for the Buildship project.
Include the Oomph model in the main catalog.
As of Eclipse Mars, Oomph is the default Eclipse installer. Having an Oomph model for Buildship will allow developers to easily get to a working setup of the Buildship project.
Once the external dependencies are available in Orbit, replace the physical jar files of the external dependencies (located in the lib folder) with references to Orbit.
Currently, the external dependencies of Buildship (Tooling API, Guava, etc.) live in the lib folder of the core plugin. This is not the Eclipse policy for features shipped with the core distribution.
Use the Eclipse build infrastructure to ensure that the Buildship plugins are signed with the real certificate.
Currently, the Buildship plugins are signed with a self-signed test certificate. In order to ship with the core distribution, the plugins must be signed with the real Eclipse certificate.
The plugins of the Buildship update site need to be compressed with pack200, and p2.index files should be added. We can do this as part of the automated Gradle build.
This is part of the simultaneous release requirements.
Hook into the Eclipse Mars Error Reporter to automatically receive error reports detected when executing Buildship.
Make it easy for users to report bugs.
- https://docs.google.com/document/d/14vRLXcgSwy0rEbpJArsR_FftOJW1SjWUAmZuzc2O8YI/pub
- http://www.infoq.com/news/2015/03/eclipse-mars-reporting
Collect data on the used functionality of Buildship and upload it in an anonymous way (iff the user has given his consent). In Buildship, display usage statistics to the user. Online, display overall statistics gathered from all participating users.
In order to constantly improve Buildship, we need to understand what functionality of Buildship people are using and how they are using it.
Provide content for the integrated help points, like in the New Wizard and the Import Wizard. Make help content available on http://help.eclipse.org, too.
Eclipse users are used to the integrated, context sensitive help system.
Have professionally designed icons for all views, buttons, and other UI elements.
As part of the UX, we need professionally designed icons.
Design a Buildship logo and integrate it into the plugins.
Each Eclipse core application should have its own logo for easy recognition in the Eclipse ecosystem.