Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

Prep InnerSource course on Learning Lab for internal repo visibility #23

Merged
merged 4 commits into from
May 23, 2019
Merged

Prep InnerSource course on Learning Lab for internal repo visibility #23

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d5c26c6
add info about internal visibility
hectorsector May 20, 2019
b9ed6d7
fix formatting of detail block
crichID May 22, 2019
250c55a
tweaks to visibility text
crichID May 22, 2019
bbd11a2
add link to enterprise accounts
hectorsector May 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions responses/02_repo-owner-answer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,20 @@ A repository _does_ exist at githubtraining/training-manual, but it is private.
![gif of repository, pointing to ownership by githubtraining organization, and to a private visibility](https://user-images.githubusercontent.com/6351798/56159957-32413700-5f83-11e9-90f6-c1b64ade39c4.gif)

<details>
<summary>Why can't you see it then? Review the <b>Files Changed</b> tab and see if you can figure it out. Collapse this text if you'd like an explanation.</summary>
<summary>Why can't you see it then? Review the <b>Files Changed</b> tab and see if you can figure it out. Expand this text if you'd like an explanation.</summary>

The repository `training-manual` in the @githubtraining organization is private. It's only visible to members of that organization. If you're not a member of the organization, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work.
</summary>
## Understanding repository visibility

There are three types of repository visiility: **public, internal, and private**.

Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only members of the organizations that an account owns will see it

@hectorsector have we introduced the concept of the enterprise account before now? If not, this may be confusing. Should we back up a bit to address the enterprise account as a tool for InnerSource?


This is an example of why having the right ownership structure is important. Otherwise, it can be difficult for members of your team to find and contribute to projects. Having too many disconnected organizations with restrictive permissions silos and isolates each organization's work.

Here are some recommendations based on some :sparkles: use of GitHub that we've seen:
- Aim for as few organizations as possible. Remember, each organization is a black box to those outside of that organization.
- Use the internal visibility (currently in beta) if you're working on behalf of an account with multiple organizations
- Name your repositories in a meaningful manner. Usually a simple project or application name will suffice.
</summary>
<hr>
</details>

Please merge this pull request.
Expand Down