Skip to content

Commit 8c5ebaa

Browse files
authored
Merge pull request #17 from cpp-lln-lab/fcerpe-patch-1
imporved readability
2 parents 53de8e3 + 33061c7 commit 8c5ebaa

File tree

1 file changed

+20
-13
lines changed

1 file changed

+20
-13
lines changed

doc/contributing.md

+20-13
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,40 @@
11
# CONTRIBUTING
22

3-
Something is not clear or incorrenct or incomplete, something needs some updates over time or you found something new and cool that absolutely needs to be shared with the others... please contribute to this docs!!!
3+
This is a common effort, please contribute actively to this docs.
4+
If something is unclear, incorrect, or incomplete; if something needs to be updated or if you found a new and cool feature, consider adding it yourself.
5+
Here's a short guidelines on how to do so.
46

5-
## Submit an issue (no git/github skills required)
67

7-
Open an issue from [here](https://github.com/cpp-lln-lab/CPP_LabGuide/issues/new/choose) and try to be the most detailed possible.
8+
## Submit an issue (no git/github skills required)
89

9-
## Make the changes your self (minor git/github skills required)
10+
Open an issue from [here](https://github.com/cpp-lln-lab/CPP_LabGuide/issues/new/choose).
11+
Try to be the most detailed possible, so it's easier to intervene.
1012

11-
The actual text/scripts you find in this website are in this [repo](https://github.com/cpp-lln-lab/CPP_LabGuide) and in the `doc` folder [here](https://github.com/cpp-lln-lab/CPP_LabGuide/tree/main/doc)
1213

13-
Each article/section of the website is a specific markdown file with the same transparent name (more or less).
14+
## Make the changes yourself (minor git/github skills required)
1415

15-
### Edit from github
16+
The actual text/scripts you find in this website are in this [repoistory](https://github.com/cpp-lln-lab/CPP_LabGuide) and in the `/doc` folder [here](https://github.com/cpp-lln-lab/CPP_HPC/tree/main/doc).
17+
Each article/section of the website is a specific markdown (`.md`) file with (more or less) the same transparent name.
1618

17-
Just find the the markdown file you want to edit (eg the one for this section [contributing.md](https://github.com/cpp-lln-lab/CPP_LabGuide/blob/main/doc/contributing.md)) and click on `edit` (the pen icon) on the top right.
19+
If you're new to markdown, here's a quick [markdown cheatsheet](https://www.markdownguide.org/cheat-sheet/).
1820

19-
When done, click on `commit changes` (green botton on the top right) and select `Create a new branch for this commit and start a pull request` and then `Commit changes`.
2021

21-
On the new opened page you can edit the title of the pull request to provide a more meaningful one, select a reviewer (highly reccomended!!!) and then finally create the pull request (PR).
22+
### Edit from github
2223

23-
If you fill confident you can then merge it right away or ask someone else to review the PR and then approve it with or without corrections and merge it.
24+
1. Browse the repo to find the the markdown file you want to edit (e.g. the one for this section is [contributing.md](https://github.com/cpp-lln-lab/CPP_HPC/blob/main/doc/contributing.md)) and click on `edit` (the pen icon) on the top right
25+
2. Edit the file with your changes
26+
3. When done, click on `commit changes` (green botton on the top right), select `Create a new branch for this commit and start a Pull Request`, and then `Commit changes`
27+
4. On the new opened page, edit the Pull Request's title to provide more information (a few words, not an essay)
28+
5. Select a reviewer (e.g. [Filippo Cerpelloni](https://github.com/fcerpe) or [Marco Barilari](https://github.com/marcobarilari)). The review process helps preventing unnecessary / unwanted changes.
29+
6. Create the Pull Request (PR).
2430

25-
To change the website strucute (change name to section, add sections or reorder them), see the file `mkdocs.yml` section `Pages`.
31+
To change the website structure (add, reorder, rename sections), see the file `mkdocs.yml` and the section `Pages`.
2632

27-
That's it!
2833

2934
### Edit locally
3035

36+
If you're unfamiliar with the terms used here, check out the [git cheatsheet](https://training.github.com/downloads/github-git-cheat-sheet/)
37+
3138
1. fork this repository
3239
2. clone your forked repository
3340
3. install the dependencies via:

0 commit comments

Comments
 (0)