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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ These are the main contributing guidelines for the development of this MOOC, and
3
3
1. Invited experts as part of a core development team, led by one or two managers for each module.
4
4
1. Open participation, where anyone can contribute using the standard processes on GitHub.
5
5
6
-
Feedback and contributions of any form are welcomed. Feel free also to [contact us](https://opensciencemooc.eu/contact-us/) to discuss anything further.
6
+
Feedback and contributions of any form are welcomed. Feel free also to [contact us](https://opensciencemooc.eu/contact/) to discuss anything further.
7
7
8
8
At the present, development is in very early stages, as this is an entirely crowd-sourced and volunteer-led project. We are focusing inititally on [Module 5](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source) to run as a pilot for testing and receiving feedback. After this, the protocol and content will be revised, and then applied accordingly to the development of the remaining modules.
9
9
@@ -13,14 +13,14 @@ If you want to contribute, add yourself to the [contributors list](https://docs.
13
13
14
14
If you have questions about the project, please [email us](info@opensciencemooc.eu) directly.
15
15
16
-
Stay tuned on what's happening on Twitter with [@OpenSci_MOOC](https://twitter.com/OpenSci_MOOC).
16
+
Stay tuned on what's happening on Twitter with [@OpenSci_MOOC](https://twitter.com/OpenScienceMOOC).
17
17
18
18
## Getting started
19
19
1.[Forming a team for collaborative design](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#forming-a-team-for-collaborative-design).
20
20
1.[The development process](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#the-development-process).
21
21
1. Familiarise yourself with the [script writing guide](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Writing_a_script.md), the [script template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Script_template.md) and the [video management protocol](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Video_management_protocol.md).
22
22
23
-
Each team will adhere to the [MOOC planning template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MOOC%20planning%20template.docx) to structure development in a systematic way.
23
+
Each team will adhere to the [MOOC planning template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MOOC_planning_template.md) to structure development in a systematic way.
<palign="center"><i>Melanie Imming, & Jon Tennant. (2018, June 8). Sticker Open Science: just science done right. Zenodo. <ahref="http://doi.org/10.5281/zenodo.128557">http://doi.org/10.5281/zenodo.128557</a></i></p>
81
+
<palign="center"><i>Melanie Imming, & Jon Tennant. (2018, June 8). Sticker Open Science: just science done right. Zenodo. <ahref="https://zenodo.org/record/1285575#.XDebSM17lPY">https://zenodo.org/record/1285575#.XDebSM17lPY</a></i></p>
82
82
83
83
<br/>
84
84
@@ -654,7 +654,7 @@ There is so much potential material out there that it would take years of contin
654
654
655
655
-[Gareth O'Neill](https://twitter.com/gtoneill), Language Lubber
656
656
-[Bruce Caron](https://twitter.com/junanaguy), Culture Work Architect
Copy file name to clipboardExpand all lines: key_elements.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,8 +134,6 @@
134
134
135
135
*[Vienna Principles](http://viennaprinciples.org/): A vision for scholarly communication.
136
136
137
-
*[Summer School Open Science course](https://www.utrechtsummerschool.nl/courses/science/open-science-and-scholarship-changing-your-research-workflow), Utrecht University.
138
-
139
137
*[A short lecture on Open Licensing](https://figshare.com/articles/A_short_lecture_on_Open_Licensing/4516892/1) (Lorena, 2017; presenter notes also on [SpeakerDeck](https://speakerdeck.com/labarba/a-short-lecture-on-open-licensing). [Bonus interview](http://rtalbert.org/blog/2015/interview-lorena-barba)).
140
138
141
139
*[The Panton Principles of Open Science](https://en.wikipedia.org/wiki/Panton_Principles).
@@ -27,14 +27,14 @@ This is a collaborative, team-based effort. Each module has its own repo on GitH
27
27
2. Expectations of what each will contribute and receive from taking part.
28
28
3. An explanation of time scales and commitments.
29
29
4. An exploration of the MOOC module, the design and development protocol, the knowledge that will be included, and what the challenges to be addressed are.
30
-
5. The core learning outcomes and mission objectives for the module. These are all defined in the [Proposed Modules](https://opensciencemooc.eu/proposed-modules/) section of the companion website for the MOOC.
30
+
5. The core learning outcomes and mission objectives for the module. These are all defined in the [Proposed Modules](https://opensciencemooc.eu/modules/) section of the companion website for the MOOC.
31
31
3. Setting a timeline and action plan for development.
32
32
4. Acquiring team information. Each team member will be required to provide:
33
33
1. A profile picture.
34
34
2. A short bio.
35
35
3. Twitter handle (where appropriate).
36
36
4. Personal website (where appropriate).
37
-
5. Publicising the team to the MOOC companion website, [here](https://opensciencemooc.eu/about-us/production-team/).
37
+
5. Publicising the team to the MOOC companion website, [here](https://opensciencemooc.eu/people/#production).
0 commit comments