md - reformatting

Author: nuest

nl/workshop1.md

@@ -79,8 +79,7 @@ code related to:
 
 - A preprint that is publicly available
 
-- Code and results files that have been or will be deposited in a
-repository, preferably GitHub or GitLab
+- Code and results files that have been or will be deposited in a repository, preferably GitHub or GitLab
 
 In each case, the code and data underlying the paper should be openly
 available, or you plan to make them available once the paper is

nl/workshop2.md

@@ -15,49 +15,49 @@ We began our morning with a round of introductions, and an intro to the project
 
 We took a break for an excellent warm lunch in the faculty canteen -- much needed in the gloomy weather -- and then delved straight into breakout groups for the afternoon. Four authors joined us with their submissions, which the breakout groups began to codecheck. Three were finished on the spot, and a fourth was begun and we agreed to complete it after the session. And voila! Completed codecheck certificates from the workshop are already available, [have a look](https://osf.io/m7tze/)!
 
-We wrapped up the day with an interesting reflection session. Along with the authors and codecheckers, we were also joined by Prof. Dr Alfred Stein, editor of the Journal of Spatial Statistics, and (virtually) Daniel Nuest, another founder of Codecheck. One of our goals in this project is to explore ways in which the codecheck workflow can be incorporated into journal submission processes, and a lively discussion followed on what codecheck can add to the review process, where in the review workflow codecheck could fit, and who would conduct them. As always, issues of reward and recognition were central to our discussions about codecheck. Have an idea about this? Join us at the next codecheck session in [Rotterdam](https://codecheckRotterdam.eventbrite.com)!
+We wrapped up the day with an interesting reflection session. Along with the authors and codecheckers, we were also joined by Prof. Dr Alfred Stein, editor of the Journal of Spatial Statistics, and (virtually) Daniel Nüst, another founder of Codecheck. One of our goals in this project is to explore ways in which the codecheck workflow can be incorporated into journal submission processes, and a lively discussion followed on what codecheck can add to the review process, where in the review workflow codecheck could fit, and who would conduct them. As always, issues of reward and recognition were central to our discussions about codecheck. Have an idea about this? Join us at the next codecheck session in [Rotterdam](https://codecheckRotterdam.eventbrite.com)!
 
 ---------------------------------------------------------------------------------------------------
 
 ## CALL FOR PAPERS/PREPRINTS/CODE: Are you a researcher in geosciences/environmental sciences interested in reproducible code and Open Science? We have the perfect opportunity for you!
 
-As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 26 September 2024** at the University of Twente.  A codecheck is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project (see more details [here](https://codecheck.org.uk/process/)).
+As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 26 September 2024** at the University of Twente.  A codecheck is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project (see more details [here](https://codecheck.org.uk/process/)).
 
-You can participate as a codechecker (i.e., a person reviewing code), or by submitting your own work to be checked (or both if you are up for it!). *Curious to know how it works? Read about our first [workshop in Delft](https://codecheck.org.uk/nl-workshop1/).*
+You can participate as a codechecker (i.e., a person reviewing code), or by submitting your own work to be checked (or both if you are up for it!). *Curious to know how it works? Read about our first [workshop in Delft](https://codecheck.org.uk/nl-workshop1/).*
 
 Anyone is welcome to participate at the workshop. Participation is free of cost and includes lunch. We have limited funding (on a first come, first served basis) for reimbursing train tickets for PhD (non-AiO) students. PhD candidates who participate in the workshop can reach out to us about getting credits for participation, provided their supervisors and institutions/departments also agree.
 
-## What do I get if I submit my paper or pre-print?  
+## What do I get if I submit my paper or pre-print?
 
-A codechecker will work with you during the session to check whether your code and data can be run by others to generate the same or similar results.  
+A codechecker will work with you during the session to check whether your code and data can be run by others to generate the same or similar results.
 
-The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible!  
+The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible!
 
-Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced.  This can be shared, for instance with potential journal editors, to enhance the visibility and reproducibility of your work.
+Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced.  This can be shared, for instance with potential journal editors, to enhance the visibility and reproducibility of your work.
 
-By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research!  
+By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research!
 
-## Sounds good! What should I do?  
+## Sounds good! What should I do?
 
-Are you interested in participating in this event, and help contribute to promoting code reproducibility? Send an email to <[email protected]> **by 9 September 2024** with a *brief description of your paper/project, and links to your code and data*. This could be code related to:  
+Are you interested in participating in this event, and help contribute to promoting code reproducibility? Send an email to <[email protected]> **by 9 September 2024** with a *brief description of your paper/project, and links to your code and data*. This could be code related to:
 
-- A paper that you have recently published  
+- A paper that you have recently published
 
-- A preprint that is publicly available  
+- A preprint that is publicly available
 
-- Code and results files that have been or will be deposited in a repository, preferably  GitHub or GitLab  
+- Code and results files that have been or will be deposited in a repository, preferably  GitHub or GitLab
 
-In each case, the code and data underlying the paper should be openly available, or you plan to make them available once the paper is published.
+In each case, the code and data underlying the paper should be openly available, or you plan to make them available once the paper is published.
 
-**Selected papers/projects will be notified in early September 2024. All authors are invited to register join the workshop.**  
+**Selected papers/projects will be notified in early September 2024. All authors are invited to register join the workshop.**
 
 ## What if I want to volunteer to be a codechecker instead?
 
-If you are interested in learning more about the codecheck process and becoming a codechecker, please register on our [eventbrite page](https://www.eventbrite.nl/e/codecheck-workshop-for-the-geosciences-and-environmental-sciences-tickets-945474348227?aff=oddtdtcreator) to volunteer to become a codechecker at the workshop on 26th September. The event will be held in person at the University of Twente.
+If you are interested in learning more about the codecheck process and becoming a codechecker, please register on our [eventbrite page](https://www.eventbrite.nl/e/codecheck-workshop-for-the-geosciences-and-environmental-sciences-tickets-945474348227?aff=oddtdtcreator) to volunteer to become a codechecker at the workshop on 26th September. The event will be held in person at the University of Twente.
 
 ### Why would I volunteer your time to code check other people's work?
 
-- Learn how others ensure reproducibility of their work  
+- Learn how others ensure reproducibility of their work  
 
 - Gaining hands-on experience in peer reviewing code
 
@@ -67,6 +67,6 @@ If you are interested in learning more about the codecheck process and becoming
 
 *Interested but still have questions? Ask us!*
 
-Write to us at <[email protected]>, we are happy to answer any questions!
+Write to us at <[email protected]>, we are happy to answer any questions!
 
 For questions related to the NWO project CHECK-NL, please contact Frank Ostermann (<[email protected]>)

nl/workshop3.md

@@ -13,11 +13,11 @@ redirect_from:
 <img src="https://github.com/user-attachments/assets/49b7fe00-55d0-4f04-b571-5134128d98fe" alt="Rotterdam workshop participants" width="60%" height = "60%">
 </p>
 
-Our third CHECK-NL workshop on the social and behavioural sciences at Erasmus University Rotterdam was an engaging, supportive community event, made even better by our gracious host at EUR, Eduard Klapwijk, who kept us well fed, watered and caffeinated through the day, in addition to being active in the sessions as well. 
+Our third CHECK-NL workshop on the social and behavioural sciences at Erasmus University Rotterdam was an engaging, supportive community event, made even better by our gracious host at EUR, Eduard Klapwijk, who kept us well fed, watered and caffeinated through the day, in addition to being active in the sessions as well.
 
-The day began with an introduction from Stephen Eglen (co-founder CODECHECK), taking us through the concepts and steps of codecheck, and leading us through a live demo of a codecheck he had begun the previous evening on the train from London, which he successfully completed. Shortly thereafter, the three authors who had submitted their work to be codechecked briefly introduced their projects, and participants divided themselves up into three breakout groups, with two groups working with R and one with Python. All three groups completed successful codechecks, and also made some headway writing the certificates of executable computations. Have a look at the [CODECHECK Register](https://codecheck.org.uk/register/venues/communities/codecheck_nl/) to see the newly published certificates from our workshop!  
+The day began with an introduction from Stephen Eglen (co-founder CODECHECK), taking us through the concepts and steps of codecheck, and leading us through a live demo of a codecheck he had begun the previous evening on the train from London, which he successfully completed. Shortly thereafter, the three authors who had submitted their work to be codechecked briefly introduced their projects, and participants divided themselves up into three breakout groups, with two groups working with R and one with Python. All three groups completed successful codechecks, and also made some headway writing the certificates of executable computations. Have a look at the [CODECHECK Register](https://codecheck.org.uk/register/venues/communities/codecheck_nl/) to see the newly published certificates from our workshop!
 
-The reflection session is always a lively and engaging way to wrap up to the workshop, and this one did not disappoint. The breakout groups recapped their experiences of codechecking, and authors reflected on how codechecking often helps them re-evaluate their own assumptions. Other reflections focussed on the challenges of performing codechecks with sensitive or confidential data, a situation that many in our audience were all too familiar with, being from the social and behavioural sciences. Incentivising and growing the codechecking community is always an interesting part of the reflection, and answers ranged from monetary compensation and making it a job, to fame and glory (if only!). 
+The reflection session is always a lively and engaging way to wrap up to the workshop, and this one did not disappoint. The breakout groups recapped their experiences of codechecking, and authors reflected on how codechecking often helps them re-evaluate their own assumptions. Other reflections focussed on the challenges of performing codechecks with sensitive or confidential data, a situation that many in our audience were all too familiar with, being from the social and behavioural sciences. Incentivising and growing the codechecking community is always an interesting part of the reflection, and answers ranged from monetary compensation and making it a job, to fame and glory (if only!).
 
 We ended the session with a well-deserved borrel, a satisfying end to a productive day! Would you also like to be rewarded with bitterballen after a day of coding? Join our next workshop on 14 February at Leiden University! Find out more on the [workshop page](https://codecheck.org.uk/nl/workshop4).
 
@@ -27,21 +27,21 @@ We ended the session with a well-deserved borrel, a satisfying end to a producti
 
 **Are you from the social/behavioural sciences and interested in reproducible code and open science? We have the perfect opportunity for you!**
 
-As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the social and behavioural sciences at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 28 November 2024.** A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
+As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the social and behavioural sciences at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 28 November 2024.** A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
 
 You can participate (a) by submitting your own work to be checked, (b) as a codechecker (that is, a person reviewing code as a participant in the workshop), or (c) both, if you are up for it! Read on to see how…
 
 ## What do I get if I submit my code?
 
 - A codechecker will work with you during the session to check whether your code and data can be run by others to generate the same or similar results.
 - The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible!
-- Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced.  This can be shared, for instance, with potential journal editors, to enhance the visibility and reproducibility of your work.
+- Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced.  This can be shared, for instance, with potential journal editors, to enhance the visibility and reproducibility of your work.
 
 By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research!
 
 ## Sounds good! What should I do?
 
-Are you interested in participating in this event, and contribute to promoting code reproducibility? Send an email to <[email protected]> **by 11 November 2024** with **a brief description of your paper/project, and links to your code and data**. This could be code related to:
+Are you interested in participating in this event, and contribute to promoting code reproducibility? Send an email to <[email protected]> **by 11 November 2024** with **a brief description of your paper/project, and links to your code and data**. This could be code related to:
 
 - A paper that you have recently published
 - A preprint that is publicly available
@@ -64,4 +64,4 @@ You can register to participate in the workshop on our [eventbrite page](https:/
 *PhD candiates at the Erasmus Graduate School for Social Sciences and the Humanities are eligible for 1.5 ECTS credit for participating in the workshop, see [this page](https://www.eur.nl/en/egsh/course/code-check-your-research) for more information.*
 
 Interested but still have questions? Ask us!
-Write to us at <[email protected]>, we are happy to answer any questions!
+Write to us at <[email protected]>, we are happy to answer any questions!