fairpm/tsc
1
0
Fork 0
mirror of https://ghproxy.net/https://github.com/fairpm/tsc.git synced 2025-09-06 01:50:22 +08:00
Code Issues Projects Packages Wiki Activity Actions

Initial export of the repository

Browse source 
Signed-off-by: Ryan McCue <me@ryanmccue.info>
This commit is contained in:
Ryan McCue 2025-06-05 11:57:22 +02:00
commit c36f4e42ee
17 changed files with 995 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.gitignore vendored Normal file
View file

@ -0,0 +1 @@
.vscode

3
EMERITUS.md Normal file
View file

@ -0,0 +1,3 @@
# Emeritus TSC members
- [TBD]

395
LICENSE Normal file
View file

@ -0,0 +1,395 @@
Attribution 4.0 International
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution 4.0 International Public License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution 4.0 International Public License ("Public License"). To the
extent this Public License may be interpreted as a contract, You are
granted the Licensed Rights in consideration of Your acceptance of
these terms and conditions, and the Licensor grants You such rights in
consideration of benefits the Licensor receives from making the
Licensed Material available under these terms and conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
d. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
e. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
f. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
g. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
h. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
i. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
j. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
k. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part; and
b. produce, reproduce, and Share Adapted Material.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
4. If You Share Adapted Material You produce, the Adapter's
License You apply must not prevent recipients of the Adapted
Material from complying with this Public License.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material; and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public licenses.
Notwithstanding, Creative Commons may elect to apply one of its public
licenses to material it publishes and in those instances will be
considered the “Licensor.” The text of the Creative Commons public
licenses is dedicated to the public domain under the CC0 Public Domain
Dedication. Except for the limited purpose of indicating that material
is shared under a Creative Commons public license or as otherwise
permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the public
licenses.
Creative Commons may be contacted at creativecommons.org.

55
README.md Normal file
View file

