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.
Remus/Clean up
< Remus
Revision as of 08:31, 4 December 2012 by Unnamed Poltroon (Talk) (New page: This site is an overview to bring the Eclipse Remus project back on track: == Current status == * Highly fragmented sources * The current release was built against Eclipse Helios (which ...)
This site is an overview to bring the Eclipse Remus project back on track:
Contents
Current status
- Highly fragmented sources
- The current release was built against Eclipse Helios (which is almost over 2 years old)
- Bundles are in a good shape
- Sources are managed in CVS
- External plugin contributions are not part of the Eclipse project
Problems of the project regarding the development process
- Project plan is not up-to-date
- No developer activity
- No official release
- Downloads are not provided from the Eclipse-servers.
- Builds is not on the infrastructure of Eclipse
- The domain remus-software.org serves as alternative project page which is not permitted
- Git Migration
Why we should not terminate the project
- There is a community interest in the project (regarding downloads and feedback)
- The efforts to bring the project in a good shape are not too high
- It's a project that enriches the diversity of the Eclipse Foundation and its project ecosystem
- Remus is running in productive applications. It needs to be ensured to provide minor bugfixes/new feature
What do we need to do?
- Update the project plan Bug 395695
- Schedule an official 0.3 release (Beginning of 2013) Bug 395695
- Built the bundles against a Juno target Bug 395641
- Automate the build with Maven/Tycho, use the build infrastructure of Eclipse.org
- Move the relevant content from remus-software.org to eclipse.org/remus and shutdown the website
What about the future?
- Remus needs to be more focused. The current application can do a lot of things but is very complicated, user-unfriendly and overloaded with features. Due to the very limited resources there must be a consolidation of the current implemented features (some features are very specific and confusing) and the last year already started re-implementation of the visualization of the overall data-structure must be committed in the next version.
- Translating the existent German documentation into English should also lower the barrier of entry.
- Release more often. Before Remus was moved to Eclipse there was a fresh version every week.
- UI Clean up: Relying on HTML for our primary visualization technology should give us enough possibilities to make Remus look like a modern application, a redesign of the editors is preferred.