Skip to content

Commit 8da867d

Browse files
committed
chore: fix typos, fix more naming issues
1 parent 46408cb commit 8da867d

11 files changed

Lines changed: 41 additions & 41 deletions

File tree

‎.github/ISSUE_TEMPLATE/join-wg.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
name: Join InnerSoure Working Group
3-
description: Use this issue to join the InnerSoure Working Group
4-
title: Join InnerSoure Working Group
2+
name: Join InnerSource Working Group
3+
description: Use this issue to join the InnerSource Working Group
4+
title: Join InnerSource Working Group
55
labels: ''
66
assignees:
77
- rrrutledge
@@ -10,11 +10,11 @@ assignees:
1010
- dellagustin-sap
1111
---
1212

13-
It would be great to have you in the InnerSoure Working Group!
13+
It would be great to have you in the InnerSource Working Group!
1414

1515
After you open this issue, one of the assignees will perform these steps to get you set up with the working group:
1616

17-
- [ ] Send an invite to to join the ["InnerSoure Working Group" GitHub team](https://github.com/orgs/InnerSourceCommons/teams/innersource-working-group).
17+
- [ ] Send an invite to to join the ["InnerSource Working Group" GitHub team](https://github.com/orgs/InnerSourceCommons/teams/innersource-working-group).
1818
Click through all of the confirmations and warnings.
1919
- [ ] Find the person's email from their Slack profile and add them to the [recurring meeting](https://calendar.google.com/calendar/u/0/r/eventedit/MHFhYnNnOXJrMDFscmw4ZHRzcW12Z28zcDRfMjAyNDA1MDZUMTUwMDAwWiBjXzYyNjk0ZjQxNDA1NWFjNTY5ZTVjYjEyZGFmYmIwODkwY2EyMmYzNjQwYjE3N2E0YjEwYjUzMTcxZmJjOWJkZDRAZw) (this and future events).
2020
- [ ] Close the issue.

‎.github/workflows/generate-slides.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
name: Generate InnerSoure Working Group Slides
1+
name: Generate InnerSource Working Group Slides
22
on:
33
push:
44
branches: [main]

‎CONTRIBUTING.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# How Do I Contribute to the InnerSoure Working Group?
1+
# How Do I Contribute to the InnerSource Working Group?
22

33
Welcome!
44

@@ -16,7 +16,7 @@ Check out our [README.md] for more details.
1616
```mermaid
1717
sequenceDiagram
1818
participant You
19-
participant WG as InnerSoure Working Group
19+
participant WG as InnerSource Working Group
2020
participant MIP as Managing InnerSource Projects Book
2121
participant ISP as InnerSource Patterns
2222
@@ -45,11 +45,11 @@ this working group. Contributions improve content in the
4545
[InnerSource Learning Path] segment.
4646

4747
Slides, spreadsheets, and other artifacts not easily represented elsewhere can
48-
go in the [InnerSoure Working Group GDrive]. Be sure to attribute all the
48+
go in the [InnerSource Working Group GDrive]. Be sure to attribute all the
4949
contributors to the resulting work (e.g., in the _Authors_ or
5050
_Acknowledgements_ sections of Patterns).
5151

52-
To contribute, get access to the board by [joining the InnerSoure Working Group team].
52+
To contribute, get access to the board by [joining the InnerSource Working Group team].
5353

5454
We track the production of our content on a [Kanban board] with the following
5555
columns:
@@ -125,12 +125,12 @@ docker compose up
125125
You should be able to access the website at <http://localhost:4000/innersource-working-group/>
126126

127127
[Kanban board]: https://github.com/orgs/InnerSourceCommons/projects/4/views/1
128-
[joining the InnerSoure Working Group team]: https://github.com/InnerSourceCommons/innersource-working-group/issues/new/choose
128+
[joining the InnerSource Working Group team]: https://github.com/InnerSourceCommons/innersource-working-group/issues/new/choose
129129
[#innersource-working-group]: https://app.slack.com/client/T04PXKRM0/C04DT6NQX7G
130130
[InnerSource Commons Slack]: https://innersourcecommons.org/slack
131131
[README.md]: ./README.md
132132
[InnerSource Learning Path]: https://github.com/InnerSourceCommons/InnerSourceLearningPath
133-
[InnerSoure Working Group GDrive]: https://drive.google.com/drive/folders/1zhP_wQQFf1cIHnkTUZtBGuLhEUYXzvlC
133+
[InnerSource Working Group GDrive]: https://drive.google.com/drive/folders/1zhP_wQQFf1cIHnkTUZtBGuLhEUYXzvlC
134134
[Project Template]: https://github.com/orgs/InnerSourceCommons/projects/18?query=is%3Aopen+sort%3Aupdated-desc
135135
[InnerSource Patterns]: https://github.com/InnerSourceCommons/InnerSourcePatterns#list-of-patterns
136136
[Managing InnerSource Projects]: https://github.com/InnerSourceCommons/managing-inner-source-projects

‎README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# InnerSoure Working Group
1+
# InnerSource Working Group
22

33
The purpose of this working group is to support InnerSource Program Offices (ISPOs) with materials needed to establish themselves, educate partners and stakeholders, and scale InnerSource in their respective company.
44
This material could be directed towards senior leaders, managers, or individuals in a variety of roles.
@@ -36,7 +36,7 @@ These two examples follow the same pattern - providing directly-usable materials
3636

3737
## Joining the Working Group
3838

39-
To chat with everybody in the InnerSoure Working Group, please join us in the _[#innersource-working-group]_ channel in [slack].
39+
To chat with everybody in the InnerSource Working Group, please join us in the _[#innersource-working-group]_ channel in [slack].
4040

4141
You can find our public meetings on the [InnerSource Commons Public Calendar] (recurring every-other-Monday).
4242
Add to your calendar and join us!
@@ -55,7 +55,7 @@ Here is our [working group documentation site].
5555

5656
## Trusted Committers
5757

58-
These people regularly give their time to the running of the InnerSoure Working Group.
58+
These people regularly give their time to the running of the InnerSource Working Group.
5959
Special thanks to:
6060

6161
* Russ Rutledge ([@rrrutledge](https://github.com/rrrutledge))

‎_config.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# See https://github.com/InnerSourceCommons/working-group-roles for an explanation of this file.
22

3-
title: "InnerSoure Working Group"
3+
title: "InnerSource Working Group"
44
description: "The purpose of this working group is to support InnerSource Program Offices (ISPOs) with materials needed to establish themselves, teach and scale InnerSource in their respective company. This material could be directed towards senior leaders, managers, or individuals in a variety of roles."
55

66
backlink: InnerSource Commons, https://innersourcecommons.org/community/
@@ -13,7 +13,7 @@ links:
1313
# The #innersource-working-group channel in the innersourcecommons Slack.
1414
chat: https://app.slack.com/client/T04PXKRM0/C04DT6NQX7G
1515

16-
# The "InnerSoure Working Group" folder.
16+
# The "InnerSource Working Group" folder.
1717
folder: https://drive.google.com/drive/folders/1vFJPuQ5l0hKIlC58qjdV1MNSIhdoSBCz
1818

1919
# Our Google Sheets attendance.

‎docs/adding-trusted-committers.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
1-
This document describes how to add a new Trusted Committer to the InnerSoure Working Group.
1+
This document describes how to add a new Trusted Committer to the InnerSource Working Group.
22

33
1. Share your suggestion for new Trusted Committer in the [#innersource-working-group-trusted-committers] private _Slack_ channel.
44
2. If you have some agreement (or even [lazy consensus](https://community.apache.org/committers/lazyConsensus.html)), then move forward.
5-
3. Let the person know that they've been accepted as a Trusted Committer in the InnerSoure Working Group.
5+
3. Let the person know that they've been accepted as a Trusted Committer in the InnerSource Working Group.
66
4. If they want to be a Trusted Committer, then move forward.
77
5. Update the ["Trusted Committers" section of the README](../README.md#trusted-committers) to list the new person.
88
6. Invite the person into the [#innersource-working-group-trusted-committers] _Slack_ channel.
99
7. Add the person to the [@InnerSourceCommons/innersource-working-group-trusted-committers] _GitHub_ team.
1010
8. Make the person an owner of the [@InnerSourceCommons/innersource-working-group-trusted-committers] _GitHub_ team.
1111
9. Add the person as an assignee for the ["Join Working Group" issue template](https://github.com/InnerSourceCommons/innersource-working-group/edit/main/.github/ISSUE_TEMPLATE/join-wg.yml).
12-
10. Invite the person to the InnerSoure Working Group Trusted Committers meeting.
12+
10. Invite the person to the InnerSource Working Group Trusted Committers meeting.
1313
11. Give a shout-out and congratulations to the person in the [#innersource-working-group] channel for becoming a Trusted Committer.
1414

1515
[#innersource-working-group-trusted-committers]: https://app.slack.com/client/T04PXKRM0/C05QTAZC5PZ

‎docs/diagrams/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# InnerSoure Working Group Diagrams
1+
# InnerSource Working Group Diagrams
22

3-
This directory contains diagrams for the InnerSoure Working Group.
3+
This directory contains diagrams for the InnerSource Working Group.
44

55
## Diagrams
66

‎docs/slides/quick-ispo-intro/quick-ispo-intro.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@ theme: ispowg
44
themeSet: ../themes
55
---
66

7-
# Welcome to the InnerSoure Working Group! 🎉
7+
# Welcome to the InnerSource Working Group! 🎉
88

99
## Quick 10-Min Intro
1010

11-
The InnerSource Program Office (ISPO) Working Group is a group of people who are interested in improving the internal code collaboration experience at full organization scale.
11+
The InnerSource Working Group (ISWG) is a group of people who are interested in improving the internal code collaboration experience at full organization scale.
1212

1313
<!--
14-
The InnerSource Program Office (ISPO) Working Group is a group of people who are interested in improving the internal code collaboration experience at full organization scale.
14+
The InnerSource Working Group (ISWG) is a group of people who are interested in improving the internal code collaboration experience at full organization scale.
1515
-->
1616

1717
---

‎docs/slides/scripts/generate-slides.sh‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
#!/bin/bash
22
set -uo pipefail
33

4-
# Generate InnerSoure Working Group Slides
4+
# Generate InnerSource Working Group Slides
55
# This script can be run locally to test slide generation
66
#
77
# Usage: ./docs/slides/scripts/generate-slides.sh

‎docs/slides/summit/innersource-summit.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
marp: true
33
---
44

5-
# The InnerSource Program Office (ISPO) Working Group
5+
# The InnerSource Program Office (ISWG) Working Group
66
<!--- Opening Statement --->
77

88
![bg right 60%](../assets/innersource-commons.svg)
@@ -11,7 +11,7 @@ The working group creates resources for enterprise InnerSource teams.
1111

1212
<!--
1313
Hello, Jeff and I are going to talk to you today about the
14-
InnerSoure Working Group, which is a working group within the InnerSource commons
14+
InnerSource Working Group, which is a working group within the InnerSource commons
1515
devoted to creating shared resources for people working on InnerSource at an Enterprise level.
1616
-->
1717

@@ -72,13 +72,13 @@ who we are trying to reach today with this presentation and working group.
7272

7373
![bg right:40%](../assets/managing-innersource-projects-cover.jpg)
7474

75-
Q: WHY is the InnerSoure Working Group a subset of InnerSource Commons?
75+
Q: WHY is the InnerSource Working Group a subset of InnerSource Commons?
7676

7777
A: We focus on accelerating teams that run and support InnerSource across an organization rather than individuals.
7878

7979
<!--
8080
81-
The InnerSoure Working Group focuses on a subset of the larger InnerSource Commons scope.
81+
The InnerSource Working Group focuses on a subset of the larger InnerSource Commons scope.
8282
8383
We focus on guidance for
8484
the teams that run and support InnerSource across an enterprise or agency rather than guidance at the project or individual level.
@@ -97,14 +97,14 @@ on elements specific to centralized teams driving InnerSource at company-wide sc
9797

9898
<!--- Our objective: Key Message --->
9999

100-
Our objective in this presentation is to help you discover the benefits of our InnerSoure Working Group.
100+
Our objective in this presentation is to help you discover the benefits of our InnerSource Working Group.
101101

102102
https://github.com/InnerSourceCommons/innersource-working-group/blob/main/CONTRIBUTING.md
103103

104104
<!--
105105
106106
Our goal for this talk is to help you learn about the
107-
InnerSoure Working Group and how it might benefit you.
107+
InnerSource Working Group and how it might benefit you.
108108
109109
In addition to the content in this talk, you can
110110
check out similar information in the contributing.md
@@ -219,7 +219,7 @@ What did I get from contributing to Source Code Management project?
219219
<!--
220220
221221
The source code management challenge is one area where I have personally
222-
participated in creating InnerSoure Working Group content.
222+
participated in creating InnerSource Working Group content.
223223
224224
There are several reasons why I took part in this challenge area:
225225
@@ -279,7 +279,7 @@ Looking ahead, this experience isn't a one-time benefit. When my company expands
279279
---
280280
<!--- How do we operate?: Key Message --->
281281

282-
## How the InnerSoure Working Group operates
282+
## How the InnerSource Working Group operates
283283

284284
![bg right 100%](../assets/how-innersource-working-group-operates.png)
285285

@@ -340,7 +340,7 @@ We contribute to the Managing InnerSource Projects Gitbook, InnerSource Patterns
340340

341341
![bg right 60%](../assets/creative.png)
342342

343-
***The InnerSoure Working Group can be your force multiplier!***
343+
***The InnerSource Working Group can be your force multiplier!***
344344

345345
*What challenges are you facing?*
346346

@@ -357,7 +357,7 @@ Is there a challenge you’ve facing today?
357357

358358
![bg right 60%](../assets/collaboration.png)
359359

360-
Attend an InnerSoure Working Group meeting
360+
Attend an InnerSource Working Group meeting
361361

362362
Get meeting invites by adding an issue:
363363

@@ -374,7 +374,7 @@ https://github.com/InnerSourceCommons/innersource-working-group/issues/new
374374

375375
<!--
376376
377-
Attend the InnerSoure Working Group meeting on November 2nd.
377+
Attend the InnerSource Working Group meeting on November 2nd.
378378
379379
-->
380380

@@ -404,7 +404,7 @@ Collaboration opportunities, code reuse, knowedge sharing through community, and
404404

405405
<!---
406406
407-
The InnerSource Program Office (ISPO) Working Group is an opportunity for those involved in enterprise-level software development.
407+
The InnerSource Working Group (ISWG) is an opportunity for those involved in enterprise-level software development.
408408
409409
Whether you're a member of an ISPO, OSPO, Platform Engineering Team, or other centralized groups, you'll find benefits .
410410

0 commit comments

Comments
 (0)