Last modified by Joseph Potvin on 2023/02/17 01:53

Show last authors
1 {{toc numbered="true"/}}
2
3 Free/libre/open works involve multi-organizational joint or collective authorship and distribution of re-usable digital data, information or knowledge works, which the parties each consider to be helpful towards achieving their business goals. They put in place arrangements across organizational boundaries to collectively self-supply specific solutions that meet their respective goals.
4
5 Each cooperating individual or team within the project community allocates resources for collective use when the benefits, risk management and/or cost outcomes of this collaboration are more attractive than what they could achieve via a solo implementation, or through any other available option. No individual or team would have a business incentive to participate in the creation or maintenance of a free/libre/open work unless the outcome were more:
6
7 * **Cost effective:** If equivalent outcomes can be obtained by some other route that takes less time and money, then the other option should be engaged.
8 or
9 * **Cost efficient:** Net outcome improvements from participation should be justifiable in view of relative amount of time and money require for participation.
10
11 Many managers have reported significant benefits through collective self-provisioning through open source methods:
12
13 >// • "Saved us $120K this year, but several hundred thousand dollars in time savings";//
14 >// • "We have seen a 75% cost savings, and we have significantly advanced our time­lines";//
15 >// • "What would have taken us two years to put into place, we accomplished in three weeks";//
16 >// • "It is unbelievably cost effective by as much as a factor of 10".//
17
18
19 These results are consistent with a view of ethical business as an optimal form of rationality. (See pg 12 in: //Economic rationality and ethical behavior// http://ideas.repec.org/p/upf/upfgen/584.html ) The set of economic purposes served, and the value proposition for organizations, is to enable participating projects, services and their partners to augment benefits, better manage risk, and reduce costs through collaborative provisioning and inter-organizational learning, across boundaries in cooperation with other teams and organizations.
20
21 = Augment Benefits =
22
23 * Optimize the pace of innovation through inter-organizational collaboration and learning:
24 ** International
25 ** Cross-sector/Cross-departmental
26 ** Cross-industry
27 * Leverage existing intellectual and informatics works that have already been paid for
28 * Foster an agile and competitive environment by reducing barriers to entry
29 * Strengthen in-house and/or independent security, management and financial control
30 * Diversify and decentralize opportunities for employment and business
31 ** Customization for niche requirements
32 ** Opportunities for small/medium enterprise outside major cities
33 * Engage internal and external expertise
34 ** Different core competencies
35 ** Quality assurance community
36 ** Implementation community
37
38 = Manage Risk =
39
40 * Distribute risk amongst multiple participant-tenants
41 * Advance and protect the "knowledge commons"
42 * Outlast team/organization (sustainability)‏
43 * Learn from peer review feedback
44 ** Praise and/or criticism
45 ** Confirmation/rejection of assumptions
46 ** Personnel retention & succession management
47
48 = Reduce Costs‏ =
49
50 * Reuse components (own & others)‏
51 ** Redirect creativity, effort and spending out of redundancy and idiosyncrasy
52 ** Externalize some costs of creation/evolution
53 ** Retain the freedom to stand still (no forced obsolescence/upgrades)
54 * Reduce time and money required for legal reviews
55 ** Reduce or eliminate the requirement for “non-disclosure agreements”
56 ** Simplify copyright license management
57 ** Rely upon general purpose re-usable licenses
58 * Reduce start-up and delivery times
59 ** Engage international standards by default
60 ** Align to a more elegant modular architecture
61 ** Allow for more agile systems development
62 ** Retain freedom to adapt to requirements

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation