1876
Comment:
|
1858
|
Deletions are marked like this. | Additions are marked like this. |
Line 23: | Line 23: |
about code, language, style of development, modularity, accessibility to users interested in touching the code, etc. |
about code, language, style of development, modularity, accessibility to users interested in touching the code, etc. |
Line 27: | Line 27: |
Does it distinguish between stable and unstable releases? Are unstable releases usable? |
Does it distinguish between stable and unstable releases? Are unstable releases usable? |
Line 31: | Line 31: |
communities around the tool? Is it vibrant? Open to newcomers? Helpful? Focused? |
communities around the tool? Is it vibrant? Open to newcomers? Helpful? Focused? |
Line 35: | Line 35: |
Is there a manifesto? What happens with new ideas which may deviate a bit from a given direction? |
Is there a manifesto? What happens with new ideas which may deviate a bit from a given direction? |
Line 39: | Line 39: |
Can it be used in more than one way? Does it have multiple interfaces? | Can it be used in more than one way? Does it have multiple interfaces? |
Factors affecting diffusions in OSS
The following factors influence the rate of adoption of tools in subject communities. The theory is that certain aspects of a tool determine whether it will be quickly and widely used.
In this list, I attempt to bring together all factors which could have any influence on the rate of adoption, not only those likely to speed things up; my research is about finding out which ones make more of a difference and which ones can be safely ignored.
If you feel like adding your thoughts to a factor, please feel free. It would help if you'd prefix your comments with your name so that I know how to contact you if I have questions and so that I can give appropriate credit.
Also see ["madduck/adoptions"] for a list of tools which have or have not been adopted by developers of the Debian project. Feel free to extend this list as well.
I use the following categories for factors (please extend as you see fit):
- [wiki:/implementation Implementation]: how is a tool implemented? This is about code, language, style of development, modularity, accessibility to users interested in touching the code, etc.
- [wiki:/maintenance Maintenance status]: how well is the tool maintained? Does it distinguish between stable and unstable releases? Are unstable releases usable?
- [wiki:/community Community]: what are the traits of the developer and user communities around the tool? Is it vibrant? Open to newcomers? Helpful? Focused?
- [wiki:/direction Direction]: does the project follow a defined direction? Is there a manifesto? What happens with new ideas which may deviate a bit from a given direction?
- [wiki:/usability Usability]: how usable is the tool? Is it well-documented? Can it be used in more than one way? Does it have multiple interfaces?