You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ESMValTool](https://www.esmvaltool.org/) tutorial is an open-source project and we greatly value contributions of all kinds: fixes to this tutorial, bug reports, reviews of pull requests, infrastructure improvements, community help, and outreach. We value the time you invest in contributing and strive to make the process as easy as possible. If you have suggestions for improving the process of contributing, please open an [issue][issues] by choosing the ``new feature`` template.
3
+
[ESMValTool](https://www.esmvaltool.org/) tutorial is an open-source project and we greatly value contributions of all kinds: fixes to this tutorial, bug reports, reviews of pull requests, infrastructure improvements, community help, and outreach. We value the time you invest in contributing and strive to make the process as easy as possible. If you have suggestions for improving the process of contributing, please open an [issue][issues] by choosing the ``New feature`` template in the ``issues`` tab of this repository.
4
4
5
5
## Acknowledgement
6
6
7
+
The [eScience academy][ea-site] initiated this tutorial.
7
8
The format of this tutorial is based on the [Software Carpentry][swc-site], which is an open-source project.
8
-
TODO escience academy
9
9
10
10
## Agreement
11
11
@@ -17,27 +17,16 @@ Everyone involved in this [tutorial](site) agrees to abide by our [code of condu
17
17
18
18
There are many ways to contribute:
19
19
20
-
If you wish to change this tutorial,
21
-
please work in <https://github.com/esmvalgroup/tutorial>,
22
-
which can be viewed at <https://esmvalgroup.github.io/tutorial>.
23
-
There are many ways to contribute,
24
-
from writing new exercises and improving existing ones
25
-
to updating or filling in the documentation
26
-
and submitting [bug reports][issues]
27
-
about things that don't work, aren't clear, or are missing.
28
-
If you are looking for ideas, please see the 'Issues' tab for
29
-
a list of issues associated with this repository,
30
-
31
-
32
-
33
20
* If you do not have a [GitHub][github] account,
34
21
you can [send us comments by email][email].
35
22
However,
36
23
we will be able to respond more quickly if you use one of the other methods described below.
37
24
38
25
* If you have a [GitHub][github] account,
39
26
or are willing to [create one][github-join],
40
-
you can report problems or suggest improvements by [creating an issue][issues].
27
+
please work in this [repository][site],
28
+
which can be viewed at <https://esmvalgroup.github.io/tutorial>.
29
+
You can report problems or suggest improvements by [creating an issue][issues].
41
30
This is the easiest way to tell us about your ideas,
42
31
and a good way to introduce yourself
43
32
and to meet some of our community members.
@@ -51,72 +40,54 @@ There are three templates to make an issue:
51
40
* If you would like to add what is already discussed in an issue,
52
41
you can submit a [pull request][PR].
53
42
To do so, you can make use of the [pull request checklist][PR].
54
-
The reviewers are community volunteers to provide feedback.
43
+
The reviewers are community volunteers who provide feedback.
55
44
The maintainers have final say over what gets merged into the tutorial.
56
45
57
46
## Lesson development guides
58
47
48
+
This tutorial is developed based on the [Carpentries Curriculum Development Handbook][swc-handbook].
49
+
59
50
### Lesson development
60
51
61
52
### Lesson organization
62
53
63
54
### Lesson formatting
64
55
65
-
### Preview your changes locally
66
-
67
-
68
-
69
-
## Using GitHub
70
-
71
-
If you choose to contribute via GitHub, you may want to look at
72
-
[How to Contribute to an Open Source Project on GitHub][how-contribute].
73
-
To manage changes, we follow [GitHub flow][github-flow].
74
-
75
-
76
-
1. Fork the originating repository to your GitHub profile.
77
-
2. Within your version of the forked repository, move to the `gh-pages` branch and
78
-
create a new branch for each significant change being made.
79
-
3. Navigate to the file(s) you wish to change within the new branches and make revisions as required.
80
-
4. Commit all changed files within the appropriate branches.
81
-
5. Create individual pull requests from each of your changed branches
82
-
to the `gh-pages` branch within the originating repository.
83
-
84
-
85
-
When starting work, please make sure your clone of the originating `gh-pages` branch is up-to-date
86
-
before creating your own revision-specific branch(es) from there.
87
-
Additionally, please only work from your newly-created branch(es) and *not*
88
-
your clone of the originating `gh-pages` branch.
89
-
Lastly, published copies of all the lessons are available in the `gh-pages` branch of the originating
90
-
repository for reference while revising.
91
-
92
56
## Previewing your changes locally
93
57
94
58
Extensive instructions for building and viewing the pages locally can be found [here](https://carpentries.github.io/lesson-example/setup.html). To get started quickly, run
59
+
95
60
```bash
96
61
# apt (Ubuntu/Devian)
97
62
sudo apt install ruby-dev ruby-bundler
98
63
```
64
+
99
65
or
66
+
100
67
```bash
101
68
# dnf (Fedora/Redhat)
102
69
sudo dnf install rubygem-bundler ruby-devel
103
70
```
104
71
105
72
Alternatively, there's an environment file available which can be installed in conda with:
0 commit comments