This service is for collaborating on code and scripts. It is not designed to be a data sharing
or storage service. In doubt please ask
Students, researchers, and staff affiliated with a Nordic academic institution.
If you are not sure whether you can use the system, please contact
Register your user account using your university email account. Then write an
email@example.com where you state your affiliation and in two
sentences (or more) describe briefly why you would like to use this service
and how you plan to use this service.
Yes, your collaborators can join your projects but cannot create new projects. Ask them to register and then you can add them to your projects or groups as collaborators.
We are working on it - currently you need a specific user account for this instance. If you create an account with the email address your identity federation gives provides for you, then you can later move to single sign on seamlessly.
Currently no limit is enforced but we recommend less than 100 MB per project. This should really be for code and not for persistent storage of data. If you use more, we will contact you. If you need more, please contact us and motivate why you need more and we will see what we can do about it. If you have a good motivation, you will probably get a larger soft limit.
The service is currently run from and the data is stored on servers at CSC - IT Center for Science in Finland. CSC is part of the Nordic e-Infrastructure collaboration funding this project.
The Git repositories, wikis, as well as issues and metadata is backed up daily. The backup is stored for the past 90 days. Backup older than 90 days is periodically discarded manually. We reserve the right to reduce the number of days backed up if space becomes an issue. Backups and the service are run in the same OpenStack cloud that is hosted in a single data center, so major catastrophes may result in the loss of both data and backups.
Initially we will announce service breaks through messages displayed once you log into the platform. Later we will set up an opt-in mailing list for service downtime notifications. In addition, we plan to announce service breaks over Twitter via @coderefine.
We are currently funded until September 2018. We are actively working on securing long-term funding for this service. The goal is to create a service for many years to come. If we do not manage to secure long-term funding, we will notify users well in advance and assist in migrating repository and data.