-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #48 from adityac8/issue38
Adding rustreach campaign
- Loading branch information
Showing
1 changed file
with
35 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Rust Reach Campaign | ||
|
||
Place your blog post drafts here, if they are not part of an existing Content-o-Tron :robot: blogging campaign. | ||
|
||
## What is Rust Reach? | ||
|
||
Rust Reach is a project to get more people involved in Rust projects and also in Rust, the language. | ||
|
||
The program matches Rust team members from all parts of the project with individuals who are underrepresented in Rust's community and the tech industry for a partnership of three months. Each partnership agrees to a commitment of 3–5 hours per week working on a Rust Project. If you are interested to know more, you can visit the [website](http://reach.rust-lang.org/). | ||
|
||
## What this campaign is all about? | ||
|
||
Through this campaign, we encourage Rust project members writing about their experiences with being involved in Rust. The tone should be encouraging and welcoming. You can have a look at an example [here](https://yakshav.es/how-I-came-to-rust/). It doesn't have to be that long. | ||
|
||
### Need help? | ||
|
||
If you have any doubts, you can join our [Gitter](https://gitter.im/content-o-tron/Lobby) channel. We have an active community of members who are ready to help you with your doubts. If you want, you can raise an issue [here](https://github.com/rust-community/content-o-tron/issues). Make sure you follow our issue template. | ||
|
||
## Adding your blog here | ||
|
||
For adding your blog post here, follow these steps: | ||
|
||
1. **Fork this repo** | ||
|
||
Click on the <img src = "https://github.com/akshitac8/github-buttons/blob/master/2x/github_fork.png" width=50 /> button to make a copy of this repo in your own account. | ||
|
||
2. **Clone your repo** | ||
|
||
git clone https://github.com/<your-name>/content-o-tron.git | ||
3. **Add your blog post under this directory.** | ||
|
||
4. **Generate a pull request** | ||
|
||
Click on the <img src = "https://github.com/akshitac8/github-buttons/blob/master/2x/github_generate_pull.png" width=100 /> button to generate a Pull Request. |