Result for Question 6

Responses Shown

Hide Responses

Go to Question 5
Go back to the List of Questions
Go to Question 7

6.

What are the positive results for users in using an IFHOSP site?

6.1. Facilitation of developers to update the source code in the repository directly and reduction of the need to interact with the project leader to change the code
Mark increase in developer <-> repository source code interaction,
with corresponding decrease in developer <-> developer source
code interaction

clarification: developers send patches to one another (not just with the project leader) and produce multiple, personal, non-synchronized versions of their software when they do not have a repository to work from.
6.2. Increase communication within the developers
Mark increase in intra-group communication
Joanne Working with others. While working with others can sometimes be frustrating, it can also be rewarding (others are interested in 'your' project, you can brainstorm with them, etc).
6.3. Increase communication between the developers and other parties
Mark attraction of interested third parties
Phil being able to get help/assistance if they have a problem/question
6.4. Decrease cost of hosting a project
Michael Decreased administrative costs. No need to maintain the infrastructure yourself.
6.5. Decrease time in administration of an IFHOSP site individually
Luke More time to spend on the project itself, instead of wasteful management overhead.
6.6. Getting people to contribute to the development from all over world
Joanne Working with others. While working with others can sometimes be frustrating, it can also be rewarding (others are interested in 'your' project, you can brainstorm with them, etc).
Luke More community awareness which can result in more contributors
Gabriel Being able to collaborate with many people distributed all around the globe.
3 Responses
6.7. Building or joining a community and increase sense of belonging
Brendan great community
Luke More community awareness which can result in more contributors
Luke Additional sense of being part of a community
3 Responses
6.8. Self-reliance, freedom of doing things by oneself
Brendan self-reliance

clarification: realizing that you can do things yourself (see R W Emerson, American philosopher
6.9. Autonomy, being able to be completely independent from others
Brendan autonomy

clarification: acting on one's own in a completely independent way
6.10. Flexibility, being able to select from many ways of doing things
Brendan flexibility

clarification: being able to select from many ways of doing things
6.11. Centralised location for project management
Jacob better more organized software developemnt
Alvin Easy coordination - there is a central point from which everything is done
6.12. Centralised location to find Free Software/Open Source Software
Michael Increased chance of people finding your site if they look for a project of that type, as people look at the IFHOSP sites to find projects (at least before creating their own projects on the same site...)
Alvin If a given IFHOSP hosts many projects, users of various software don't have to go to 10 different places to get their software, and everything is presented consistently
6.13. More reliable then individually hosted servers (e.g. with only dial-up connection)
Mark reliable point of storage and distribution for software, documents
Garrett IFHOSP sites provide 24/7 service-hosting abilities. Without this, dialup-connection developer's ability to provide Open Source products effectively is extremely limited.
6.14. Uniform toolset with uniform interface for users
Michael Users and potential contributors are likely to be used to the tools. If you set up your own infrastructure, you are likely to do it customized to your needs - and this makes it less likely that you'll choose the packages your users are used to. If you use a large site like e.g. Sourceforge, there is also an increased chance that the users are used to just that site and the particular implementation of the tools there.
Alvin If a given IFHOSP hosts many projects, users of various software don't have to go to 10 different places to get their software, and everything is presented consistently
6.15. Great programs will be produced
Brendan great software
6.16. Greater possibility for getting community credit
Luke Greater possibility for community kudos
6.17. Facilitating collaboration and reduction of dulplicated effort
Garrett Of particular importance is the ability to revive dead projects. Without this ability, many projects would sit on someone's personal computer, forever gotten.
6.18. Possibility of reviving dead projects
Garrett Of particular importance is the ability to revive dead projects. Without this ability, many projects would sit on someone's personal computer, forever gotten.
6.19. Getting paid
Joanne In some instances, you might even be paid to work on something that you'd like to do anyway.
6.20. Obtaining up to date information
Phil getting up to date information
6.21. A more complete toolset - individually hosted sites usually only have tools that just meet the needs
Michael "Complete" basic toolset comes for free, which makes it more likely that the complete set of tools are implemented. In a self-hosted project, tools that are convenient but do not give very strong immediate benefits are often postponed.
6.22. Tools with better quality than individually hosted sites
Michael Quality Assurance on the tools you use are done by more than your own local developer- and userbase, so problems are more likely to be fixed before they impair one of your developers/users.
6.23. Special custom tools may be readily available
Michael Special custom tools may be available, which would be a pain to implement yourself (either as code or as configuration.)
6.24. Interesting parties on a certain project can be found before the project begins
Joanne Knowing, in advance, if there is interest in the project. (Are there any customers requesting it?)
6.25. Decrease the startup cost of hosting an Open Source/Free Software project
Michael Decreased project startup cost. The use of premade hosting infrastructure makes it possible to set up a fairly complete set of project infrastructure very simply, avoiding the normal costs (in terms of time or money) associated with finding a place to host it, aquiring a domain name, finding which software to use, setting up various software, etc.
6.26. Decrease the possibility of producing multiple non-synchronized versions of software
Mark increase in developer <-> repository source code interaction,
with corresponding decrease in developer <-> developer source
code interaction

clarification: developers send patches to one another (not just with the project leader) and produce multiple, personal, non-synchronized versions of their software when they do not have a repository to work from.

Hide Responses

Go to Question 5
Go back to the List of Questions
Go to Question 7

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