7. |
What are the negative results for users in using an IFHOSP site? |
Average
Totally Irrelevant |
Extremely Relevant |
|
No. of Votes
|
|
|
|
7.10
|
Loss control of the choice of tools hosted on site |
|
7
|
|
Details |
|
7.20
|
Decrease access to various data such as backups and logs from hosting server thus the ability of analysing this data was limited |
|
7
|
|
Details |
|
7.9
|
No negative results |
|
1
|
|
Details |
|
7.16
|
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
|
|
Details |
|
7.12
|
Limited tool customisation |
|
8
|
|
Details |
|
7.11
|
Loss control of the changes, quality and disappearing of toolset hosted |
|
7
|
|
Details |
|
7.13
|
Increase of commitment due to the community expectation on a developer to work on a certain project |
|
7
|
|
Details |
|
7.17
|
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. |
|
7
|
|
Details |
|
7.1
|
Lossing control over hosting uptimes and downtimes |
|
8
|
|
Details |
|
7.4
|
Possible extra "collaboration" with unwanted parties ("back-seat programmers", trolls) |
|
8
|
|
Details |
|
7.19
|
Users may hope an IFHSOP to implement new features and not to program them themselves. These features may never get implemented. |
|
8
|
|
Details |
|
7.18
|
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
|
|
Details |
|
7.2
|
Administrator(s) of IFHOSP may interfere with the development of project(s) |
|
7
|
|
Details |
|
7.14
|
Possible confusion when trying to use an IFHOSP site |
|
6
|
|
Details |
|
7.8
|
Low cost in setup will encourage starting unserious projects |
|
8
|
|
Details |
|
7.7
|
Low cost in setup will encourage projects to be publish before they are ready |
|
7
|
|
Details |
|
7.6
|
Low cost in setup will encourage development of projects that are similar (reinvention of the wheel) |
|
8
|
|
Details |
|
7.5
|
Low cost in setup will encourage forking of projects |
|
8
|
|
Details |
|
7.15
|
Having to rely on one's self. There is no other party or company to put the blame on. |
|
6
|
|
Details |