7. |
What are the negative results for users in using an IFHOSP site? |
Average
Totally Irrelevant |
Extremely Relevant |
|
No. of Votes
|
|
|
|
1
|
Loss control of the choice of tools hosted on site |
|
8
|
|
|
2
|
More inertia in tool choice. If a new tool become available to replace an old one, it will be harder for an entire IFHOSP site to switch than a single project. |
|
8
|
|
|
3
|
Limited tool customisation |
|
7
|
|
|
4
|
Loss control of the changes, quality and disappearing of toolset hosted |
|
8
|
|
|
5
|
Increase of commitment due to the community expectation on a developer to work on a certain project |
|
7
|
|
|
6
|
Decrease access to various data such as backups and logs from hosting server thus the ability of analysing this data was limited |
|
8
|
|
|
7
|
Lossing control over hosting uptimes and downtimes |
|
8
|
|
|
8
|
Possible extra "collaboration" with unwanted parties ("back-seat programmers", trolls) |
|
8
|
|
|
9
|
Decreases tool knowledge depth. The administrative tasks related to running the tools yourself is also useful in using the tool. This knowledge is removed from the knowledge pool for your project unless somebody incidentally administer the tool elsewhere. |
|
8
|
|
|
10
|
Limitation placed on Intellectual Property rights. Depending on the license under which you get to use the IFHOSP, you may suddenly find that you've allowed licensing you hadn't planned. |
|
8
|
|