Differences between revisions 1 and 2
Revision 1 as of 2007-09-18 18:55:28
Size: 1760
Editor: madduck
Comment:
Revision 2 as of 2007-09-18 18:57:03
Size: 1790
Editor: madduck
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
* [/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:/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.
Line 16: Line 16:
* [/maintenance Maintenance status]: how well is the tool maintained? Does it distinguish between stable and unstable releases? Are unstable releases usable?  * [wiki:/maintenance Maintenance status]: how well is the tool maintained? Does it distinguish between stable and unstable releases? Are unstable releases usable?
Line 18: Line 18:
* [/community Community]: what are the traits of the developer and user communities around the tool? Is it vibrant? Open to newcomers? Helpful? Focused?  * [wiki:/community Community]: what are the traits of the developer and user communities around the tool? Is it vibrant? Open to newcomers? Helpful? Focused?
Line 20: Line 20:
* [/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:/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?
Line 22: Line 22:
* [/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?  * [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?

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.

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?