Result for Question 5

Responses Shown

Hide Responses

Go to Question 4
Go back to the List of Questions
Go to Question 6

5.

What are barriers that prevent users from using an IFHOSP site?

5.1. Unreliable
Mark downtime
Jacob Problems of knowing the hosted site is reliable and does not become
a bottleneck
Alvin Lack of reliability
Luke Fear that the IFHOSP will shut down and disrupt the project
4 Responses
5.2. Poor publicity, cannot find the site
Garrett no knowledge of the existence of the site
Brendan poor publicity
Noah Finding it.
3 Responses
5.3. Low in technical skill, inexperience in using an IFHOSP
Garrett Inexperience with the toolsets used
Joanne Not understanding how the IFHOSP works.
Brendan cluelessness
Brendan low geek level
4 Responses
5.4. Low bandwidth, hard to access
Mark inaccessibility
Mark slow connection
Jacob Problems of knowing the hosted site is reliable and does not become
a bottleneck
Noah Low bandwidth.
4 Responses
5.5. The opposite of the answers in question 4
Leslie the oposite of the former answer
5.6. Low storage capacity
Mark low capacity
5.7. Counterproductive user interface
Schulhoff Counterproductive user interface - Many developers view productivity as a goal in it self.
Dave Tools that are hard to use or that are impossible to get ones work done.
Noah Poor user interface.
3 Responses
5.8. The odd urge to pay for software rather than help build it yourself
Brendan the odd urge to pay for software rather than help build it yourself
5.9. Wanting to have more control and not wanting to develop software in an Open Source/Free Software style
Joanne Wanting to work completely on their own.
Luke Fear of losing control of their project.
5.10. Not providing the tools or the features needed
Alvin Lack of features that can be had hosting a project on a locally controlled machine
Dave Tools that are hard to use or that are impossible to get ones work done.
Luke Not having all the tools they need to maintain the project on the given IFHOSP site.
3 Responses
5.11. Not having enough control over the IFHOSP comparing with a local machine
Alvin Lack of features that can be had hosting a project on a locally controlled machine
5.12. Not trusting the host of the IFHOSP
Alvin Worry that the entity controlling the IFHOSP may do something negative with the project or that they may have some rights to the project by nature of the fact that it is hosted with them.
Luke Fear that the IFHOSP will shut down and disrupt the project
5.13. Not control the content and the development direction of the IFHOSP
Jacob Lack of control over hosted content
Alvin Worry that the entity controlling the IFHOSP may do something negative with the project or that they may have some rights to the project by nature of the fact that it is hosted with them.
5.14. Intellectual property issues - the host of the IFHOSP may impose some rights to the projects hosted
Jacob issues of intellectual property
Alvin Worry that the entity controlling the IFHOSP may do something negative with the project or that they may have some rights to the project by nature of the fact that it is hosted with them.
5.15. Incompatibility with the format that users had in software development
Mark incompatibility

clarification: the site may impose a set of tools, a community organization structure, and a development methodology which is not readily compatible with the way a user is already developing their software. this will prevent the user from moving from their private facility to the IFHOSP site. the IFHOSP site must be willing to provide "partial" service using the user's preferred tools and methodology, at least as a stopgap until the user converts to the IFHOSP site's preferred tools and methodology.
5.16. Unresponsive administrators
Mark unresponsive administrators
5.17. Legal issues on software distribution
Alvin Worry about international laws, if you're writing an encryption package, it matters where the IFHOSP is located as to whether or not you would want to use it due to export laws, etc.
5.18. Lack of documentation and/or information or poor quality documentation and/or information so that users could not work out how to use the site
Alvin Lack of technical documentation on how to set up programs needed to use services. (Like encrypted CVS, or CVS in general)
Brendan poor documentation
Noah Poor quality of information.
3 Responses
5.19. The IFHOSP does not reach a critical mass of users and projects to achieve its advertising function
Schulhoff Critical mass - IFHOSP sites also functions as advertising locations for projects. The site must have a sufficient number of projects and users.
5.20. Difficult to casually browse or some information cannot be accessed without a username
Dave Difficult to casually browse w/o a username
5.21. The fear of getting flame from other people
Phil the fear of getting flame from other people (i.e. open source community is often perceived as being hostile to new people)
5.22. Poor access tools
Brendan poor access tools

Hide Responses

Go to Question 4
Go back to the List of Questions
Go to Question 6

Go to Infrastructure For Hosting Open Source Project (IFHOSP) Delphi Survey
Generated On: 27 Sep 2002