This is an
entry about the wonderful world of forks.
Firstly, general requirements of project management system:
- Documentation management
- Incidents tracking system: Incidents, queries and requirements [2] )
- Communication: News, forum, blogs, wiki’s, IM, user guides, development guides, styles guide, and so on.
- Community management system: User, roles, access control,
- Code management: SCM, automatic documentation, automatic test, continuous integration), releases.
Redmine is
a project management system, it is free software licensed as GNU General Public
License v2. Redmine is written using the
Ruby on
Rails framework.
Some of the main features of Redmine are:
- Multiple projects support
- Flexible role based access control
- Flexible issue tracking system
- Gantt chart and calendar
- News, documents & files management
- Feeds & email notifications
- Per project wiki
- Per project forums
- Time tracking
- Custom fields for issues, time-entries, projects and users
- SCM integration:
- SVN, CVS, Git, Mercurial, Bazaar and Darcs
- Issue creation via email
- Multiple LDAP authentication support
- User self-registration support
- Multilanguage support
- Multiple databases support
- Plugin model for extension
- REST API
ChiliProject
is a web based project management system. It supports your team throughout the
complete project life cycle, from setting up and discussing a project plan,
over tracking issues and reporting work progress to collaboratively sharing
knowledge. ChiliProject is free software licensed as GNU General Public License
v2.
Some of the
main features of ChiliProject are:
- Project planning (Roadmap, Gantt diagram)
- Issue tracking and progress reporting (activities, notification, feeds)
- Sharing knowledge collaboratively (Wiki, SCM:Git or subversion)
- Keep control of your expenses (Track the time, reports)
- Interact with externals (News, forum)
- Setup your work flows to support your business processes (Work flow, role, permissions)
- Plugin model for extension
In February
2011 a group of developers from the Redmine community, in particular, 6
developers.
Their
reasons for creating a fork were:
-
The
maintenance and evolution of Redmine has not been as predictable and responsive
-
Patches
were too sporadic
-
Lacked
a clear methodology.
-
The
efforts of community via public and private forums to discuss the goals and
future direction with the project manager of Redmine failed.
-
The
current project manager did not share these priorities.
Therefore,
they created this fork, called ChiliProject, which has been launched on the
basis of a 1.0.4 version of Redmine, with these principles:
- Depends upon people producing useful software and supporting documentation, contributing as a team for the benefit of the community.
- Reflects a spirit of collaboration and fun while garnering community feedback and providing good governance that allows for businesses to confidently invest in further development.
- Is open to the participation of anyone who can contribute value and who is willing to work with the community.
Actually,
it seems that Chiliproject have not had so much successful during these years.
At least
they have the same colour in their logos.
In
conclusion, in a first analysis seems to be a problem of communication of the
new community manager or managers, that he did not know how to integrates these concerns.
References:
[2] Example
of requirement management using issue tracker system http://www.redmine.org/projects/redmine/issues?set_filter=1&tracker_id=2
No hay comentarios:
Publicar un comentario