Skip to content

Commit c325e11

Browse files
authored
Update CONTRIBUTING.md
- added spam policy - updated getting involved & feedback links
1 parent d3aea00 commit c325e11

File tree

1 file changed

+24
-22
lines changed

1 file changed

+24
-22
lines changed

CONTRIBUTING.md

+24-22
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,16 @@
11
# How to Contribute to Chayn ⭐
22

3-
First off, thank you so much for taking the time to contribute!
3+
Thank you for taking the time to contribute!
44

5-
We ❤️ our contributors!
5+
We ❤️ our contributors and strive to give back more than we get. Have feedback on how we can improve? Questions, insight, or other concerns? We invite you to share in our [this anonymous form](https://forms.gle/v2whmf4XX3du4Y3t9).
66

7-
While Chayn is hybrid between paid staff and volunteers now, we cherish our volunteers for helping to create Chayn and keep us going! We hope to give back more than our contributors give. Please do not hesitate to give us feedback, so we can learn how to make this experience better for you. 😊 You can include feedback in your pull request, GitHub issue, or [this anonymous form](https://forms.gle/17GQpeHc4G1Mgdf3A).
8-
9-
**This guide below assumes you are an open-source contributor and NOT an official Chayn volunteer that has already completed the onboarding process. If you would like to become an official tech volunteer with Chayn, please [visit our Getting Involved Guide](https://www.notion.so/chayn/Get-involved-423c067536f3426a88005de68f0cab19?pvs=4). As an official Chayn volunteer, you will receive professional onboarding onto our platforms and more opportunities to volunteer outside of GitHub contributions!**
10-
11-
Next, let's get started... 🎉
7+
Do you want to make a greater impact with Chayn and receive special access to our organization and volunteer opportunities? Please visit our [visit our Getting Involved Guide](https://www.chayn.co/get-involved) to get started! Don't forget to star this repository ⭐ so we can find more contributors like you!
128

139
# Table of Contents
14-
- [New Contributor Guide:](#new-contributor-guide)
15-
- [Prerequisites](#prerequisites)
16-
- [Where Can I Get Help?](#where-can-i-get-help)
17-
- [What kind of contributions does Chayn want?](#what-kind-of-contributions-does-chayn-want)
10+
- [Prerequisites](#prerequisites)
11+
- [Where Can I Get Help?](#where-can-i-get-help)
12+
- [What kind of contributions does Chayn want?](#what-kind-of-contributions-does-chayn-want)
13+
- [Chayn's Spam Policy](#chayns-spam-contribution-policy-)
1814
- [The Contribution Process Guide:](#the-contribution-process-guide)
1915
1. [Read the README and Code of Conduct](#1-read-the-readme-and-code-of-conduct)
2016
2. [Claim an Issue](#2-claim-an-issue)
@@ -24,13 +20,9 @@ Next, let's get started... 🎉
2420
6. [Push Changes to GitHub](#6-push-changes-to-github)
2521
7. [Make a Pull Request to Chayn](#7--make-a-pull-request-to-chayn)
2622

27-
# New Contributor Guide
28-
29-
**If you are experienced in making open-source contributions, please feel free to skip ahead to the [Contribution Process Guide](#the-contribution-process-guide).**
3023

31-
## Prerequisites
24+
# Prerequisites
3225

33-
3426
If you are new to GitHub and git version control, here are some resources to help you get started:
3527

3628
- [Getting Started with First Time Git Setup](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup)
@@ -46,7 +38,7 @@ Here are prerequisites you should meet before contributing to Chayn's GitHub:
4638

4739
**It is not required that you have experience contributing to open-source projects on GitHub!** Chayn aims to be a safe space for contributors of all skill-levels to build their skills while making an impact in digital public goods. If this is your first contribution, we recommend saving the cheatsheet linked above for future reference, learning how to navigate the GitHub and git version control docs, and in general -- *learn as you go.* The Chayn team is here to help. You got this! 💪
4840

49-
## Where can I get help?
41+
# Where can I get help?
5042
Chayn maintainers and developers are here to help! We aim to give a safe space for contributors of all skill levels to build their skills while making an impact. 🤝
5143

5244
You can ask Chayn team members questions at any point during your contribution in the following places on GitHub:
@@ -57,18 +49,28 @@ You can ask Chayn team members questions at any point during your contribution i
5749

5850
Chayn team members will respond within 3 business days.
5951

60-
## What kind of contributions does Chayn want?
52+
# What kind of contributions does Chayn want?
6153

6254
Chayn is open to all kinds of contributions, such as:
6355

64-
- no-code (improved documentation and translations)
6556
- additional software tests
6657
- code of any kind (enhancements, new features, maintenance)
58+
- no-code (documenation, translations) *see spam policy below for accepted documentation changes.
59+
60+
# Chayn's Spam Contribution Policy 🚫
61+
62+
**Chayn will reject contributor pull requests if they are defined as spam or not associated with an issue.**
63+
All pull requests need to be associated with an issue. If you open a pull request without claiming an issue, you will be asked to create an issue for your pull request.
64+
65+
Documentation contributions will only be accepted under these circumstances:
66+
- adds additional context to the developer experience, such as environment set-up.
67+
- describes solutions for common error handling.
68+
- fixes a typo.
6769

68-
Just no spamming (such as unwanted, minor documentation and HTML/CSS changes) please! 🚫
70+
Unwanted documentation changes, such as summarizations, white space edits, or minor grammatical edits will be DENIED (unless there is evidence provided that these changes are for accessibility).
6971

70-
# The Contribution Process Guide:
71-
### The Contribution Process Outline:
72+
# The Contribution Process Guide
73+
### Directions for Contributing to Chayn:
7274
1. [Read the README and Code of Conduct](#1-read-the-readme-and-code-of-conduct)
7375
2. [Claim an Issue](#2-claim-an-issue)
7476
3. [Fork the Repo and Create a New Branch](#3-fork-the-repo-and-create-a-new-branch)

0 commit comments

Comments
 (0)