@@ -32,7 +32,18 @@ Let's introduce the *inner source framework*.
32
32
33
33
## Governance
34
34
35
- As described by OSSWatch[ ^ 1 ] :
35
+ According to the Business Dictionary, governace is defined as:
36
+
37
+ > Establishment of policies, and continuous monitoring
38
+ > of their proper implementation, by the members of the
39
+ > governing body of an organization. It includes the
40
+ > mechanisms required to balance the powers of the
41
+ > members (with the associated accountability), and
42
+ > their primary duty of enhancing the prosperity and
43
+ > viability of the organization
44
+
45
+ In open source, governance is described in the "governance
46
+ model" document, defined by OSSWatch[ ^ 1 ] as:
36
47
37
48
> A governance model describes the roles that project participants
38
49
> can take on and the process for decision making within the project.
@@ -58,14 +69,80 @@ Usually the governance model is a written document containing:
58
69
59
70
## Technical infrastructure
60
71
72
+ By technical infrastructure we describe the tools used by inner source
73
+ developers for their daily work. Usually, this tools cover:
74
+
75
+ - Source code management systems
76
+
77
+ - Issue/tasks tracking systems
78
+
79
+ - Forums or mailing lists, and "questions and answers" forums
80
+
81
+ - Chat or instant messaging tools
82
+
83
+ - Continous integration systems
84
+
85
+ - Document/knowledge management systems (wikis)
86
+
61
87
## Collaboration as cultural change
62
88
63
- ## Finnancial support
89
+ Creating an engaged community is one of the key points for
90
+ open source projects success and sustainability. Same
91
+ principle applies for inner source projects.
92
+
93
+ Managing a community is different from traditional development teams
94
+ management, so project managers need to adapt their skills
95
+ to the new scenario.
96
+
97
+ Open source communities are very flat organizations where
98
+ leadership is usually more important than formal power.
99
+ Companies adopting inner source need to adapt their
100
+ organizational structure to a flatter one.
101
+
102
+ ## Financial support
103
+
104
+ In a perfect inner source scenario, and based in David Pink quote
105
+ you should pay enough “to take the issue of money off the table.”
106
+
107
+ But we usually don't live in perfect worlds, and there are several
108
+ scenarios where financial support for inner projects are critical:
109
+
110
+ - payment in different geographical regions
111
+
112
+ - employees working in a mix of inner and non-inner source projects
113
+
114
+ - cost sharing between different business units with their own budget
115
+
116
+ - projects developed by a mix of company employees and subcontractors
117
+
118
+ Again, open source provides some examples of how to
119
+ get financial support for their projects, and
120
+ organizations like Linux Foundation, Apache Software Foundation, etc.
121
+ could work as reference, translating their "foundation"
122
+ principles to our companies.
64
123
65
124
## Processes measurement
66
125
126
+ Last but not least, if we are speaking about management, to measure becomes
127
+ a basic skill for us.
128
+
129
+ Beyond collecting data, managers need to understand the goals of the organization
130
+ and how the gathered data can help them to achieve such goals. They also
131
+ need to take care of how they share that data
132
+ with the teams, and what the want to achieve.
133
+
67
134
> “Collecting data is only the first step toward wisdom, but sharing data
68
135
> is the first step toward community.” – Henry Lewis Gates (professor at
69
136
> Harvard)
70
137
138
+ Open measurment gives a lot of benefits for our inner source community:
139
+
140
+ - awareness, it allows us to understand who we are, what we are doing, etc.
141
+
142
+ - governance check, monitoring policies implementatio
143
+
144
+ - transparency, as trust generator for third parties and fairness
145
+ for our inner community
146
+
147
+
71
148
[ ^ 1 ] : http://oss-watch.ac.uk/resources/governancemodels
0 commit comments