.gitlab/issue_templates/bug.md

+<!-- Please include a self-contained copy-pastable example that generates the issue if possible
+
+Please be concise with code posted. See guidelines below on how to provide a good bug report:
+
+- Craft Minimal Bug Reports: http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports
+- Minimal Complete Verifiable Examples: https://stackoverflow.com/help/mcve
+
+-->
+## Summary
+
+(Summarize the bug encountered concisely)
+
+
+## What is the current bug behavior?
+
+(What actually happens)
+
+Examples:
+
+- be specific about what in the verification pipeline may be wrong
+- be specific about what in the data (forecasts/observations) may be wrong
+- be specific about what in the xskillscore.rps code is wrong (maybe raising an issue in [xskillscore](https://github.com/xarray-contrib/xskillscore) is more relevant)
+
+
+## What is the expected correct behavior?
+
+(What you should see instead)
+
+
+## Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+```python/bash
+code
+```
+
+or link to notebook/gist.
+
+(Maybe just create an example project here on GitLab.com that exhibits the problematic
+behavior, and link to it here in the bug report)
+
+## Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as
+it's very hard to read otherwise.)
+
+## Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~bug
+/cc @aaron.spring

.gitlab/issue_templates/discussion.md

+<!-- 
+#️⃣ General: Chat about anything and everything here
+💡 Ideas: Share ideas for new features and efficient workflows
+🙏 Q&A: Ask the community and organizers for help, will be transfered to the [FAQ](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge/-/wikis/Frequently-Asked-Questions-(FAQ))
+🙌 Show and tell: Show off something you've made
+-->
+
+/label ~discussion
+/cc @aaron.spring
\ No newline at end of file

.renku/metadata.yml

@@ -2,7 +2,7 @@
 '@type':
 - http://schema.org/Project
 - http://www.w3.org/ns/prov#Location
-http://schema.org/agent: 0.14.2
+http://schema.org/agent: 0.15.1
 http://schema.org/creator:
   '@id': mailto:aaron.spring@mpimet.mpg.de
   '@type':

Dockerfile

@@ -27,7 +27,7 @@ RUN conda env update -q -f /tmp/environment.yml && \
 # RENKU_VERSION determines the version of the renku CLI
 # that will be used in this image. To find the latest version,
 # visit https://pypi.org/project/renku/#history.
-ARG RENKU_VERSION=0.14.2
+ARG RENKU_VERSION=0.15.1
 
 ########################################################
 # Do not edit this section and do not add anything below

OPEN_REVIEW_GUIDELINES.md

+# Open review guidelines
+
+One goal of this challenge is to foster a conversation about how AI/ML can improve S2S forecasts.
+Therefore, we will open the floor for discussions and evaluating all methods submitted
+in an open peer review process. The organizers created a table of all submissions and
+everyone is invited to comment on submissions, like in the
+[EGU’s public interactive discussions](https://www.egu.eu/publications/statement/online-open-access-publishing/).
+This open peer review will be hosted on renku’s gitlab via the issue tracker.
+Please use the links provided by the [leaderboard](https://s2s-ai-challenge.github.io/#leaderboard) for the respective repositories.
+
+Participants are asked to answer to review questions and
+the expert review judgement may take the open review discussions into account.
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and organizers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* Edit or delete comments created by others. If you find your review comments
+  edited/deleted by the repository owner, please contact the organizers.
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+The organizers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Organizers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the [organizers](mailto:aaron.spring@mpimet.mpg.de). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The organizers team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

README.md

-# s2s-ai-challenge
+# `s2s-ai-challenge`
 
-This is the gitlab project organizing the `s2s-ai-challenge`. It hosts:
+The submission period for the `s2s-ai-challenge` ended.
+However, the `s2saichallengescorer` still remains active. So you can still verify your 2020 predictions in the future and they will show up in the [RPSS leaderboard](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge-leaderboard), but do not qualify for prizes.
+
+During open and expert peer review from November 2021 to January 2022, there is the possibility to ask questions to the submitting teams. Do so by clicking on the review button of the respective repository in the [leaderboard](https://s2s-ai-challenge.github.io/#leaderboard) and open an issue or read other issue comments.
+
+---
+
+This is the gitlab project organizing the [`s2s-ai-challenge`](https://s2s-ai-challenge.github.io). It hosts:
 
 - [issue tracker](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge/-/issues) for discussions under the `discussion` label.
 - [issue tracker](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge/-/issues) for issues regarding the code and organization to be reported by users and organizers.
 - [wiki](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge/-/wikis/home) for more information, e.g. FAQ transferred from issue tracker, resources, etc.
 
+To enter a submission for the competition, please follow [instructions](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge-template)!
+
+[Find other parts of the competition here](https://renkulab.io/gitlab/aaron.spring/s2s-ai-challenge/-/wikis/Flow-of-information:-Where-do-I-find-what%3F)!