@ -0,0 +1,55 @@
# The FAIR Package Manager - Technical Steering Committee (TSC)
The FAIR Package Manager Technical Steering Committee is responsible for oversight of the various Technical Initiatives (TI) of all internal projects.
## Get Involved
Although the TSC is composed of a set of official members listed below, any community member is welcome to participate in the TSC discussions, provided they adhere to the [Code of Conduct](code-of-conduct.md).
Use [GitHub Issues](https://github.com/fairpm/tsc/issues) to request and discuss agenda items.
If you need support in any part of the process, please ping the TSC in Slack.
## Meetings
[TBD]
## TSC Members
| Name | Position | Email | Organization | Term |
| ---------------- | :--------: | ------------------------------ | ------------- | -----------------------------|
| Carrie Dils | Co-Chair | `fair@carriedils.com` | [TBD] | March 31 2025 - June 2025 |
| Mika Epstein | Co-Chair | `fair@ipstenu.org` | [TBD] | March 31 2025 - June 2025 |
| Ryan McCue | Co-Chair | `fair@rmccue.io` | [TBD] | March 31 2025 - June 2025 |
For a complete list, see [Membership](https://github.com/fairpm/tsc/tree/main/membership.md)
## Charter
The TSC is chartered as part of The FAIR Package Manager Charter in the Linux Foundation.
## Technical Initiatives
At this time, Technical Initiatives are limited to our Working Groups.
### Working Groups (WGs)
See [Working Groups](https://github.com/fairpm/tsc/tree/main/working-groups)
| Name | Repository | Type (due) | Status |
| ------------------------------ | ------------------------------------------- | ----------------- | ----------- |
| Community | [GitHub](https://github.com/fairpm/tsc/tree/main/working-groups/community) | Permanent | In Progress |
| FAIR | [TBD] | Permanent | In Progress |
| Tech Independence | [TBD] | Temp (due June 5) | In Progress |
### Projects
| Name | Repository | Tracking | Sponsoring Org | Status |
| ---------------------- | ----------------------------------------------------- | ------------------------------------------------------ | ----------------- | ----------- |
| FAIR Protocol | [GitHub](https://github.com/fairpm/fair-protocol/) | | FAIR | Planning |
| Tech Ind. Plugin | [GitHub](https://github.com/fairpm/plugin/) | [Github](https://github.com/orgs/fairpm/projects/1) | Tech Independence | In Progress |
## License
* https://creativecommons.org/licenses/by/4.0/

13
TI-Reports/README.md Normal file
View file

@ -0,0 +1,13 @@
[//]: # (SPDX-License-Identifier: CC-BY-4.0)
# Technical Initiatives Updates
Updates are:
- used by the TSC to determine the health of an Initiative, including whether it should change state
- provided to the Governing Board on a regular basis in the TSC Update
- used to highlight interesting updates to the Governing Board about the Initiatives
- used to share interesting information with member companies by both the staff and TSC members
- suggested as a point of reference for newcomers to determine if a Initiative would be worth joining based on information like the contributor diversity, as well as, the type of feature work that is ongoing within the Initiative
# Instructions for Filing
[TBD]

BIN
assets/formation.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 463 KiB

5
charter.md Normal file
View file

@ -0,0 +1,5 @@
# Technical Charter (the “Charter”) for FAIR Package Manager a Series of LF Projects, LLC
Adopted May 14, 2025
[Link to charter](https://lfx-cdn-prod.s3.us-east-1.amazonaws.com/project-artifacts/fair-package-manager/fair-package-manager_Charter.pdf?v=1749049715416)

212
code-of-conduct.md Normal file
View file

@ -0,0 +1,212 @@
# Code of Conduct
---
status: "proposed"
date: 2025-04-29
---
Effective: `{{DATE_TBD}}`
As part of LF Projects, LLC (“LF Projects”), The FAIR Package Manager takes on all activities and behaviors that are consistent with the LF Projects mission and purpose.
The Code of Conduct aims to support a community where all people should feel safe to participate, introduce new ideas and inspire others, regardless of regardless of age, background, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, geographic location, personal appearance, race, caste, color, religion, sexual identity and orientation, or other dimension of diversity.
## Introduction
The purposes of The FAIR Package Manager are to:
* support the collaborative development, availability and adoption of open source web publishing software, as well as related hardware and networking and other technologies and the collaborative development, with availability and adoption of open protocols and standards (individually and collectively, “Open Technology”);
* host various projects related to The FAIR Package Manager, in the pursuit of the development of Open Technology and other technical assets, materials and processes as sub projects (there may be any number of associated sub projects at any one point in time);
* provide enablement and support to sub projects to assist their development activities; and
* undertake such other lawful activity as permitted by law and as consistent with the mission, purpose and tax status of Joint Development Foundation, a Washington non-profit non-stock corporation and the sole member of LF Projects.
The FAIR Package Manager is a community where participants choose to work together, and in that process experience differences in language, location, nationality, and experience. In such a diverse environment, misunderstandings and disagreements happen, which in most cases can be resolved informally. In rare cases, however, behavior can intimidate, harass, or otherwise disrupt one or more people in the community, which The FAIR Package Manager will not tolerate.
A **Code of Conduct (“Code” or "CoC")** is useful to define accepted and acceptable behaviors and to promote high standards of professional practice. It also provides a benchmark for self-evaluation and acts as a vehicle for better identity of the organization.
LF Projects is a Delaware series limited liability company. Projects of LF Projects are formed as separate series of LF Projects (each, a “Series”). References to “Projects” within this Policy include the applicable Series for each Project. Specifically, The FAIR Package Manager.
The CoC applies to any participant of The FAIR Package Manager – including without limitation developers, participants in meetings, teleconferences, mailing lists, conferences or functions, and contributors. Note that the CoC complements rather than replaces legal rights and obligations pertaining to any particular situation.
In addition, with the approval of LF Projects and leadership of The FAIR Package Manager, any sub projects or Working Groups are free to adopt their own Code of Conduct in place of or in addition to the Code.
## Statement of Intent
The FAIR Package Manager is committed to maintaining a positive, professional work environment. This commitment calls for community spaces (aka workplaces) where participants at all levels behave according to the rules of the following Code. A foundational concept of the CoC is that we all share responsibility for our work environment.
## Code
* Make participation in The FAIR Package Manager community a harassment-free experience for everyone.
* Act and interact with people in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
* Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.
* Never harass or bully anyone verbally, physically or sexually.
* Never discriminate on the basis of personal characteristics or group membership.
* Communicate constructively and avoid demeaning or insulting behavior or language.
* Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.
* Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.
* Respect the privacy of others and the confidentiality of data you access.
* With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.
* Promote the rules of the CoC and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed.
* Stay on topic: Make sure that you are posting to the correct channel and avoid off-topic discussions. Remember when you update an issue or respond to an email you are potentially sending to a large number of people.
* Step down considerately: participants in every project come and go, and The FAIR Package Manager is no different. When you leave or disengage from the project, in whole or in part, we ask that you do so in a way that minimizes disruption to the project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you left off.
## Scope
The CoC applies within all community spaces (aka workspaces), and also applies when an individual is officially representing the community in public spaces.
Community spaces are a set of all available means of collaboration, including, but not limited to, messages to mailing lists, private correspondence, web pages, chat channels, phone and video teleconferences, and any kind of face-to-face meetings or discussions.
Those who contribute code, comment code or specs, participate in discussions, attend conferences, represent corporate participants, or are otherwise involved in community spaces are considered participants of The FAIR Package Manager. Participants who are group chairs, staff members, board members, organizers, or project maintainers are considered to be in leadership positions.
Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
## Glossary
### Demeaning behavior
is acting in a way that reduces another person’s dignity, sense of self-worth or respect within the community.
### Discrimination
is the prejudicial treatment of an individual based on criteria such as: physical appearance, race, ethnic origin, genetic differences, national or social origin, name, religion, gender, sexual orientation, family or health situation, pregnancy, disability, age, education, wealth, domicile, political view, morals, employment, or union activity.
### Insulting behavior
is treating another person with scorn or disrespect.
### Acknowledgement
is a record of the origin(s) and author(s) of a contribution.
### Harassment
is any conduct, verbal or physical, that has the intent or effect of interfering with an individual, or that creates an intimidating, hostile, or offensive environment.
### Leadership position
includes group Chairs, project maintainers, staff members, and Board members.
## Participant
includes the following persons:
* Developers
* Representatives of corporate participants
* Anyone from the Public partaking in the LF Projects work environment (e.g. contribute code, comment on our code or specs, email us, attend our conferences, functions, etc)
### Respect
is the genuine consideration you have for someone (if only because of their status as participant in LF Projects, like yourself), and that you show by treating them in a polite and kind way.
### Sexual harassment
includes visual displays of degrading sexual images, sexually suggestive conduct, offensive remarks of a sexual nature, requests for sexual favors, unwelcome physical contact, and sexual assault.
### Unwelcome behavior
Hard to define? Some questions to ask yourself are:
* how would I feel if I were in the position of the recipient?
* would my partner, parent, child, sibling or friend like to be treated this way?
* would I like an account of my behavior published in the organization’s newsletter?
* could my behavior offend or hurt other members of the work group?
* could someone misinterpret my behavior as intentionally harmful or harassing?
* would I treat my boss or a person I admire at work like that?
Summary: if you are unsure whether something might be welcome or unwelcome, don’t do it.
### Unwelcome sexual advance
includes requests for sexual favors, and other verbal or physical conduct of a sexual nature, where:
* submission to such conduct is made either explicitly or implicitly a term or condition of an individual’s employment,
* submission to or rejection of such conduct by an individual is used as a basis for employment decisions affecting the individual,
* such conduct has the purpose or effect of unreasonably interfering with an individual’s work performance or creating an intimidating hostile or offensive working environment.
### Workspace Bullying
is a tendency of individuals or groups to use persistent aggressive or unreasonable behavior (e.g. verbal or written abuse, offensive conduct or any interference which undermines or impedes work) against a co-worker or any professional relations.
### Work Environment
is the set of all available means of collaboration, including, but not limited to messages to mailing lists, private correspondence, Web pages, chat channels, phone and video teleconferences, and any kind of face-to-face meetings or discussions.
## Incident Procedure
Every attempt will be made to address an incident in-house, following the procedures laid out in the CoC. The overall goal is to correct behavior and continue forward.
While an incident is being reviewed, contribution privileges to The FAIR Package Manager may be restricted or limited, depending on the nature of the incident. This is in order to protect the project as a whole but also those involved in the incident, so they cannot be blamed unjustly for actions that occur during this investigation.
All participants are expected to promote the expectations of the CoC and take action to bring the discussion back to a more civil level whenever inappropriate behaviors are observed.
Those in leadership positions are responsible for clarifying and enforcing our standards of acceptable behavior and taking appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. They also have the right and responsibility to remove, edit, or reject any contributions not aligned to the CoC. If such action is taken, they also have the responsibility to communicate reasons for their decisions when appropriate.
### Reporting Incidents
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at
[CONTACT METHOD]
All incidents will be reported via email to the Manager of LF Projects, Mike Dolan (`manager@lfprojects.org`). They will include any available relevant information, including links to any publicly accessible material relating to the matter. Every effort will be taken to ensure a safe and collegial environment in which to collaborate on matters relating to the Project.
In order to protect the community, the Project reserves the right to take appropriate action, potentially including the removal of an individual from any and all participation in the project. The Project will work towards an equitable resolution in the event of a misunderstanding.
### Appealing
To appeal reports of incidents, send email to the Manager of LF Projects, Mike Dolan (`manager@lfprojects.org`) with all relevant information.
### Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of the Code of Conduct:
#### 1. Correction
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested but cannot be required.
Violating these terms will lead to a Warning.
#### 2. Warning
**Community Impact**: A violation through a single incident or series of actions.
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media.
Violating these terms may lead to a temporary or permanent ban.
#### 3. Temporary Ban
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
#### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within the community.
### Behavioral Examples
The FAIR Package Manager is committed to maintaining a positive, community space. This commitment calls for community spaces where participants at all levels behave according to the expectations of the Code of Conduct. A foundational concept of the CoC is that all members share responsibility for the community and everyone's safety.
The following examples are not meant to be a comprehensive list. Instead, they capture the shared understanding of how to work together. They should be followed in both spirit and practice.
Examples of behavior that contributes to a _positive_ environment for the community include:
* demonstrating empathy and kindness toward other people;
* being respectful of differing opinions, viewpoints, and experiences;
* giving and gracefully accepting constructive feedback;
* accepting responsibility and apologizing to those affected by one's mistakes, and learning from the experience;
* focusing on what is best not just for individuals, but for the overall community;
Examples of _unacceptable_ behavior include:
* the use of sexualized language or imagery, and sexual attention or advances of any kind;
* trolling, insulting or derogatory comments, and personal or political attacks;
* public or private harassment;
* publishing others' private information, such as a physical or email address, or even their legal name, without their explicit permission;
* other actions which could reasonably be considered inappropriate in a professional setting;
## Credits
The CoC is based on the W3C’s Code of Ethics and Professional Conduct with some additions from the Cloud Foundry’s Code of Conduct and the Hyperledger Project Code of Conduct.
Aspects of the CoC are adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. For answers to common questions about the Code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
* [homepage]: https://www.contributor-covenant.org
* [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
* [Mozilla CoC]: https://github.com/mozilla/diversity
* [FAQ]: https://www.contributor-covenant.org/faq
* [translations]: https://www.contributor-covenant.org/translations

1
contributing.md Normal file
View file

@ -0,0 +1 @@
# Contributing

22
elections/README.md Normal file
View file

@ -0,0 +1,22 @@
# Election Procedures
This document outlines the election process.
## Voter Eligibility (Electorate) and Self-Nomination Process
[TBD]
## Self-Nomination Process
[TBD]
## Election Process
[TBD]
## Appointment Process
[TBD]
## Chair Elections
[TBD]
## Standard Nomination, Election, and Appointment Timeline
[TBD]

79
faq.md Normal file
View file

@ -0,0 +1,79 @@
# TSC FAQ
---
status: "in progress"
date: 2025-04-23
---
## Why is this a "technical" steering committee?
At its heart, this is a project to create technical products. Everything that goes into making the products, including documentation and events, are a part of this technical project. It may sound scary, and you may think that you're going to be left out because you don't write code, but that couldn't be further from the truth. All contributors are contributors to a technical project, making you a technical contributor!
## What does the steering committee do?
Our purpose is to make sure projects align with business objectives, monitor progress, approve any changes related to scope or budgets, conflict resolution, project strategy, and the overall task of getting the team to produce deliverables eventually. We also act as a central resource that facilitates communication and decision making between different groups, as well as mediation.
If that sounded like a mix between a technical lead and a project manager, then you nailed it on the head.
Our responsibilities include:
* developing plans, goals, objectives, policies;
* identifying and addressing risks;
* providing strategic oversight and guidance;
making key decisions (decisions regarding changes to the scope, budget or timeline);
* assessing progress;
* ensuring resources are managed properly (and that the project or initiative stays within the designated budget).
## What do ‘technical’ contributions mean?
Since the project in and of itself is a technical one with an output of a code product, anyone who contributes in any way is a technical contributor!
* Did you help someone in the forums? You’re a contributor!
* Did you write documentation? You’re a contributor!
* Did you file an issue? You’re a contributor!
* Did you manage a multi day event with speakers and swag? You’re a contributor!
* Did you manage publicity related documents and announcements? You guessed it, you’re a contributor!
## I don’t write code. Does this mean I could still be a contributor?
That’s exactly what it means. Don't get too hung up on the term 'technical.' It's really just that we're a project for a technical purpose, so things are 'technical.' It's not as scary as it sounds.
## What about being an “Organizer”?
Organizers are contributors who have become trusted enough to approve changes to the project.
For code sub-projects, this is synonymous with being “a committer” (or in Git terms, having the ability to merge). If it’s helpful, every time you read “Organizer” you can think “committer”, but we also include non-code contributions.
For non-code sub-projects, these are people who can sign off on the work done by others - this could be a person approving documentation changes, moderating forums, or organizing an event.
Contributions to both code projects and non-code sub-projects are valuable, and organizers are recognized for their contributions across the project. Members of the TSC can come from any team.
## What’s a Working Group?
A working group is an organization of contributors who are aligned and tasked with a specific sub project. Some examples of working groups are…
* The Community Working Group - tasked with managing and maintaining our Code of Conduct, FAQ, and more.
* The Independence Working Group - tasked with making our plugin
* The FAIR Working Group - tasked with reinventing the ecosystem
## What are the Co-Chairs?
They’re members of the collective community who have been elected to manage the Technical Steering Committee. They are responsible for ensuring the project meets deadlines, provides the necessary services, and appointing Organizers as needed amongst the working groups.
## Can anyone be a Co-Chair?
As long as they’re in compliance with our [Code of Conduct (CoC)](/code-of-conduct.md), they can be nominated and elected at the next cycle. They do not have to be incredibly technically savvy, but having a solid grounding in the technical aspects of the project will certainly be considered by the voting public.
## I was nominated but I don’t want to be an Organizer or Co-Chair. What should I do?
You can say no.
We promise, it’s that easy.
## Does the Code of Conduct apply to all groups?
Yes it does. No one is above the Code of Conduct.
## Why is the Code of Conduct written in legalese?
A great number of community projects use a very casual, easy to read, Code of Conduct. There's nothing wrong with that, however in order to be a part of the Linux Foundation, we were required to adopt a Code of Conduct that meets their requirements. While it does create a new hurdle for contributors, it also serves a long term benefit of demonstrating to the global open source world that we take this seriously and with the proper attention.

48
organizers.md Normal file
View file

@ -0,0 +1,48 @@
# Organizers
The TSC consists of contributors throughout The FAIR Package Manager community, who have been nominated or appointed as Organizers within their areas of contribution. The TSC includes all Organizers from across all projects, with three nominated co-chairs from the group.
## TSC Co-chairs
The TSC Co-chairs are:
| Name | GH Handle | Affiliation | Term |
|------|-----------|-------------| ---- |
| Carrie Dils | [@cdils](https://github.com/cdils) | Self | (elected 2025-03-31) |
| Mika Epstein | [@ipstenu](https://github.com/ipstenu) | Self | (elected 2025-03-31) |
| Ryan McCue | [@rmccue](https://github.com/rmccue) | Self | (elected 2025-03-31) |
## TSC Members
In addition to the co-chairs, the following Organizers are members of the TSC:
| Name | GH Handle | Affiliation |
|------|-----------|-------------|
| Andy Fragen | [@afragen](https://github.com/afragen)| Self |
| Ben Rubin | [@notarealemail](https://github.com/notarealemail) | Self |
| Brent Toderash | [@toderash](https://github.com/toderash) | Self |
| Chuck Adams | [@chuckadams](https://github.com/chuckadams) | AspirePress|
| circuitaxel | [@circuitaxel](https://github.com/circuitaxel) | Self |
| Colin Stewart | [@costdev](https://github.com/costdev) | Self |
| Courtney Robertson | [@courtneyr-dev](https://github.com/courtneyr-dev) | Self |
| cutterfishj | [@cutterfishj](https://github.com/cutterfishj) | Self |
| Cristi Rusu | [@cristirusu](https://github.com/cristirusu) | Crowd Favorite |
| Drew Jaynes | [@drewapicture](https://github.com/drewapicture) | Self |
| Francesca Marano | [@francescamarano](https://github.com/francescamarano) | Self |
| Jason Cosper | [@boogah](https://github.com/boogah) | Self |
| Javier Casares | [@javiercasares](https://github.com/javiercasares) | Self |
| Joe Dolson | [@joedolson](https://github.com/joedolson) | Self |
| Joost de Valk | [@jdevalk](https://github.com/jdevalk) | Emilia Capital |
| Karim Marucchi | [@pirazo](https://github.com/pirazo)| Crowd Favorite |
| Kevin Cristiano | [@kcristiano](https://github.com/kcristiano) | Self |
| Andrew Norcross | [@norcross](https://github.com/norcross) | Self |
| Pascal Birchler | [@swissspidy](https://github.com/swissspidy) | Self |
| Pat Ramsey | [@ramseyp](https://github.com/ramseyp) | Self |
| Robby McCullough | [@RobbyMcCullough](https://github.com/RobbyMcCullough) | Beaver Builder |
| Sam Sidler | [@samuelsidler](https://github.com/samuelsidler) | Self |
| Sarah Savage | [@sarah-savage](https://github.com/sarah-savage) | AspirePress |
| Scott Kingsley Clark | [@sc0ttkclark](https://github.com/sc0ttkclark) | Self |
| Se Reed | [@sereedmedia](https://github.com/sereedmedia) | Self |
| Shadi Sharaf | [@shadyvb](https://github.com/shadyvb) | Self |
| Siobhan McKeown | [@smckeown](https://github.com/smckeown) | Self |
| Taco Verdonschot | [@tacoverdo](https://github.com/tacoverdo) | Emilia Capital |
| Timi Wahalahti | [@timiwahalahti](https://github.com/timiwahalahti) | Self |

14
process/README.md Normal file
View file

@ -0,0 +1,14 @@
## TSC Process Documentation
This folder contains the policies and procedures The FAIR Package Manager TSC uses to perform their duties as well as guidelines for the Initiatives of the Project.
## Onboarding
## Decision Process
## Initiative Processes & Lifecycle
## Roles & Responsibilities
## Election Process
- [Elections Folder](https://github.com/fairpm/tsc/tree/main/elections) - contains documentation and historic election results

56
working-groups/README.md Normal file
View file

@ -0,0 +1,56 @@
# The FAIR Package Manager - Working Groups
Working Groups (“WGs”) are autonomous projects created by the Technical Steering Committee (TSC).
Working Groups can be formed at any time but must be ratified by the TSC. Once formed the work defined in the Working Group charter is the responsibility of the WG rather than the TSC.
As the TSC Charter is intended as a temporary charter, any Working Groups formed under the charter are similarly temporary. When a permanent TSC Charter is created, any prior Working Groups must be ratified by the TSC under the terms of the new TSC Charter.
When the work defined in a Working Group's charter is complete, the charter will be dissolved (revoked) unless there is a reason to extend it to a permanent Working Group.
A Working Group's charter can be revoked either by consent of the Working Group's members or by a TSC vote. Once revoked, any future work that arises becomes the responsibility of the TSC.
## Starting A Working Group
A Working Group is established by the TSC, with a statement of purpose and a list of responsibilities. The list of responsibilities should be specific. Each Working Group is self-governed under the standard governance below.
## Governance Rules for Working Groups
The following is a temporary set of governance rules for each Working Group. It is the intention that under a future TSC Charter, working groups shall have the ability to self-govern.
Each Working Group should copy the [`sample-readme.md`](https://github.com/fairpm/tsc/tree/main/working-groups/sample-readme.md) file as a template and place it within their designated subfolder under `/working-groups/` in the this repository (e.g., `/working-groups/community/README.md`). This file serves as the project “front door” for the Working Group and should be customized with the relevant details in `{}`. If the Working Group operates from a separate repository, the file should instead be placed in that repository’s main README or equivalent homepage.
Working Groups have a high degree of flexibility in how they work, but the following should remain consistent across all groups:
* All TSC policies, including the Code of Conduct and Licensing policies must be included by reference;
* Workspaces for all Working Groups, such as Slack channels, forums, mailing lists or other spaces must be posted centrally for easy access;
* All Working Groups must share details on how someone can contribute to them;
A [sample meeting notes template](https://github.com/fairpm/tsc/tree/main/working-groups/sample-meeting-notes.md) is available.
## Active Working Groups
### Community
The Community Working Group (CWG) is a documentation and process-focused initiative to support contributor onboarding and clarify how to engage with the FAIR Package Manager project.
- [Community WG](./community/)
### Technical Independence
The Technical Independence Working Group is responsible for developing a solution to independence from the existing central WP server.
This includes a replacement central server, a plugin to connect existing WP sites to this server, and the creation of tools to package and maintain a distribution of WP including this plugin. These are as outlined in the previously-created Timeline and Goals document; specifically, Phase 1 (“Drop-In Mirror”) and Phase 2 (“Sever Connection”).
The plugin created by the Technical Independence WG is to be created in a modular way, so that the plugin and tooling can be used by The FAIR WG.
**The Technical Independence WG is time- and scope-limited to the development of this solution. Once the solution is created, long-term maintenance of the plugin and any server components will transition to The FAIR WG. The Technical Independence WG shall complete its work prior to June 5, aiming for May 5 for a usable MVP of its work.**
### FAIR
The FAIR Working Group is responsible for the development and operation of The FAIR Package Manager, including server infrastructure, protocol design, and a connector plugin.
This includes the design of the decentralized protocol, design and operation of the discovery aggregator, design and operation of repository node software, and design and operation of the analytics service. These are as outlined in the previously-created Timeline and Goals document; specifically, Phase 3 (“MVP”), Phase 4 (“Distributed FAIR”), and Phase 5 (“Full FAIR”).
It also includes the installable connector plugin, which is expected to exist as a module within the plugin created by the Independence WG. The Independence WG will create the plugin initially, however long-term maintenance will transition to The FAIR WG upon that WG’s completion.
**The FAIR WG is a permanent Working Group.**

41
working-groups/community/README.md Normal file
View file

@ -0,0 +1,41 @@
The Community Working Group (CWG) is a documentation and process-focused initiative to support contributor onboarding and clarify how to engage with FAIR Package Manager for WordPress project.
The CWG is hosted by The FAIR Package Manager for WordPress Technical Steering Committee (TSC).
We follow The FAIR Package Manager [Code of Conduct](../../code-of-conduct.md).
Organizer access to this group is granted to members of The FAIR Package Manager TSC and regular contributors to the project, as determined by The FAIR Package Manager TSC. To request access, please reach out to a TSC member.
This project is licensed under the GNU General Public License (GPL), v2 or later.
This group welcomes contributions from any member of our community. To get started contributing, please see the contribution guide on this repo.
This Working Group is intended to be evergreen. Its scope may evolve over time to meet the needs of the project and the direction set by the TSC.
## 📌 Current Tasks
### 🗓️ Active Projects (Time-Scoped)
#### Private .github Repository + README
Deadline: June 5, 2025
Set up a private .github repository profile for our organization that will serve as an internal “front door” to the project. This will include a “New Contributor experience” README providing high-level orientation and internal reference points for contributors.
#### Contributor Communications Guide
Deadline: June 5, 2025
Create a document explaining how to participate in GitHub Discussions, including expectations for engagement, where to ask questions, and how to propose ideas. This may be included in the [contributing.md](../../contributing.md) file or provided as a standalone guide (e.g., `contributor-guide.md`).
#### FAQ Document (Private)
Deadline: June 5, 2025
A private document (shared via Google Docs) outlining key talking points and anticipated questions related to the upcoming project announcement. This document is not intended for public release, though always be mindful that private documents sometimes get shared.
### 🔄 Evergreen Responsibilities
## ✅ Completed Tasks
#### Provide initial TSC Charter/Code of Conduct review and make recommendations
Deadline: May 5, 2025
Our current documentation and policies are primarily based on the templates provided by the Linux Foundation with few modifications. While we intend to stick to these, some aspects need review for applicability to our community, to ensure it reflects the values of our community, and to determine whether any aspects are missing.
#### Develop initial documents for TSC repository
Deadline: May 5, 2025
The Community WG is responsible for advising the TSC on the FAQ and other related documentation. It also provides recommendations for Working Group self-governance to replace the temporary structures outlined in this repository.

38
working-groups/sample-meeting-notes.md Normal file
View file

@ -0,0 +1,38 @@
# {Working Group Name} Meeting Notes
Date: {Insert date}
Time: {Insert start-end time}
Location: {Slack/Call/etc}
Conversation Link: {Link to Slack Meeting if it happened there
## Attendees
{Name}, {Name}, {Name}, {etc}
## Items Discussed
* {Discussion item 1}
* {Discussion item 2}
* {Discussion item 3}
## Decisions Made
* {Decision summary 1}
* {Decision summary 2}
* {Decision summary 3}
## Open questions and concerns
* {Open question 1}
* {Open question 2}
* {Open question 3}
## Action Items
* {Action}: Assigned to {Name}, Due by {Date}
* {Action}: Assigned to {Name}, Due by {Date}
* {Action}: Assigned to {Name}, Due by {Date}
## Next Meeting
* Date: {Insert next meeting date}
* Time: {Insert next meeting time}
* Location: {Insert next meeting location or virtual link}
## Additional Notes
{Any other relevant notes or remarks}

12
working-groups/sample-readme.md Normal file
View file

@ -0,0 +1,12 @@
{Name} Working Group is a {project,group,etc} to {purpose}.
{Name} is hosted by The FAIR Package Manger TSC.
This {project,group,etc} welcomes contributions from any member of our community. To get started contributing, please see the contribution guide on this repo, and the [contribution guide for The FAIR Package Manager](contrib link tbd).
We follow The FAIR Package Manager [Code of Conduct](https://github.com/fairpm/tsc/blob/main/code-of-conduct.md).
{Elevated,Commit} access to this {project,group,etc} is granted to members of The FAIR Package Manager TSC and regular contributors to the project, as determined by The FAIR Package Manager TSC. To request access, please reach out to a TSC member.
This project is licensed under the GNU General Public License (GPL), v2 or later.