Skip to content

Add Gitlab tool content #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add Gitlab tool content #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce7b09d
first commit
yenk Feb 19, 2025
a4ab116
add gitlab config content
yenk Feb 20, 2025
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
30 changes: 30 additions & 0 deletions tooling/gitlab-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,31 @@
# GitLab InnerSource Configuration

- [Layering Source Control Management Configurations](#layering-source-control-management-configurations)
- [Enterprise Setting](#enterprise-setting)
- [Repository policies](#repository-policies)
- [Base permissions](#base-permissions)
- [Repository creation](#repository-creation)
- [Repository forking (Private / Internal)](#repository-forking-private--internal)
- [Organization Setting](#organization-setting)
- [Member privileges](#member-privileges)
- [Base permissions](#base-permissions-1)
- [Repository creation](#repository-creation-1)
- [Repository forking](#repository-forking)
- [GitHub Enterprise Server Setting](#github-enterprise-server-setting)
- [GitHub Connect - Server statistics](#github-connect---server-statistics)
- [Resources](#resources)

## Self-Managed and Free with Customization
GitLab is a self-managed configured source controlled platform. We can a lot of autonomy with that for being a free tier patform. With that said, there are of course pros and cons to having the ability to self-managed. We will need to configure and customize based on our organizational needs.

Here is an [overview](https://docs.gitlab.com/administration/configure/) of what we can configure within GitLab.

There are various tiers of self-administering hierarchy within GitLab that InnerSource Commons can based on depending on the scope of project,organization, or user specifics.

### GitLab Administration Layers

**By organizations**
<On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can enable the feature flag named ui_for_organizations. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use.>

**By projects**
**By users**
1 change: 1 addition & 0 deletions tooling/innersource-tooling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,3 +36,4 @@ for a perspective focused entirely on security.
- [Resources](./github-configuration.md/#resources)

### GitLab
For GitLab, we are using a similar set of de factos - [GitHub InnerSource Strategies](./github-strategy.md#github-innersource-strategies) as that should not changed much in terms of InnerSource security, access, and various setting protocols prescribed under InnerSource Commons principles.