Join us


Nordic Earth System Modeling hub is an open source project, and we welcome contributions of all kinds:

Contributor Agreement

By contributing, you agree that we may redistribute your work under our license. In exchange, we will address your issues and/or assess your change proposal as promptly as we can, acknowledge your contributions and help you become a member of our community. Everyone involved in Nordic Earth System Modeling hub agrees to abide by our code of conduct.

How to Contribute

The easiest way to get started is to file an issue to tell us about a spelling mistake, some awkward wording, or a factual error. This is a good way to introduce yourself and to meet some of our community members.

  1. If you have a GitHub account, or are willing to create one, but do not know how to use Git, you can report problems or suggest improvements by creating an issue. This allows us to assign the item to someone and to respond to it in a threaded discussion.

  2. If you are comfortable with Git, and would like to add or change material, you can browse the list of existing issues (see below) and submit a pull request (PR). Instructions for doing this are included below.

Where to Contribute

NordicESMhub repositories have many open issues where you are welcome to contribute.

  1. If you wish to change this repository, please work in, which can be viewed at

  2. If you wish to change another repository in the NordicESMhub organization, please review guideline of the corresponding repository. In the section below, we list priority areas but these are mostly to help you to find where to contribute.

  3. If you wish to add a new repository in the NordicESMhub organization, create a new issue in this repository. Do not forget to mention the purpose of your issue.

What to Contribute

There are many ways to contribute, from writing new tools and improving existing ones to updating or filling in the documentation and submitting bug reports about things that don’t work, aren’t clear, or are missing. If you are looking for ideas, please see the ‘Issues’ tab for a list of issues associated with each repository.

Comments on issues and reviews of pull requests are just as welcome: we are smarter together than we are on our own. Reviews from novices and newcomers are particularly valuable: it’s easy for people who have been using these lessons for a while to forget how impenetrable some of this material can be, so fresh eyes are always welcome.


Here is a non-exhaustive list of repositories for which we need your help:

For UiO folks

Using GitHub

If you choose to contribute via GitHub, you may want to look at How to Contribute to an Open Source Project on GitHub. To manage changes, we follow GitHub flow.

Each issues and pull requests are reviewed by volunteers and we also encourage you to do so. The repository owners have final say over what gets merged into the lesson so it is often good practice to discuss your plans in an issue before you implement anything.

To use the web interface for contributing to a lesson:

  1. Fork the originating repository to your GitHub profile.
  2. Within your version of the forked repository, move to the master branch and create a new branch for each significant change being made.
  3. Navigate to the file(s) you wish to change within the new branches and make revisions as required.
  4. Commit all changed files within the appropriate branches.
  5. Create individual pull requests from each of your changed branches to the master branch within the originating repository.
  6. If you receive feedback, make changes using your issue-specific branches of the forked repository and the pull requests will update automatically.
  7. Repeat as needed until all feedback has been addressed.

When starting work, please make sure your clone of the originating master branch is up-to-date before creating your own revision-specific branch(es) from there. Additionally, please only work from your newly-created branch(es) and not your clone of the originating master branch.