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.
Public web site (Task #7)
To go public we will need a public website (Redmine probably) and a way for interested parties to signup for it. We should also have much of our organization documentation on it so people can see that it's open.
- Public Redmine instance
Homepage set to a specific wiki page (OSS plugin)
- Documents posted to the Wiki
- Server instance setup
- Limited management (root)
- Using open sourced code (theme, plugins, etc)
|related to Task #50: Setup Server||Closed||2011-01-19|
|related to Bug #81: Replace favicon||Closed||2011-01-20|
|related to Task #60: Change website homepage to load the Wiki homepage||Closed||2011-01-13|
|related to Task #37: ChiliProject Security Mailing Lists||Closed||2010-12-29|
|related to Task #36: ChiliProject Blog||Closed||2010-12-29|
|related to Task #35: ChiliProject Wiki||Closed||2010-12-29|
|related to Task #34: ChiliProject forums||Closed||2010-12-29|
The minimum should be a public redmine instance. I vote for this as the single starting point to go live.I'm wondering whether it would be a good idea to have certain information in a CMS later. That could include
- Introductory infos (What is Bluemine, screenshots, ...)
- Blog (Aggregator ?)
This Website could be the much more friendly starting point for people and should properly integrate into the Redmine (design, link structure, users, ...)
- Assignee deleted (