@@ -26,12 +26,13 @@ introduce yourself and to meet some of our community members.
26
26
27
27
2 . If you have a [ GitHub] [ github ] account, or are willing to [ create
28
28
one] [ github-join ] , but do not know how to use Git, you can report problems
29
- or suggest improvements by [ creating an issue] [ issues ] . This allows us to
30
- assign the item to someone and to respond to it in a threaded discussion.
29
+ or suggest improvements by [ creating an issue] [ repo- issues] . This allows us
30
+ to assign the item to someone and to respond to it in a threaded discussion.
31
31
32
32
3 . If you are comfortable with Git, and would like to add or change material,
33
33
you can submit a pull request (PR). Instructions for doing this are
34
- [ included below] ( #using-github ) .
34
+ [ included below] ( #using-github ) . For inspiration about changes that need to
35
+ be made, check out the [ list of open issues] [ issues ] across the Carpentries.
35
36
36
37
Note: if you want to build the website locally, please refer to [ The Workbench
37
38
documentation] [ template-doc ] .
@@ -49,8 +50,8 @@ There are many ways to contribute, from writing new exercises and improving
49
50
existing ones to updating or filling in the documentation and submitting [ bug
50
51
reports] [ issues ] about things that do not work, are not clear, or are missing.
51
52
If you are looking for ideas, please see [ the list of issues for this
52
- repository] [ repo ] , or the issues for [ Data Carpentry] [ dc-issues ] , [ Library
53
- Carpentry] [ lc-issues ] , and [ Software Carpentry] [ swc-issues ] projects.
53
+ repository] [ repo-issues ] , or the issues for [ Data Carpentry] [ dc-issues ] ,
54
+ [ Library Carpentry] [ lc-issues ] , and [ Software Carpentry] [ swc-issues ] projects.
54
55
55
56
Comments on issues and reviews of pull requests are just as welcome: we are
56
57
smarter together than we are on our own. ** Reviews from novices and newcomers
@@ -101,7 +102,8 @@ community listed at <https://carpentries.org/connect/> including via social
101
102
media, slack, newsletters, and email lists. You can also [ reach us by
102
103
email] [ contact ] .
103
104
104
- [ repo ] : https://example.com/FIXME
105
+ [ repo ] : https://github.com/LibraryCarpentry/lc-data-intro
106
+ [ repo-issues ] : https://github.com/LibraryCarpentry/lc-data-intro/issues
105
107
[ contact ] :
mailto:[email protected]
106
108
[ cp-site ] : https://carpentries.org/
107
109
[ dc-issues ] : https://github.com/issues?q=user%3Adatacarpentry
@@ -111,7 +113,7 @@ email][contact].
111
113
[ github ] : https://github.com
112
114
[ github-flow ] : https://guides.github.com/introduction/flow/
113
115
[ github-join ] : https://github.com/join
114
- [ how-contribute ] : https://egghead.io/series /how-to-contribute-to-an-open-source-project-on-github
116
+ [ how-contribute ] : https://egghead.io/courses /how-to-contribute-to-an-open-source-project-on-github
115
117
[ issues ] : https://carpentries.org/help-wanted-issues/
116
118
[ lc-issues ] : https://github.com/issues?q=user%3ALibraryCarpentry
117
119
[ swc-issues ] : https://github.com/issues?q=user%3Aswcarpentry
0 commit comments