Answer from Alvin

Summary Shown

Hide Summary

Go to List of Participants

Alvin regards himself/herself as:

1. What are the objectives of an IFHOSP site?

1.1 To make communication between developers fast and easy. (Mailing lists, possibly instant messaging, web forums, etc)
To facilitate communication between developers
1.2 To provide technical tools (such as CVS) to aid in development
To enable distributed software development for developers from different geographic locations
To provide tools needed to achieve the objectives of IFHOSP
1.3 To provide a method for publishing the result. (Downloads of files created)
To distribute Free Software/Open Source Software
To provide an archive of Open Source/Free Software development related materials to the general public
1.4 To provide a method for making public new releases (like an announcement board)
To promote existing project(s) hosted on site to users of software
To promote existing project(s) to developers and attract contribution
To provide tools needed to achieve the objectives of IFHOSP
1.5 To provide a mechanism to recruit new developers to the project. (Simply allowing the posting of "ads", as in, this project needs another C programmer, join if you're interested)
To promote existing project(s) to developers and attract contribution

2. What tools can be employed on an IFHOSP site and what are the important features and usability factors for each of them?

Tool 1: CVS   Source Code Repository

2.1 Brief Description

Concurrent Versioning System. Allows revision of a centralized copy of source code by many developers simultaneously.
CVS (Concurrent Versions System)
Maintains a centralised repository of current and previous versions of source code, documentation, etc.
Allow concurrent development of software, support cooperative work by many developers

2.1.2 What are the important features of this tools?

2.1.2.1 Ability to allow usernames and passwords for access
Security features, e.g. usernames and passwords protection, access via ssh encryption
2.1.2.2 Ability to allow anonymous passwordless access to source repositories (read only)
Allowing anonymous users read only access
2.1.2.3 Can be set up to run with ssh encrypted.
Security features, e.g. usernames and passwords protection, access via ssh encryption
2.1.2.4 Allows branching of code
Handling of branching of code

2.1.3 What are the important usability factors of this tools?

2.1.3.1 No Comment.

Tool 2: Mailman   Mailing List

2.2 Brief Description

Mailman is a mailing list manager that allows multiple public or private mailing lists, usernames/passwords for list members.
Mailing list management system
Allows multiple public or private mailing lists
Provide usernames and passwords for list members.

2.2.2 What are the important features of this tools?

2.2.2.1 No Comment.

2.2.3 What are the important usability factors of this tools?

2.2.3.1 No Comment.

3. What work practices and culture should be promoted?

3.1 They shouldn't promote any particular practice. The heterogeneity of approaches is one of the strengths of the way things are done without these infrastructure sites.
The value of heterogeneity, differences as assets
Nothing should be 'promoted'.

4. What are factors that movitate users to use an IFHOSP site?

4.1 Accessibility (is the site well designed and easy to navigate? Does is respond quickly?)
Ease of use, high usability
Fast access, responsive (high bandwidth and power server)
Well designed site structure for navigation
4.2 Reliability. (is the machine going to get broken into? Are the CVS servers going to go down? Do they do regular backups?)
Reliable
High security
4.3 Cost. (does the site have a monthly fee? Are there lots of banner ads?)
Low Cost or Free
4.4 Available tools
Convenience - provides resources are difficult for an individual to maintain (e.g. web site)
Many tools are provided

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

5.1 Lack of technical documentation on how to set up programs needed to use services. (Like encrypted CVS, or CVS in general)
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
5.2 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.
Not trusting the host of the IFHOSP
Not control the content and the development direction of the IFHOSP
Intellectual property issues - the host of the IFHOSP may impose some rights to the projects hosted
5.3 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.
Legal issues on software distribution
5.4 Lack of reliability
Unreliable
5.5 Lack of features that can be had hosting a project on a locally controlled machine
Not providing the tools or the features needed
Not having enough control over the IFHOSP comparing with a local machine

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

6.1 Easy coordination - there is a central point from which everything is done
Centralised location for project management
6.2 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
Centralised location to find Free Software/Open Source Software
Uniform toolset with uniform interface for users

7. What are the negative results for users in using an IFHOSP site?

7.1 No Comment.

8. What are factors that motivate adminstrators to setup or maintain an IFHOSP site?

8.1 No Comment.

9. What are barriers that prevent adminstrators from setting up or maintaining an IFHOSP site?

9.1 No Comment.

10. What are the positive results for adminstrators in setting up or maintaining an IFHOSP site?

10.1 No Comment.

11. What are the negative results for adminstrators in setting up or maintaining an IFHOSP site?

11.1 No Comment.

12. What are other important issues in IFHOSP?

12.1 Usage agreements - the IFHOSP must be very careful in terms of what they are and aren't allowed to do with the code on their site. Sites that have statements such as "hosting your project here grants the site owners a nonexclusive, royalty free perpetual license to use the software" are not acceptable.
IFHOSP site should be careful on the usage agreements with users and provide them with enough freedom


Hide Summary

Go to List of Participants


Generated On: 27 Sep 2002