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.

notify some central server when Redmine is installed/upgraded (Feature #417)

Added by Alexey Java at 2011-05-18 12:51 am. Updated at 2011-05-20 05:45 pm.

Status:Open Start date:2011-05-18
Priority:Normal Due date:
Assignee:- % Done:

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

Description

see https://www.chiliproject.org/boards/1/topics/427

History

#1
Updated by Muntek Singh at 2011-05-18 03:53 am

What data would be relevant and what would we use it for?

#2
Updated by Alexey Java at 2011-05-18 04:30 am

we can show this data on the project main page (chiliproject.org):
"Number of Chiliproject installs" - total: XX, this month: YY

This info can be useful for the potential users who consider Redmine or Chiliproject.

when a Chiliproject instance is installed and some initial webpage is loaded, our server (well, some server) will be notified via an HTTPS request or email and it will increment its counter of Chiliproject installations.

we don't really need any specific data from the installation, but we could have these optional items in the request:
1) Chiliproject version
2) Country where the server is installed (we can show a pie diagram with this info on chiliproject.org)

User can choose whether or not to provide any of these fields or whether or not to send the request at all.

We can have (if not already have) some initial webpage which user need to open before the application can be used. There could be some setup parameters - like "set admin password", etc. One of the steps during this initial web-based setup would be asking permission to send the info I described above.

#3
Updated by Gregor Schmidt at 2011-05-20 04:39 pm

There is, I think, only 1 option to justify such a remote call: To show a warning, that a bug fix release was released and the current version is outdated. But w/o an auto-update mechanism, this warning is fairly lame.

#4
Updated by Eric Davis at 2011-05-20 05:45 pm

Gregor Schmidt wrote:

There is, I think, only 1 option to justify such a remote call: To show a warning, that a bug fix release was released and the current version is outdated.

I agree with this. I don't know if we should track the actual installs really. It's social proof but not really that valid. More installs is not the same as "best software for me". (e.g. Windows vs OSX vs Linux)

But w/o an auto-update mechanism, this warning is fairly lame.

But I 100% disagree with this. I use Wordpress and it has a "Update available" notification that I use all the time to hear about updates (mostly security ones too). They have an auto-update but that is a separate point. Letting people know that an update is available is more important.

(And if this worked for plugins too... :) )

Also available in: Atom PDF