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.

Why companies contribute

This document is a DRAFT that is being worked on. You can help out by discussing it in the Forums.

Companies contribute to the project for multiple reasons. The better we understand the requirements and motivating factors the better we can invite companies to support the project or even to become active members of the project.

Contents

1. Companies that use ChiliProject internally

  • Ability to customize ChiliProject in oder to support their company-specific requirements and processes
  • Features
  • Low training costs
    • Usability
    • Training material
  • Low operating costs
  • High standards of data security
  • Integration in existing infrastruture and systems
  • Reliability of the project's future (e.g. for investment decisions)
  • Service providers (hosters, developers, trainers, consultants, etc.)

2. Providers of ChiliProject-based services

2.1. Hosters

  • Low operating costs
  • Reliable performance tests and public benchmark
  • Software packages
  • Release notes
  • Documentation

2.2. Developers

  • High code quality
  • API stability
  • Extendability
  • Low costs for code maintenance

2.3 Trainers and consultants

  • Usability
  • Customization-features
  • Training material
  • Presentations for promotions
  • Documentation
  • Screencasts