Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -32,19 +32,16 @@
32	32	(((
33	33	What research method(s) will you use to answer this question? (200)
34	34
35		-Mixed methodology based on literature and artifact reviews, surveys, environmental studies, and interviews supplemented by historiographical analysis of specific projects and corporate users.
	35	+The research design will employ mixed methodologies including literature and artifact reviews, surveys, environmental studies, and interviews supplemented by historiographical analysis of specific projects and corporate users. The intent is to use iterative triangulation to derive variables that describe “business readiness” to be integrated into a maturity-indexing assessment tool. The tool will be openly reviewed for comment and improvement. The investigation will include:
36	36
37		-* Literature review from expert sources, industry press, etc. to identify business and management expectations considered by leaders and decision-makers, investors, and end-users for assessing infrastructure and supporting organizations that ensure continuous value.
38		-* Content analysis to review industry RFP/RFI’s for software infrastructure as evidence of actual expectations considered by leaders and decision-makers, investors, and end-users for assessing infrastructure and supporting organizations that ensure continuous value.
39		-* Interviews of industry leaders to identify expectations considered when assessing infrastructure and supporting organizations to ensure continuous value.
40		-* Literature review from expert sources, industry press, etc. to identify successful open source projects.
41		-* Literature review from expert sources, industry press, etc. to identify key quantitative metrics that define successful project.
42		-** Observational sampling of open source projects based on quantitative metrics of literature review.
43		-* General survey of open source community members to identify those projects perceived as “successful”.
44		-* General survey of business leaders to identify those projects perceived as “successful”.
45		-* Observational sampling to understand the environment and behaviours of open source software development and community practices.
	37	+* Literature review of expert and popular sources to identify business and management expectations of a range of stakeholders for assessing OSS infrastructure relative to perceived business needs.
	38	+* Content analysis of industry RFP/RFI’s for software infrastructure as evidence of actual expectations considered by decision-makers, investors, and end-users while assessing infrastructure reflecting perceived business needs.
	39	+* Interview industry leaders to identify expectations when assessing infrastructure.
46	46
47		-Interviews of open source maintainers to identify best practices for assuring infrastructure and supporting organizations to can deliver continuous value.
	41	+* Literature review of expert and popular sources to identify successful open source projects and key metrics that define successful projects, leading to observational of open source projects to assess the previously identified quantitative metrics.
	42	+* General surveys of OSS community members and business leaders to identify those projects perceived as “successful”.
	43	+* Observational techniques to understand the environment and behaviors of open source software development and community practices.
	44	+* Interviews with OSS maintainers to identify best practices.
48	48	)))
49	49
50	50	== What data or other resources will you use to answer this question? (200) ==
...	...	@@ -77,41 +77,26 @@
77	77	* (% style="font-style: normal;" %)Individuals making adoption decisions for OSS digital infrastructure on the behalf of a range organizational types including businesses, public organizations, government agencies, and OSS communities.
78	78	* (% style="font-style: normal;" %)Maintainers, leaders, and governors of OSS project communities.
79	79
80		-
81	81	(% style="font-style: normal;" %)//**Impact:**//
82	82
83		-
84		-
85	85	* (% style="font-style: normal;" %)//Improved understanding about open production models and how to estimate the “business readiness” of a project and community by digital infrastructure adopters and users.//
86	86
	81	+* (% style="font-style: normal;" %)//Better and more informed decision making on the part of potential adopters.//
87	87
88		-* (% style="font-style: normal;" %)//Better and more informed decision making on the part of potential adaptors.//
89		-
90		-
91	91	* (% style="font-style: normal;" %)//Enhanced willingness by adopters to appropriately support and invest in the OSS project and community to reduce business risk.//
92	92
93		-
94	94	* (% style="font-style: normal;" %)//Improved OSS project business readiness and continuous improvement through use of the OpenBRR Maturity Index tool.//
95	95
96		-
97	97	(% style="font-style: normal;" %)// //
98	98
99		-
100		-
101	101	(% style="font-style: normal;" %)//**Needs of needs marginalized and under-represented communities:**//
102	102
103		-
104		-
105	105	* (% style="font-style: normal;" %)//Ensure that the tool and report is available in accessible formats and licenses, with a commitment to libre and gratis distribution.//
106	106
107	107	* (% style="font-style: normal;" %)//Multi-language presentation.//
108	108
109		-
110	110	// //
111	111
112		-
113		-==== ====
114		-
115	115	==== //Guiding questions: Who is the audience for this work? What do you hope the near and long-term impacts of this work are on the digital infrastructure field? How will this work address the needs marginalized and under-represented communities?// ====
116	116
117	117	==== ====