Table of Contents
Project Management
This page has been set up to capture information about the software tools that are used to manage SSF projects. Please clearly outline in a reasonable sentence or paragraph what the issue or requirement is. Non-coders may read this and a brief explanation may be necessary.
Whilst there are no immediate plans to change project management environment, at some point in the future, there will probably be an effort to consolidate all SSF project management tools onto a single platform. This page will help capturing our experience and observations to guide that decision.
Please add the perspective you are coming from - be it SSF, User, or a project such as Agasti or Eden.
Strengths of Existing Systems
Please reference the issue under the correct heading. These are listed in alphabetical order.
Launchpad
Used by Agasti, and partly by Eden (although Trac is preferred).
- …
Redmine
Used by CUNY SPS internally.
- …
Trac
Used by Eden.
- …
Weaknesses of Existing Systems
Please reference the issue under the correct heading. These are listed in alphabetical order.
Launchpad
Used by Agasti, and partly by Eden (although Trac is preferred).
- …
Redmine
Used by CUNY SPS internally.
- Ruby on Rails - Redmine is a Ruby on Rails application, requiring non-native skills and platforms that are not native to the SSF, which are mostly PHP and Python.
Trac
Used by Eden.
- Lack of robust multi-project support - Trac lacks the ability to provide a robust approach to managing multiple projects under one instance. There are some existing options, but these do not provide the level of integration and easy administration required. See the (in)famous feature request #130. (SSF)
Desired Requirements
- Multi-project - it must support multiple projects e.g. Agasti and Eden. (SSF)
- Multi-branch - it must support multiple branches with a project e.g. Agasti-Vesuvius/Mayon or Eden-trunk/Haiti etc. (SSF)
- Single sign-on - it should be possible for a user or developer to sign in once and be able to access all SSF projects. (SSF)
- Single URL - it should be possible to promote a single high-level entry URL for the collection of bugs for all SSF products. Multiple URLs for different projects can lead to confusion for the users submitting bugs. (SSF)
- Tags - it should support tagging across multiple projects, so that we can provide easy access to issues such as GIS or OpenLayers, for example. This would allow us to point domain experts (e.g. GIS) to all GIS issues and then let then choose which project and bugs/features they wish to work on. (SSF)
- Transfer of bugs - often users register a bug in one project, when in fact it is another project. The system needs the ability to easily transfer bugs from one project to another when new bug reports are triaged, e.g. Eden to Agasti. (SSF)
- Easy administration - other than installation, the system should be able to be managed via a web interface for easy administration. (SSF)
