Skip to content

Commit 8bb83a8

Browse files
nazunalikanazunalika
authoredJan 14, 2025··
Merge pull request #122 from neil-forks/sig-guide/onboarding
update sig guide, add git agreement. modify git agreement to not disallow company devices
2 parents 81dc2a9 + 26f165a commit 8bb83a8

File tree

7 files changed

+420
-26
lines changed

7 files changed

+420
-26
lines changed
 

‎docs/contributing/git.md

+210
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,210 @@
1+
---
2+
title: Rocky Linux Git Contributor Agreement
3+
---
4+
5+
Account Services helps the Rocky Enterprise Software Foundation keep track of
6+
contributors as well as the projects that they work on. This agreement goes over
7+
the RESF Git Service (Gitea) and the Rocky Linux GitLab instance, as well as
8+
their overall usage and what is expected for contributors.
9+
10+
We require that contributors of Rocky (RESF) accept the following agreement, as
11+
it provides access to the RESF Git Service.
12+
13+
Please read carefully before accepting this agreement.
14+
15+
Preface
16+
=======
17+
18+
The RESF Git Service (Gitea) is a core part of the Rocky Enterprise Software
19+
Foundation. It is used to host code/software that is under the RESF or provide
20+
the teams within the Rocky ecosystem to manage their own projects, code, wiki,
21+
and so on. It will also act as a mirror for some repositories from the Rocky
22+
GitHub organizations and in some special cases, mirrors from the Rocky Linux
23+
GitLab instance.
24+
25+
The Rocky Linux GitLab instance is a core part of the Rocky Linux build
26+
ecosystem, and thus a mode of the development process for the distribution and
27+
available software. Being a user of the Rocky Linux GitLab allows you (the user)
28+
to create repositories, open issues, and collaborate on Special Interest Groups,
29+
and fixing all types of issues within the ecosystem, such as assets or failed
30+
patches.
31+
32+
This agreement does not cover, nor affect the ability to contribute to any of
33+
the Rocky GitHub organizations.
34+
35+
General Guidelines
36+
==================
37+
38+
As a contributor, there are guidelines in which you (the user) and others must
39+
follow. Below are a list of general things to be aware of:
40+
41+
* Moderation is enforced - As is done in the Rocky Linux MatterMost chat, it is
42+
important to mind your language and word choice. Speak to others as you would
43+
want them to speak to you.
44+
45+
* A valid GPG key must be uploaded and used to sign your commits. Signed
46+
commits, as a general rule, are recommended. Expect that most projects will
47+
have unsigned commits disabled.
48+
49+
* Accounts that are not in use or have not logged in may be deactivated or
50+
disabled
51+
52+
* Do not treat any git service as a general purpose Rocky Linux bug tracker.
53+
All issues should be tracked at our current bug tracker at
54+
https://bugs.rockylinux.org. Issues pertaining to a project under RESF may
55+
have other guidelines.
56+
57+
Expectations
58+
============
59+
60+
As a contributor, there are expectations for you (the user) and others who work
61+
in and interact with the git service. Below are a list of expectations we have
62+
of you:
63+
64+
* Do not create personal repositories - If the repository is not for the RESF,
65+
Rocky Linux, a SIG, a "people" page / area of work, or planned Rocky
66+
contributions, it should not be created.
67+
68+
* You will retain ownership of your contributions - Anything contributed by you
69+
(the user) will not be taken away from you or your name removed from said
70+
contributions, as outlined in the Rocky Open Source Contributor Agreement.
71+
72+
* Git is not a Rocky Linux bug tracker - All issues related to Rocky Linux
73+
should be tracked at our current bug tracker. Depending on the SIG, issues
74+
with the software or otherwise can be tracked either with their repositories
75+
or the bug tracker. This does not stop you (the user) from opening issues or
76+
PR's to improve or fix other issues without opening a bug report in most
77+
circumstances.
78+
79+
* Users must have GPG keys assigned to their account and their commits signed
80+
for specific repositories as configured.
81+
82+
Repository/Project Management
83+
=============================
84+
85+
Git software generally has repositories that holds code. Almost, if not all git
86+
software also allows a user to not only contribute to other repositories, but
87+
also have their own repositories that are directly connected to their profile.
88+
In both Rocky Git instances, while we encourage contributions and work on the
89+
many projects within, a personal repository connected only to you is discouraged
90+
in most circumstances.
91+
92+
Below are some general ideas of what is allowed for repository management:
93+
94+
* Allowed: Forking repositories, creating pull requests where needed
95+
* Allowed: Creating repositories (if permitted) in groups you are part of
96+
* Allowed: Creating repositories in your namespace for "people" material (such
97+
as wiki, pages, and other material)
98+
* Allowed: Creating repositories in your namespace that may potentially move to
99+
or become a or part of a project within the Rocky ecosystem
100+
101+
* Discouraged: Creating repositories under your namespace for your own use or
102+
consumption.
103+
104+
If the repository is planned to be moved under a team, SIG or another manner,
105+
this is a valid case for having repositories under your namespace. The user
106+
should request the move when ready by one of the following:
107+
108+
* Submit an issue in a meta repository if applicable
109+
* Open a ticket in the bug tracker if a meta repository does not exist or one
110+
is not appointed
111+
* Request directly in a public mattermost channel or another applicable medium
112+
such as email.
113+
114+
Repositories that are found to be personal in nature and do not reflect a
115+
given project, SIG, use for a "people" site or set of material, or repository
116+
(such as a fork) within the Rocky ecosystem may be archived or deleted.
117+
118+
Account Lifecycle
119+
=================
120+
121+
As a general rule of access, the RESF Git Service requires the signing of this
122+
agreement to gain access. For the Rocky Linux GitLab, this is not the case as
123+
the user also needs to be part of the "gitusers" group.
124+
125+
While there are other groups that facilitate more finer grained access into
126+
the various projects and groups, all users (contributors) will need to have
127+
signed this agreement and in the case of GitLab, be part of "gitusers" to login.
128+
129+
Direct sign-ups or local git accounts are not permitted and no exceptions will
130+
be granted.
131+
132+
Obtaining Access to the RESF Gitea Instance
133+
-------------------------------------------
134+
135+
A user obtains access to the RESF Gitea instance as long as the following
136+
conditions have been met:
137+
138+
* The user accepts the relevant contributor agreements in Account Services
139+
140+
* The user accepts this agreement
141+
142+
Obtaining Access to the Rocky Linux GitLab
143+
------------------------------------------
144+
145+
A user obtains access to the Rocky Linux git as long as the following
146+
conditions have been met:
147+
148+
* The user accepts the relevant agreements in Account Services
149+
150+
* The user will be part of a Special Interest Group or other general
151+
development
152+
153+
* The user or sig sponsor requests access to the "gitusers" group by
154+
contacting a sponsor in MatterMost - These sponsors can be found in
155+
the gitusers group in Account Services or at our wiki:
156+
https://wiki.rockylinux.org/guidelines/git_guidelines/
157+
158+
* The user accepts this agreement
159+
160+
* Upon acceptance and review, user will be added to the "gitusers" group
161+
in Account Services and their account will then be enabled in the GitLab
162+
instance.
163+
164+
Requesting Removal of Access
165+
----------------------------
166+
167+
A user that has access to any Rocky git can, at any time, request their account
168+
to be removed. This can be done by logging into the Rocky Linux bug tracker at
169+
https://bugs.rockylinux.org, clicking "Report Issue", selecting the
170+
"Account Services" item, and then selecting "Account Removal Request."
171+
172+
Note that you can also request a full account closure. Please see the
173+
following link for more information.
174+
175+
https://wiki.rockylinux.org/team/infrastructure/idm_pdr/
176+
177+
Revocation of Access
178+
--------------------
179+
180+
A user's access to any Rocky Git can be revoked at any time. Access can be
181+
revoked for but not limited to any of the following reasons:
182+
183+
* Repeated breach of guidelines and expectations as outlined in this agreement
184+
185+
* Breach of the Rocky Open Source Contributor Agreement
186+
187+
* Spam/Bot Accounts - An account that is found to spam or perform bot-like
188+
activities will be removed. This also applies to the bug
189+
tracking system.
190+
191+
* "Trophy" Accounts - An account that is found just to have access to any Rocky
192+
Git that has no plans for contributions and is using it
193+
as a way of a status symbol will have their access
194+
removed.
195+
196+
This also applies to accounts that are solely to make
197+
small/trivial changes that does not bring any benefits to
198+
the packages, software, and code produced for Rocky as a
199+
whole. Pull requests that are found to not improve the
200+
state of function of a package, software, or code, as
201+
a general rule, are denied.
202+
203+
Acceptance
204+
==========
205+
206+
To access the RESF Git Service, you must accept this agreement to signify
207+
you agree to the guidelines and expectations as laid out above.
208+
209+
To join the "gitusers" group, you must accept this agreement first before a
210+
sponsor can add or request your addition to "gitusers".

