Skip to content

Add community charter #1

New issue

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

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

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Dec 17, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,12 @@ the primary clients are the two versions of the original Singularity software:
If you know of other implementations of registries or clients (the writer of this documentation
seems to recall some that she cannot remember) please [let us know](https://github.com/singularityhub/library-api/issues)
or [open a pull request](https://github.com/singularityhub/library-api) to add it.

## Community standard

Since this is a community standard, anyone in the community is invited to participate!
Suggestions for improvements are welcome through
[github issues](https://github.com/singularityhub/library-api/issues)
or [pull requests](https://github.com/singularityhub/library-api/pulls).
Changes to the specification will be reviewed and approved by people from the community
as described in the [community charter](community_charter.md).
45 changes: 45 additions & 0 deletions docs/community_charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Container Library API Standard Community Charter

The Container Library API Standard Community is made up of people who
are interested in the specification for the API.
Standards usually evolve, so this charter describes the process for
making that happen.
The community's intention is to evolve the standard in compatible ways
so older implementations can continue to work.

## Approving changes

In order to avoid letting the specification be controlled by a single
individual or company, changes to the specification and to this charter
are reviewed by a set of people designated as "Maintainers."
There are 3 to 5 Maintainers, each from separate organizations.
Maintainers are "members" in the
[github repository](https://github.com/singularityhub/library-api)
so they can use GitHub tools to mark pull requests as "Approved" or
"Changes requested."
Discussions will be public in issues or pull requests in that repository.
Maintainers will watch the GitHub repository for all activity.
Every effort will be made to achieve a consensus among the Maintainers,
but if consensus cannot be reached, changes can still be accepted if a
majority of the Maintainers agree.

## Adding Maintainers

If there are less than the maximum number of Maintainers and someone else volunteers,
as long as the new person is from a different organization,
a new approver can be added when a majority of the existing Approvers agree.

## Removing Maintainers

People can be removed from the current list of Maintainers if they request to be removed.

In addition, an Maintainer can be removed if for some reason the Maintainer stops
responding for a period of 2 months or more,
and the remaining Maintainers all agree.

## Current list of Maintainers

- [@DrDaveD](https://github.com/DrDaveD), Fermi National Accelerator Laboratory
- [@GodloveD](https://github.com/GodloveD), National Institute of Health
- [@tri-adam](https://github.com/tri-adam), Sylabs
- [@vsoch](https://github.com/vsoch), Lawrence Livermore National Laboratory