... | ... | @@ -8,12 +8,16 @@ INRIA Forge project administrators and/or users need to coordinate to decide *wh |
|
|
|
|
|
Coordination is paramount because if, as a project admin, you migrate for example the source control repository without telling the users, some of them might still use the old repository on the forge for checkouts or commits.
|
|
|
|
|
|
## Available documentation
|
|
|
## Available documentation and help
|
|
|
|
|
|
The gitlab documentation is available here: https://gitlab.inria.fr/help
|
|
|
|
|
|
Beware that gitlab is both a software (gitlab) and a free hosting platform (https://gitlab.com). In many places in the documentation, the links given point to https://gitlab.com, you have to replace these by links to our instance: https://gitlab.inria.fr
|
|
|
|
|
|
Migration support is available through the [inria helpdesk](https://helpdesk.inria.fr), in section "IT request", subsections "Ask for a fix" or "Service request" / "Services for research " / "GitLab" or "Inriaforge"
|
|
|
|
|
|
A mattermost channel is also available https://mattermost.inria.fr/devel/channels/gforge-gitlab (but remember that the preferred way to ask for support is through the helpdesk because support tickets can be correctly tracked)
|
|
|
|
|
|
## Migration of source control repositories
|
|
|
|
|
|
INRIA gitlab is restricted to git (no subversion anymore), so for subversion users unfamiliar with git, you should take the time to read and understand the basic differences between subversion and git. If you want to stay with subversion, there is no alternative at INRIA, but you can go to SourceSup https://sourcesup.renater.fr/, which is actively maintained by Renater.
|
... | ... | |