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