You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Our mission
38
38
*[Common Requirements](patterns/2-structured/common-requirements.md) - *Common code in a shared repository isn't meeting the needs of all the project-teams that want to use it; this is solved through requirements alignment and refactoring.*
39
39
*[Contracted Contributor](patterns/2-structured/contracted-contributor.md) - *Associates wanting to contribute to InnerSource are discouraged from doing so by their line management. Relief is provided by formal contracts and agreements.*
40
40
*[Dedicated Community Leader](patterns/2-structured/dedicated-community-leader.md) - *Select people with both communications and technical skills to lead the communities to ensure success in starting an InnerSource initiative.*
41
-
*[Feature Owners](patterns/2-structured/feature-owners.md) - *This pattern is for scaling inner source project contributions and for aspirant associates who are looking for more accountability, develop their soft skills and be successful at work.*
41
+
*[Feature Owners](patterns/2-structured/feature-owners.md) - *This pattern is for scaling inner source project contributions and for aspirant employees who are looking for more accountability, develop their soft skills and be successful at work.*
42
42
*[Gig Marketplace](patterns/2-structured/gig-marketplace.md) - *Establish a marketplace by creating an intranet website that lists specific InnerSource project needs as "Gigs" with explicit time and skill requirements. This will enable managers to better understand their employee’s time commitment and professional benefits thereby increasing the likelihood of garnering approval to make InnerSource contributions.*
43
43
*[Maturity Model](patterns/2-structured/maturity-model.md) - *Teams have started adopting InnerSource. The practice is spreading to multiple departments. Understanding of what constitutes an InnerSource project are wide spread though. The solution is to provide a maturity model to allow for teams to go through a self check and discover patterns and practices that they are not yet aware of.*
44
44
*[InnerSource License](patterns/2-structured/innersource-license.md) - *Two legal entities that belong to the same organization want to share software source code with each other but they are concerned about the implications in terms of legal liabilities or cross-company accounting. An InnerSource License provides a reusable legal framework for the sharing of source code within the organization. This opens up new collaboration options, and makes the rights and obligations of the involved legal entities explicit.*
Copy file name to clipboardExpand all lines: patterns/2-structured/feature-owners.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@ Feature Owners
4
4
5
5
## Patlet
6
6
7
-
This pattern is for scaling inner source project contributions aligned with business initiatives and for aspirant associates who are looking for stretch assignments, more accountability, develop their soft skills and be successful at work.
7
+
This pattern is for scaling inner source project contributions aligned with business initiatives and for aspirant employees who are looking for stretch assignments, more accountability, develop their soft skills and be successful at work.
8
8
9
9
## Problem
10
10
11
11
Contributions in innersource projects mostly are all volunteer based. Below are the challenges we see in day-to-day life:
12
12
- How to increase more contributions in the project.
13
-
- How to create opportunities for associates who want to play more than an individual contributor role and are looking for:
13
+
- How to create opportunities for employees who want to play more than an individual contributor role and are looking for:
14
14
- Elevating leadership skills.
15
15
- More visibility at work.
16
16
- More accountability.
@@ -19,7 +19,7 @@ Contributions in innersource projects mostly are all volunteer based. Below are
19
19
20
20
## Story
21
21
22
-
A single project which is on high demand and consumption is increasing every month. We need to expand the contributions and add new functionalities. But associates have a concern on how they can play more than an individual contributor role and which will motivate them to contribute more.
22
+
A single project which is on high demand and consumption is increasing every month. We need to expand the contributions and add new functionalities. But employees have a concern on how they can play more than an individual contributor role and which will motivate them to contribute more.
23
23
24
24
## Context
25
25
@@ -37,7 +37,7 @@ Business & [Community leader](patterns/2-structured/core-team.md) looking for sc
37
37
38
38
Define all the features needed in the project. Per definition, <em>"A feature is the product's service/function that provides business value, meets customer needs and must be able to be done in 2-3 months".</em>
39
39
40
-
Invite all contributors for open participation. Empower associates to pick the features which they would be interested in and become feature owners. There can be more than one owner for any given feature.
40
+
Invite all contributors for open participation. Empower employees to pick the features which they would be interested in and become feature owners. There can be more than one owner for any given feature.
0 commit comments