‎docs/guidelines/git_guidelines.md

+3
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ title: Git Guidelines
44

55
This document covers how the Rocky Enterprise Software Foundation (RESF) handles the use of Git in the ecosystem for the RESF and its projects such as Rocky Linux. It contains information about how various teams and the community interact and work with Git, as well as expectations and requirements.
66

7+
!!! note
8+
Usage of Git services hosted by the RESF are subject to the [Rocky Git Contributor Agreement](../contributing/git.md)
9+
710
## Contact Information
811
| | |
912
| - | - |

‎docs/special_interest_groups/current.md

+18-14
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,27 @@ This section goes over the current SIGs that may have sponsors and are active or
55

66
Below are some that may be established with sponsors/members or are in progress to being established.
77

8-
| SIG | Purpose |
9-
|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
10-
| [Cloud](https://sig-cloud.rocky.page/) | Cloud images and infrastructure - May work upstream with Stream for openstack and others as well. |
11-
| [AltArch](https://sig-altarch.rocky.page/) | Maintains alternative architectures or devices (such as the raspberry pi) that are not directly supported by Rocky Linux |
12-
| Desktop and Gaming | Supports and maintains the desktop and gaming experience for Rocky Linux |
13-
| Embedded | Embedded Systems |
14-
| [FastTrack](https://sig-fasttrack.rocky.page) | Provides fixes, customizations, upgrades, or improvements to existing Rocky Linux packages that the community would like to see |
15-
| [Kernel](https://sig-kernel.rocky.page/) | Maintains kernels (such as mainline or other long term support) and drivers |
16-
| Legacy | Supports and maintains legacy hardware support for Rocky Linux |
17-
| [HPC](https://sig-hpc.rocky.page/) | Maintains High Performance Computing support for Rocky Linux |
18-
| Hyperscale | Hyperscale Computing |
19-
| [Security](https://sig-security.rocky.page/) | Extra security features and security-hardened override packages (replacing those from the main distribution) for Rocky Linux and other EL distros |
8+
If you want to join one of these SIGs, check out their Wiki for information on how to get in touch and become a member.
9+
10+
## Active Special Interest Groups
11+
12+
| SIG | Purpose |
13+
|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
14+
| [AltArch](https://sig-altarch.rocky.page/) | Maintains alternative architectures or devices (such as the raspberry pi) that are not directly supported by Rocky Linux |
15+
| [Cloud](https://sig-cloud.rocky.page/) | Enables and supports running Rocky Linux inside of and as the base OS for public and private clouds |
16+
| [Desktop and Gaming](https://sig-desktop.rocky.page) | Supports and maintains the desktop and gaming experience for Rocky Linux |
17+
| [FastTrack](https://sig-fasttrack.rocky.page) | Provides fixes, customizations, upgrades, or improvements to existing Rocky Linux packages that the community would like to see |
18+
| [HPC and AI](https://sig-hpc.rocky.page/) | Maintains High Performance Computing support for Rocky Linux and the workloads which run atop Performance Intensive Computing clusters (e.g., AI/big data)|
19+
| [Kernel](https://sig-kernel.rocky.page/) | Maintains kernels (such as mainline or other long term support) and drivers |
20+
| [Security](https://sig-security.rocky.page/) | Extra security features and security-hardened override packages (replacing those from the main distribution) for Rocky Linux and other EL distros |
2021

2122
Below are those that have community interest, but no direct sponsors yet.
2223

2324
| SIG | Purpose |
2425
|---------------------------------------------|--------------------------------------------------------------------------------------------------|
25-
| [Database](https://sig-database.rocky.page) | Databases of all shapes, sizes, and use cases |
26-
| [AI](https://sig-ai.rocky.page/) | Rocky Linux Ecosystem for AI, ML, Data Science & BigData. |
26+
| Embedded | Embedded Systems |
27+
| Hyperscale | Hyperscale Computing |
2728
| Leapp | Focuses on the leapp framework to facilitate upgrades between major versions of Rocky |
29+
| Legacy | Supports and maintains legacy hardware support for Rocky Linux |
30+
| [Database](https://sig-database.rocky.page) | Databases of all shapes, sizes, and use cases |
31+
| [Storage](https://sig-storage.rocky.page) | Storage applications running on Rocky Linux |

0 commit comments

Comments
 (0)
Please sign in to comment.