12. |
What are other important issues in IFHOSP? |
Totally Irrelevant |
Extremely Relevant |
|
|
12.1
|
Expanding an IFHOSP into multiple mirror sites to increase reliability and obtain more credibility from users |
|
|
12.2
|
Maintaining a commitment to hosting only those projects which are under a sufficiently liberal license. |
|
|
12.3
|
Using the site to promote the concept Open Software/Free Software to the commercial world and non-free software developers |
|
|
12.4
|
IFHOSP site should be careful on the usage agreements with users and provide them with enough freedom |
|
|
12.5
|
Fair to all efforts |
|
|
12.6
|
Giving hosts of IFHOSP sites every credit that they deserve
Comment: |
They certainly deserve credit, but beware: they have their own advantages in doing so, either reputation-wise or in a financial way.
|
|
|
|
12.7
|
IFHOSP sites need to focus on maximising productivity |
|
|
12.8
|
Anyone wanting to setup an IFHOSP needs to be aware of the responsibility involved |
|
|
12.9
|
An IFHOSP should be run in an open fashion and users should be well informed |
|
|
12.10
|
An IFHOSP should be have up to date information of the site and employ novel techniques |
|
|
12.11
|
The acronym IFHOSP is pointlessly obscure
Comment: |
In question 12.12, I saw Freshmeat mentioned, while I was thinking of sites that hosts projects themselves, like SourceForge. I think of Freshmeat as a kind of Yahoo of projects, providing important things like categorizing and news related to open source projects. Thus, I answered things like "IFHOSP should not put too much emphasis on categorizing and news", because I was thinking that they should leave this kind of things to sites like Freshmeat. Now, if Freshmeat *is* an IFHOSP... :-)
|
|
|
|
12.12
|
Big IFHOSP are bad (e.g. Freshmeat) Small IFHOSP are good. |
|
|
12.13
|
A remedy of the administrator(s) of IFHOSP interfering with the development of project(s) is to provide mirroring or withdrawal paths for users if they want to host their projects elsewhere |
|
|
12.14
|
Ability to operate private or semi-private developer groups necessary to avoid "collaboration" with unwanted parties |
|