Skip to content

Commit

Permalink
Restructuring and updating sections within the template Markdown docu…
Browse files Browse the repository at this point in the history
…ments.
  • Loading branch information
jrgriffiniii committed Mar 16, 2023
1 parent 2905104 commit 4c7f039
Show file tree
Hide file tree
Showing 4 changed files with 34 additions and 88 deletions.
37 changes: 4 additions & 33 deletions templates/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,36 +1,7 @@
The Samvera community is dedicated to providing a welcoming and
positive experience for all its members, whether they are at a formal
gathering, in a social setting, or taking part in activities online.
The Samvera community welcomes participation from people all over the
world and these members bring with them a wide variety of
professional, personal and social backgrounds; whatever these may be,
we treat colleagues with dignity and respect.
The Samvera community is dedicated to providing a welcoming and positive experience for all its members, whether they are at a formal gathering, in a social setting, or taking part in activities online. The Samvera community welcomes participation from people all over the world and these members bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect.

Community members communicate primarily in English, though for many of
them this is not their native language. We therefore strive to express
ourselves simply and clearly remembering that unnecessary use of
jargon and slang will be a barrier to understanding for many of our
colleagues. We are sensitive to the fact that the international
nature of the community means that we span many different social norms
around language and behaviour and we strive to conduct ourselves,
online and in person, in ways that are unlikely to cause offence.
Community members communicate primarily in English, though for many of them this is not their native language. We therefore strive to express ourselves simply and clearly remembering that unnecessary use of jargon and slang will be a barrier to understanding for many of our colleagues. We are sensitive to the fact that the international nature of the community means that we span many different social norms around language and behaviour and we strive to conduct ourselves, online and in person, in ways that are unlikely to cause offence.

Samvera conversations are often information-rich and intended to
generate discussion and debate. We discuss ideas from a standpoint of
mutual respect and reasoned argument.
Samvera conversations are often information-rich and intended to generate discussion and debate. We discuss ideas from a standpoint of mutual respect and reasoned argument.

