Getting Started with Open Source Development

110 Getting started with open source development
It is the responsibility of the documentation writer to ensure that every person can
use the software in hand.
4. Translators are needed because OSS communities are worldwide communities.
Though every member must have some English skills, having documentation in
their own language will help.
5. Two guidelines can be:
6. E
7. B
8. C
9. A
10. C
- Search before you ask.
- Do not engage in acts of verbal aggression.
Chapter 6
1. Before starting an open source software development project, a person must
evaluate following two key points:
A. What is the fundamental idea or requirement of your software? Do you feel
many people would have same kind of requirements?
B. Is there any software already available in the market for the same purpose? If
yes, where does your product stand out i.e. why would people use it?
2. Following are the basic steps for setting up the infrastructure of the project:
A. Fix a definite mission or goal for your project.
B. Plan a roadmap or strategy to accomplish your objective.
C. Find people.
D. Understand the basic needs of your project and community.
E. Arrange for necessary funds.
3. Once you get a few members for your community, encourage all of them to
publicize your community. This makes the awareness effort multiplied by the
number of members.
4. Users always prefer licenses which are well known in the industry (e.g. BSD, GPL,
etc.). An unfamiliar license, even if it is very short, simple, and straight forward may
discourage some users from choosing your software and contribute in the project.
So, it is always recommended to select an unchanged version of a well known,