Open Source ROI Model - Revision history

Tim Bird: /* Dynamics of participation costs */ fix typo

2007-07-17T23:38:08Z

‎Dynamics of participation costs: fix typo

2007-07-17T16:51:17Z

‎Dynamics of participation costs

2007-06-05T22:57:49Z

‎Miscellaneous

2007-06-05T22:56:57Z

‎Effect of experience with open source

2007-05-31T18:40:07Z

‎Miscellaneous

2007-05-31T18:38:47Z

‎Big overview

2007-05-31T18:36:56Z

‎Overview

2007-05-31T18:34:42Z

‎Miscellaneous: add details about measuring

2007-05-31T18:29:32Z

‎Dynamics of participation costs

2007-05-31T18:23:37Z

‎Relevant code dynamics

@@ Line 102: / Line 102: @@
 * Enhancement features or timely bug fixes
 ** Example I took the time to Email Quicken 2004
-*** no resonse
+*** no response
 *** Why should I upgrade
 *** Then they drop support of features that I paid for

@@ Line 100: / Line 100: @@
 *** That is, if the contribution rate is below a certain point, do contributors wander off and abandon the project?
 *** Are there generic parameters that affect this point, or is it project-specific (or market-specific)?
 == Miscellaneous ==

@@ Line 107: / Line 107: @@
 ** Not trying to predict an individual outcome.
 *** e.g. Can't predict how long to invent the light bulb
-*** Can't predict when a particular drive will be written (or a particular problem solved)
+*** Can't predict when a particular driver will be written (or a particular problem solved)
 ** Is it possible to predict the code size of the Linux kernel for 2008, 2009, etc.?
 ** Is it possible to predict the number of supported ARM platforms in the future?

@@ Line 80: / Line 80: @@
 ** What is the magnitude of the learning curve for participating?
 ** Does the learning curve increase over time (I believe it does, as complexity of code bases grow)
-* Can this be measured by examining
+* Can this be measured by examining contribution rate from individuals over time (if they stick with it)?
 == Dynamics of network effects ==

@@ Line 107: / Line 107: @@
 *** e.g. Can't predict how long to invent the light bulb
 *** Can't predict when a particular drive will be written (or a particular problem solved)
-** Is it possible to predict the code size of the Linux kernel for 2008, 2009, etc.
+** Is it possible to predict the code size of the Linux kernel for 2008, 2009, etc.?
 ** Is it possible to predict the number of supported ARM platforms in the future?
-** As granularity increases, quantum effects dominate
+* As granularity increases, quantum effects dominate
 ** So, what '''CAN''' be measured?
 * Trying to get an estimate for amount of code that will not have to be written or bought, in future
-** Trying to determine factors that affect that, so it can be increased
+** Trying to determine factors which affect that, so it can be increased

@@ Line 30: / Line 30: @@
 * Total return from open source = value of code that is relevant to your product, minus acquisition and integration cost, minus participation cost
-** Let RP = value of code relevant to your product
+** Let PRCV = value of code relevant to your product (Product-Relevant Code Value)
 ** Let AC = acquisition cost
 ** Let IC = integration cost
 ** Let PC = participation cost
-* the formula becomes ROI = RP - AC - IC - PC
+* the formula becomes ROI = PRCV - AC - IC - PC
 * Acquisition cost = license fees plus subscription fees plus downloading costs

@@ Line 21: / Line 21: @@
 Right now, this is just a loose collection of ideas for things that affect ROI.  Maybe someday, I'll turn this
-into a more formal paper, and try to collect metrics for some of the factors mentioned below. --[[User:TimBird|TimBird]] 21:16, 31 May 2007 (EEST)
+into a more formal paper, and try to collect metrics for some of the factors mentioned below.
 == Big overview ==

← Older revision		Revision as of 18:34, 31 May 2007
Line 99:		Line 99:
	* What about "quantum effects"?		* What about "quantum effects"?
	** a single developer or single company may significantly affect the outcome		** a single developer or single company may significantly affect the outcome
		+	* How do you predict the future when it is completely dependent on individual contributions?
		+	** Not trying to predict an individual outcome.
		+	*** e.g. Can't predict how long to invent the light bulb
		+	*** Can't predict when a particular drive will be written (or a particular problem solved)
		+	** Is it possible to predict the code size of the Linux kernel for 2008, 2009, etc.
		+	** Is it possible to predict the number of supported ARM platforms in the future?
		+	** As granularity increases, quantum effects dominate
		+	** So, what '''CAN''' be measured?
		+	* Trying to get an estimate for amount of code that will not have to be written or bought, in future
		+	** Trying to determine factors that affect that, so it can be increased

@@ Line 89: / Line 89: @@
 * as participation increasing, training cost go down
 ** finding cost is reduced
-** mainlinging cost is reduced
+** mainlining cost is reduced
 ** integration cost is reduced??
 == Miscellaneous ==
 * What about "quantum effects"?
 ** a single developer or single company may significantly affect the outcome

@@ Line 45: / Line 45: @@
 *** Adaptation costs likely decrease when older hardware is used (due to software "showing up" for hardware over time)
-== Relevant code dynamics ==
+== Issues regarding Relevant code ==
-* the amount of relevant code depends on the total size of the available code, and the uniqueness of your hardware
+* the value of relevant code depends on the total size of the available code, and the uniqueness of your hardware
 ** total size of available code depends on the contribution amount and contribution value (and contribution rate, over time)
 ** contribution amount depends on size of contributor pool
@@ Line 54: / Line 57: @@
 * size of relevant code depends on network size (and network quality)?
 ** maybe network size should not be measured in people, but by contribution rate?
 == Effect of mainlining code ==