Community members work together to promote a respectful and safe
community. In the event that someone’s conduct is causing offence or
distress, Samvera has a detailed
[Anti-Harassment Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
which can be applied to address the problem. The first step in dealing
with any serious misconduct is to contact a local meeting organizer,
the
[Samvera community helpers](https://wiki.duraspace.org/display/samvera/Samvera+Community+Helpers)
([email](mailto:helpers@samvera.org)), a community member you
trust, or the
[Samvera Steering Group](https://wiki.duraspace.org/display/samvera/Samvera+Steering+Group+membership)
immediately; at Samvera events, these people can be identified by
distinctive name badges. The
[Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
should be consulted for fuller details.
Community members work together to promote a respectful and safe community. In the event that someone’s conduct is causing offence or distress, Samvera has a detailed [Samvera Code of Conduct and Anti-Harassment Policy](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Samvera+Code+of+Conduct+and+Anti-Harassment+Policy) which can be applied to address the problem. The first step in dealing with any serious misconduct is to contact a local meeting organizer, the [Samvera Community Helpers](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211681/Samvera+Community+Helpers) ([email](helpers@samvera.org)), a community member you trust, or the [Samvera Board](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405210594/Samvera+Board+membership) immediately; at Samvera events, these people can be identified by distinctive name badges. The [Anti-Harassment Policy](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Samvera+Code+of+Conduct+and+Anti-Harassment+Policy) should be consulted for fuller details.
62 changes: 20 additions & 42 deletions templates/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,26 @@
# How to Contribute

We want your help to make the Samvera community great. There are a few guidelines
that we need contributors to follow so that we can have a chance of
keeping on top of things.
We want your help to make the Samvera community great. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

## Code of Conduct

The Samvera Community is dedicated to providing a welcoming and positive
experience for all its members, whether they are at a formal gathering, in
a social setting, or taking part in activities online. Please see our
[Code of Conduct](CODE_OF_CONDUCT.md) for more information.
The Samvera Community is dedicated to providing a welcoming and positive experience for all its members, whether they are at a formal gathering, in a social setting, or taking part in activities online. Please see our [Code of Conduct](./CODE_OF_CONDUCT.md) for more information.

## Samvera Community Intellectual Property Licensing and Ownership

All code contributors must have an Individual Contributor License Agreement
(iCLA) on file with the Samvera Steering Group. If the contributor works for
an institution, the institution must have a Corporate Contributor License
Agreement (cCLA) on file.

https://wiki.duraspace.org/display/samvera/Samvera+Community+Intellectual+Property+Licensing+and+Ownership
While there are some [select exceptions](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211658/Licensed+software+acceptance+procedure), nearly all source code bases produced and maintained by Samvera Community members are published under the [Apache 2.0 License restrictions](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211660/Code+Copyright+Statement). As such, we please insist that, when creating a new GitHub repository within [https://github.com/samvera-labs](samvera-labs), one please include a copy of the [Apache 2.0 license](./LICENSE) within the repository.

You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.

## Language

The language we use matters. Today, tomorrow, and for years to come
people will read the code we write. They will judge us for our
design, logic, and the words we use to describe the system.
The language we use matters. Today, tomorrow, and for years to come people will read the code we write. They will judge us for our design, logic, and the words we use to describe the system.

Our words should be accessible. Favor descriptive words that give
meaning while avoiding reinforcing systemic inequities. For example,
in the Samvera community, we should favor using allowed_list instead
of whitelist, denied_list instead of blacklist, or source/copy
instead of master/slave.
Our words should be accessible. Favor descriptive words that give meaning while avoiding reinforcing systemic inequities. For example, in the Samvera community, we should favor using allowed\_list instead of whitelist, denied\_list instead of blacklist, or source/copy instead of master/slave.

We're going to get it wrong, but this is a call to keep working to
make it right. View our code and the words we choose as a chance to
have a conversation. A chance to grow an understanding of the systems
we develop as well as the systems in which we live.
We're going to get it wrong, but this is a call to keep working to make it right. View our code and the words we choose as a chance to have a conversation. A chance to grow an understanding of the systems we develop as well as the systems in which we live.

See [“Blacklists” and “whitelists”: a salutary warning concerning the
prevalence of racist language in discussions of predatory
publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) for
further details.
See [“Blacklists” and “whitelists”: a salutary warning concerning the prevalence of racist language in discussions of predatory publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) for further details.

## Contribution Tasks

Expand All @@ -65,20 +43,20 @@ further details.

### Making Changes

- Fork the repository on GitHub
- Create a topic branch from where you want to base your work.
- This is usually the `main` branch.
- To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
- Then checkout the new branch with `git checkout fix/main/my_contribution`.
- Please avoid working directly on the `main` branch.
- Please do not create a branch called `master`. (See note below.)
- You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
- Make sure you have added sufficient tests and documentation for your changes.
- Test functionality with RSpec; Test features / UI with Capybara.
- Run _all_ the tests to assure nothing else was accidentally broken.
* Fork the repository on GitHub
* Create a topic branch from where you want to base your work.
* This is usually the `main` branch.
* To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
* Then checkout the new branch with `git checkout fix/main/my_contribution`.
* Please avoid working directly on the `main` branch.
* Please do not create a branch called `master`. (See note below.)
* You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
* Make sure you have added sufficient tests and documentation for your changes.
* Test functionality with RSpec; Test features / UI with Capybara.
* Run _all_ the tests to assure nothing else was accidentally broken.

NOTE: This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Samvera+Code+of+Conduct+and+Anti-Harassment+Policy) and [language recommendations](#language).

NOTE: This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct)
and [language recommendations](#language).
Please **_do not_** create a branch called `master` for this repository or as part of
your pull request; the branch will either need to be removed or renamed before it can
be considered for inclusion in the code base and history of this repository.
Expand Down
21 changes: 9 additions & 12 deletions templates/README.md
Original file line number Diff line number Diff line change
@@ -1,43 +1,40 @@
# {{library}}

Code: [![Version](https://badge.fury.io/rb/{{library}}.png)](http://badge.fury.io/rb/{{library}})
[![Build Status](https://travis-ci.org/samvera/{{library}}.png?branch=master)](https://travis-ci.org/samvera/{{library}})
[![Coverage Status](https://coveralls.io/repos/github/samvera/{{library}}/badge.svg?branch=master)](https://coveralls.io/github/samvera/{{library}}?branch=master)
Code: [![Samvera Core Component](https://img.shields.io/badge/samvera-core--component-brightgreen)](https://github.com/samvera/maintenance#samvera-core-components)
[![Build Status](https://circleci.com/gh/samvera/{{library}}.svg?style=svg)](https://circleci.com/gh/samvera/{{library}})
[![Version](https://badge.fury.io/rb/{{library}}.png)](http://badge.fury.io/rb/{{library}})

Docs: [![Contribution Guidelines](http://img.shields.io/badge/CONTRIBUTING-Guidelines-blue.svg)](./CONTRIBUTING.md)
[![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.svg)](./LICENSE)

Jump in: [![Slack Status](http://slack.samvera.org/badge.svg)](http://slack.samvera.org/)
Community Support: [![Samvera Community Slack](https://img.shields.io/badge/samvera-slack-blueviolet)](http://slack.samvera.org/)

# What is {{library}}?

Enter a description of the library here.

## Product Owner & Maintenance
## Product Owner and Maintenance

{{library}} is a Core Component of the Samvera community. The documentation for
what this means can be found
[here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).
{{library}} is a Core Component of the Samvera community. The documentation for what this means can be found [here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).

### Product Owner

[githubusername](https://github.com/githubusername)

# Help

The Samvera community is here to help. Please see our [support guide](./SUPPORT.md).
The Samvera community is here to help. Please see the [support guide](./SUPPORT.md).

# Getting Started

Give a description w/ examples of how to use the library.
Give a description with examples of how to use the library.

## Prerequisites

Include any system-level dependencies this library has.

# Acknowledgments

This software has been developed by and is brought to you by the Samvera community. Learn more at the
[Samvera website](http://samvera.org/).
This software has been developed by and is brought to you by the Samvera community. Learn more at the [Samvera website](http://samvera.org/).

![Samvera Logo](https://wiki.duraspace.org/download/thumbnails/87459292/samvera-fall-font2-200w.png?version=1&modificationDate=1498550535816&api=v2)
2 changes: 1 addition & 1 deletion templates/SUPPORT.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@ If you would like to report an issue, first search [the list of issues](https://

If you have questions or need help, please email [the Samvera community tech list](https://groups.google.com/forum/#!forum/samvera-tech) or stop by the #dev channel in [the Samvera community Slack team](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211682/Getting+Started+in+the+Samvera+Community#Join-the-Samvera-Slack-workspace).

You can learn more about the various Samvera communication channels on the [Getting Started in the Samvera Community](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211682/Getting+Started+in+the+Samvera+Community) wiki page.
You can learn more about the various Samvera communication channels on the [Getting Started in the Samvera Community](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211682/Getting+Started+in+the+Samvera+Community#Join-the-Samvera-Slack-workspace) wiki page.

0 comments on commit 4c7f039

Please sign in to comment.