ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Package and distribute ChiliProject as a gem (Feature #334)

Added by Sam Kuper at 2011-04-14 03:15 pm. Updated at 2011-04-14 09:34 pm.

Status:Open Start date:2011-04-14
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:

Description

Currently, users installing ChiliProject are required to:
  • install a number of gems,
  • ensure they have obtained a suitable version of each of those gems,
  • use git to obtain ChiliProject itself.
By packaging and distributing ChiliProject as a gem, couldn't this be improved to simply the following step, which would automatically install dependent gems of the correct versions?
  • install ChiliProject as a gem.
Benefits:
  • Fewer steps required for the user, and therefore:
  • less scope for user mistakes,
  • greater user productivity (which is crucial, given that ChiliProject is supposed to be a productivity-enhancing tool).
  • Wouldn't require users to have Git installed, or even to know what it is. (Remember, for newbies, each dependency, especially if not automatically handled, is potentially a world of installation headaches, and also remember that for many newbies, even trying to grok what Git is for can be a bit confusing!)
  • Less documentation for ChiliProject to have to maintain.
  • Upgrades might also become a bit simpler.

History

#2
Updated by Sam Kuper at 2011-04-14 09:34 pm

Sam Kuper wrote:

Currently, users installing ChiliProject are required to:
  • use git to obtain ChiliProject itself.

I should note that I was wrong about this. My bad.

Also available in: Atom PDF