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.


Version 7 (Felix Schäfer, 2015-01-15 11:13 am)

1 1
h1. Frequently asked questions
2 1
3 4 Felix Schäfer
4 2 Felix Schäfer
5 2 Felix Schäfer
h2. Why shall I use ChiliProject and not Redmine?
6 2 Felix Schäfer
7 3 Felix Schäfer
ChiliProject is a fork of the "Redmine": project. One of the [[Why Fork|main reasons for forking]] was to gain stronger growth and speed in development by opening the process of contribution to a larger community. We believe that this will gain trust in the community and in the product. That is why we think that you can trust in this project, too.
8 2 Felix Schäfer
9 1
h2. Is ChiliProject OpenSource?
10 1
11 1
Yes, it is provided under the "GNU General Public License, version 2":
12 4 Felix Schäfer
13 4 Felix Schäfer
h2. What is Bluemine?
14 4 Felix Schäfer
15 4 Felix Schäfer
Bluemine was the code name for ChiliProject before we had an actual name.  It is based on the Ruby's community fascination with colors (RedCloth, BlueCloth).
16 5 Felix Schäfer
17 5 Felix Schäfer
h2. What is the proper name for ChiliProject?
18 5 Felix Schäfer
19 5 Felix Schäfer
The proper name is ChiliProject, as "CamelCase":  chiliproject is okay too when it's referring to "code" things like a filesystem path (e.g. install to @/var/chiliproject@) or package (e.g. @apt-get install chiliproject@).
20 5 Felix Schäfer
21 5 Felix Schäfer
Chili Project, chili-project, and chiliProject are not the correct spelling.
22 6 Felix Schäfer
23 6 Felix Schäfer
{{html_comment(TODO: Compatibility to Redmine?)}}
24 7 Felix Schäfer
{{html_comment(TODO: Where's the error trace from a 500 error, should probably be on a separate FAQ though)}}