Update contribute.md

main/contribute.md

@@ -4,4 +4,56 @@ title: Contribute
 
 ## Contributing to this lesson
 
-Add contributing guidelines for you project.
+# Contributing to this Research Software Support platform
+
+In the RSE training modules we want to provide a comprehensive overview of the different aspects of Research Software and how to provide support to researchers.
+This, as you can imagine, is no easy feat, and we need your help!
+So first of all, thank you very much for your interest in contributing to this project.
+
+### What can I do?
+
+- Contribute to the content discussion in the [module issues](https://github.com/NLESC/internal-training/issues?q=is%3Aissue+is%3Aopen+label%3A%22module+update%22%2C%22new+module%22%2C%22all+modules%22), e.g. by listing good resources for information.
+- Author a new module by creating a [new issue and pr](#how-can-i-do-it), while taking into account the [documentation for creating a new module](https://github.com/esciencecenter-digital-skills/NEBULA-docs/blob/main/module-dir-structure.md)
+- Review a lesson module; both by looking at [open PRs](https://github.com/esciencecenter-digital-skills/research-software-support/pulls), as well as flagging issues for improvement in the [existing content](https://esciencecenter-digital-skills.github.io/research-software-support/).
+- [Provide feedback](https://github.com/NLESC/internal-training/issues) on the different subjects covered: what did we miss? Should something be restructured?
+
+### How can I do it?
+
+If you want to contribute to the content: look whether the issue you want to tackle [already exists](https://github.com/NLESC/internal-training/issues) or make a [new issue](https://github.com/NLESC/internal-training/issues/new), and [create a PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) with your changes from a fork or a branch. 
+
+It is useful to take a look at [the NEBULA documentation](https://github.com/esciencecenter-digital-skills/NEBULA-docs) and specifically review [the section on directory structure and content tags](https://github.com/esciencecenter-digital-skills/NEBULA-docs/blob/main/module-dir-structure.md) before you start. 
+
+## Target audience
+
+The target audience for this material is research software engineers.
+
+On a practical level, this means that these modules do not need to be very technical.
+For example, a module on version control does not need to explain the details of Git and the different commands.
+What it does need to do is explain why version control is important, and why it matters particularly in a research context.
+A participant should walk away with a more elaborate vocabulary around a subject, knowledge on where and how to find more information, and motivation that they could transfer to others.
+
+## Philosophy
+
+As you are contributing to this material, please keep a few principles in mind:
+
+### The material should be broadly usable
+
+It should be ready for teaching both online and offline; in a regular and a flipped classroom; and even for self study.
+
+The modules in this repository will be used as lesson materials for a live audience, and provide a resource for self-study.
+Every module should therefore contain some essential classroom elements (e.g. slides, group exercises), as well as exercises that can be done individually, and reference material that can be read at home.
+
+### The modules should be easy to (re)use
+
+It is important that anybody can work with the material in this repository.
+Slides should therefore contain complete notes for an instructor, which can also be used in self-study.
+Exercises should be clearly explained, and where possible, times should be given for different parts of the lesson so an instructor can plan a workshop around these materials.
+
+### Maintenance load should be kept to a minimum
+
+We all know how fast things change, and how quickly information becomes outdated.
+It is important to keep this in mind when creating lesson materials, and focus on core concepts, rather than specific tools and details.
+Where it is useful to mention these, consider linking to external resources that will be maintained by others.
+
+In general, it is better to link to external resources than to rewrite information that already exists elsewhere.
+This, too, will limit the amount of maintenance that is required.