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
There is also the [workbook](workbook/), a collection of questions and answers on based on the videos and articles for people to check their knowledge against after consuming the material.
19
19
20
20
New sections and segments may be added at any time via the [contribution] process.
@@ -25,7 +25,7 @@ The InnerSource Learning Path is produced via the [InnerSource Commons] communit
25
25
We coordinate our work in the [#learning-path]_Slack_ channel.
26
26
We track our tasks and discuss their status openly using our GitHub project [Kanban board].
27
27
28
-
Typically, a card bundles tasks about one artifact (e.g. written articles accompanying one learning path section) or small milestones (e.g. finishing the post production of one section).
28
+
Typically, a card bundles tasks about one artifact (e.g. written articles accompanying one learning path section) or small milestones (e.g. finishing the post production of one section).
29
29
You can infer whether a task is currently actively developed or under review based on the card's column in the [Kanban board].
30
30
31
31
## Trusted Committers
@@ -67,7 +67,7 @@ workbook/0n-section-name.asciidoc // Contains the part of the workbook matching
67
67
After material is finished the scripts will be used to film videos.
68
68
Each video should be about 5min in length.
69
69
Each article should be about a page long.
70
-
The idea is that a person could receive a link to an article or video and watch or read it without having to set aside time in advance to do so.
70
+
The idea is that a person could receive a link to an article or video and watch or read it without having to set aside time in advance to do so.
71
71
Videos, articles, and workbooks will be published at _learning.oreilly.com_ and also at _innersourcecommons.org_.
Copy file name to clipboardExpand all lines: introduction/05-principles.asciidoc
+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
@@ -41,7 +41,7 @@ This means that guest teams should be able to have an understanding of:
41
41
* Decision making of the host team
42
42
43
43
When possible, the above should be communicated clearly and in detail, from teams' internal definitions of items to special-case scenarios specific to the project.
44
-
This communication should be done in a manner that can be easily queried and understood to those that are not part of the core team.
44
+
This communication should be done in a manner that can be easily queried and understood to those that are not part of the host team.
Copy file name to clipboardExpand all lines: introduction/07-faq.asciidoc
+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
@@ -24,7 +24,7 @@ It depends on how far you're going. You'll probably be going a lot further than
24
24
image::https://user-images.githubusercontent.com/9609562/151901209-52b3468b-dedd-4319-9ca3-38b6b2bcfaf5.png[If you want to go fast, go alone. If you want to go far, go together]
25
25
26
26
=== Will we just be reviewing PRs all day every day?
27
-
If so then your core team is understaffed. A healthy team is staffed so that there is time for assisting contributors and making core contributions yourself.
27
+
If so then your https://patterns.innersourcecommons.org/p/core-team[core team] is understaffed. A healthy team is staffed so that there is time for assisting contributors and making core contributions yourself.
28
28
29
29
You can mitigate this by setting expectation, potentially via SLAs. If contributors expect PR reviews within an hour, maybe you will be stuck reviewing PRs all the time, but if you set an SLA of 1 day or 1 week, this won't be the case.
0 commit comments