Skip to content

Commit eac74a9

Browse files
xdelaruellexdelaruelle
committed
doc: add Modules Technical Charter
1 parent 32b981e commit eac74a9

File tree

4 files changed

+247
-0
lines changed

4 files changed

+247
-0
lines changed

‎.hunspell.en.dic‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1207,3 +1207,7 @@ envmodules
12071207
lightsteelblue
12081208
HowTos
12091209
xdelaruelle
1210+
stichting
1211+
Kunstlaan
1212+
LF
1213+
TSC

‎NEWS.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ Modules 5.6.0 (not yet released)
2525
development how-to guides.
2626
* Doc: add :ref:`acknowledgments` page in the documentation.
2727
* Doc: describe :ref:`GOVERNANCE`.
28+
* Doc: add :ref:`CHARTER`.
2829

2930
.. _Security policy: https://github.com/envmodules/modules/blob/main/SECURITY.md
3031

‎doc/source/CHARTER.rst‎

Lines changed: 241 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,241 @@
1+
.. _CHARTER:
2+
3+
Modules Technical Charter
4+
=========================
5+
6+
**Technical Charter (the "Charter") for Modules.**
7+
8+
Draft version.
9+
10+
This Charter sets forth the responsibilities and procedures for technical
11+
contribution to, and oversight of, the Modules open source project, which has
12+
been established as a project of Linux Foundation Europe, a Belgian private
13+
stichting headquartered at Kunstlaan 56, Brussels ("LF Europe").(the
14+
"Project"). All contributors (including maintainers, and other technical
15+
positions) and other participants in the Project (collectively,
16+
"Collaborators") must comply with the terms of this Charter.
17+
18+
1. **Mission and Scope of the Project**
19+
20+
a. The mission of the Project is to enable dynamic shell environment
21+
management by users. Allowing a simplified access and use of software
22+
stacks and environment configurations.
23+
24+
b. The scope of the Project includes collaborative development under the
25+
Project License (as defined herein) supporting the mission, including
26+
documentation, testing, integration and the creation of other artifacts
27+
that aid the development, deployment, operation or adoption of the open
28+
source project.
29+
30+
2. **Technical Steering Committee**
31+
32+
a. The Technical Steering Committee (the "TSC") will be responsible for all
33+
technical oversight of the open source Project.
34+
35+
b. The TSC voting members are initially the Project's Maintainers. At the
36+
inception of the project, the Maintainers of the Project will be as set
37+
forth within the ":ref:`GOVERNANCE<GOVERNANCE>`" file within the
38+
Project's code repository. The TSC may choose an alternative approach
39+
for determining the voting members of the TSC, and any such alternative
40+
approach will be documented in the :ref:`GOVERNANCE<GOVERNANCE>` file.
41+
Any meetings of the Technical Steering Committee are intended to be open
42+
to the public, and can be conducted electronically, via teleconference,
43+
or in person.
44+
45+
c. TSC projects generally will involve Contributors and Maintainers. The
46+
TSC may adopt or modify roles so long as the roles are documented in the
47+
:ref:`GOVERNANCE<GOVERNANCE>` file. Unless otherwise documented:
48+
49+
i. Contributors include anyone in the technical community that
50+
contributes code, documentation, or other technical artifacts to
51+
the Project;
52+
53+
ii. Maintainers are Contributors who have earned the ability to modify
54+
("commit") source code, documentation or other technical artifacts
55+
in a project's repository; and
56+
57+
iii. Maintainers are appointed by the TSC. A Contributor may become a
58+
Maintainer by a majority approval of the TSC. A Maintainer may be
59+
removed by a majority approval of the TSC.
60+
61+
d. Participation in the Project through becoming a Contributor and
62+
Maintainer is open to anyone so long as they abide by the terms of this
63+
Charter.
64+
65+
e. The TSC may (1) establish work flow procedures for the submission,
66+
approval, and closure/archiving of projects, (2) set requirements for
67+
the promotion of Contributors to Maintainer status, as applicable, and
68+
(3) amend, adjust, refine and/or eliminate the roles of Contributors,
69+
and Maintainers, and create new roles, and publicly document any TSC
70+
roles, as it sees fit.
71+
72+
f. The TSC may elect a TSC Chair, who will preside over meetings of the TSC
73+
and will serve until their resignation or replacement by the TSC. The
74+
TSC Chair, or any other TSC member so designated by the TSC, will serve
75+
as the primary communication contact between the Project and High
76+
Performance Software Foundation, a directed fund of The Linux
77+
Foundation.
78+
79+
g. Responsibilities: The TSC will be responsible for all aspects of
80+
oversight relating to the Project, which may include:
81+
82+
i. coordinating the technical direction of the Project;
83+
84+
ii. approving project or system proposals (including, but not limited
85+
to, incubation, deprecation, and changes to a sub-project's scope);
86+
87+
iii. organizing sub-projects and removing sub-projects;
88+
89+
iv. creating sub-committees or working groups to focus on cross-project
90+
technical issues and requirements;
91+
92+
v. appointing representatives to work with other open source or open
93+
standards communities;
94+
95+
vi. establishing community norms, workflows, issuing releases, and
96+
security issue reporting policies;
97+
98+
vii. approving and implementing policies and processes for contributing
99+
(to be published in the :ref:`CONTRIBUTING<CONTRIBUTING>` file) and
100+
coordinating with LF Europe to resolve matters or concerns that may
101+
arise as set forth in Section 7 of this Charter;
102+
103+
viii. discussions, seeking consensus, and where necessary, voting on
104+
technical matters relating to the code base that affect multiple
105+
projects; and
106+
107+
ix. coordinating any marketing, events, or communications regarding the
108+
Project.
109+
110+
3. **TSC Voting**
111+
112+
a. While the Project aims to operate as a consensus-based community, if any
113+
TSC decision requires a vote to move the Project forward, the voting
114+
members of the TSC will vote on a one vote per voting member basis.
115+
116+
b. Quorum for TSC meetings requires at least fifty percent of all voting
117+
members of the TSC to be present. The TSC may continue to meet if quorum
118+
is not met but will be prevented from making any decisions at the
119+
meeting.
120+
121+
c. Except as provided in Section 7.c. and 8.a, decisions by vote at a
122+
meeting require a majority vote of those in attendance, provided quorum
123+
is met. Decisions made by electronic vote without a meeting require a
124+
majority vote of all voting members of the TSC.
125+
126+
d. In the event a vote cannot be resolved by the TSC, any voting member of
127+
the TSC may refer the matter to LF Europe for assistance in reaching a
128+
resolution.
129+
130+
4. **Compliance with Policies**
131+
132+
a. Contributors will comply with the policies of LF Europe as may be
133+
adopted and amended by LF Europe, including, without limitation the
134+
policies listed at https://linuxfoundation.eu/policies/.
135+
136+
b. The TSC may adopt a code of conduct ("CoC") for the Project, which is
137+
subject to approval by LF Europe. In the event that a Project-specific
138+
CoC has not been approved, the LF Europe Code of Conduct listed at
139+
https://linuxfoundation.eu/policies/ will apply for all Collaborators
140+
in the Project.
141+
142+
c. When amending or adopting any policy applicable to the Project, LF
143+
Europe will publish such policy, as to be amended or adopted, on its web
144+
site at least 30 days prior to such policy taking effect; provided,
145+
however, that in the case of any amendment of the Trademark Policy or
146+
Terms of Use of LF Europe, any such amendment is effective upon
147+
publication on LF Project's web site.
148+
149+
d. All Collaborators must allow open participation from any individual or
150+
organization meeting the requirements for contributing under this
151+
Charter and any policies adopted for all Collaborators by the TSC,
152+
regardless of competitive interests. Put another way, the Project
153+
community must not seek to exclude any participant based on any
154+
criteria, requirement, or reason other than those that are reasonable
155+
and applied on a non-discriminatory basis to all Collaborators in the
156+
Project community.
157+
158+
e. The Project will operate in a transparent, open, collaborative, and
159+
ethical manner at all times. The output of all Project discussions,
160+
proposals, timelines, decisions, and status should be made open and
161+
easily visible to all. Any potential violations of this requirement
162+
should be reported immediately to LF Europe.
163+
164+
5. **Community Assets**
165+
166+
a. LF Europe will hold title to all trade or service marks used by the
167+
Project ("Project Trademarks"), whether based on common law or
168+
registered rights. Project Trademarks will be transferred and assigned
169+
to LF Europe to hold on behalf of the Project. Any use of any Project
170+
Trademarks by Collaborators in the Project will be in accordance with
171+
the license from LF Europe and inure to the benefit of LF Europe.
172+
173+
b. The Project will, as permitted and in accordance with such license from
174+
LF Europe, develop and own all Project GitHub and social media accounts,
175+
and domain name registrations created by the Project community.
176+
177+
c. Under no circumstances will LF Europe be expected or required to
178+
undertake any action on behalf of the Project that is inconsistent with
179+
the tax-exempt status or purpose, as applicable, of LF Europe.
180+
181+
6. **General Rules and Operations.**
182+
183+
a. The Project will:
184+
185+
i. engage in the work of the Project in a professional manner consistent
186+
with maintaining a cohesive community, while also maintaining the
187+
goodwill and esteem of LF Europe and other partner organizations in
188+
the open source community; and
189+
190+
ii. respect the rights of all trademark owners, including any branding
191+
and trademark usage guidelines.
192+
193+
7. **Intellectual Property Policy**
194+
195+
a. Collaborators acknowledge that the copyright in all new contributions
196+
will be retained by the copyright holder as independent works of
197+
authorship and that no contributor or copyright holder will be required
198+
to assign copyrights to the Project.
199+
200+
b. Except as described in Section 7.c., all contributions to the Project
201+
are subject to the following:
202+
203+
i. All new inbound code contributions to the Project must be made using
204+
GPL-2.0-or-later (the "Project License").
205+
206+
ii. All new inbound code contributions must also be accompanied by a
207+
Developer Certificate of Origin (http://developercertificate.org)
208+
sign-off in the source code system that is submitted through a
209+
TSC-approved contribution process which will bind the authorized
210+
contributor and, if not self-employed, their employer to the
211+
applicable license;
212+
213+
iii. All outbound code will be made available under the Project License.
214+
215+
iv. Documentation will be received and made available by the Project
216+
under the Creative Commons Attribution 4.0 International License
217+
(available at http://creativecommons.org/licenses/by/4.0/).
218+
219+
v. The Project may seek to integrate and contribute back to other open
220+
source projects ("Upstream Projects"). In such cases, the Project
221+
will conform to all license requirements of the Upstream Projects,
222+
including dependencies, leveraged by the Project. Upstream Project
223+
code contributions not stored within the Project's main code
224+
repository will comply with the contribution process and license
225+
terms for the applicable Upstream Project.
226+
227+
c. The TSC may approve the use of an alternative license or licenses for
228+
inbound or outbound contributions on an exception basis. To request an
229+
exception, please describe the contribution, the alternative open source
230+
license(s), and the justification for using an alternative open source
231+
license for the Project. License exceptions must be approved by a
232+
two-thirds vote of the entire TSC.
233+
234+
d. Contributed files should contain license information, such as SPDX short
235+
form identifiers, indicating the open source license or licenses
236+
pertaining to the file.
237+
238+
8. **Amendments**
239+
240+
a. This charter may be amended by a two-thirds vote of the entire TSC and
241+
is subject to approval by LF Europe.

‎doc/source/index.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,7 @@ automatically configured to the correct architecture.
119119
CONTRIBUTING
120120
devel
121121
design
122+
CHARTER
122123
GOVERNANCE
123124
acknowledgments
124125

0 commit comments

Comments
 (0)