You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Questions regarding co-creation


Github is an ideal place to work together with colleagues and also external parties. In the new organization https://github.com/Deltares-research, there are a few ways to work with outside collaborators:


  1. Use PULL REQUESTS. Allow your repository to accept pull requests. This way collaborators do not require to be added (and managed) as 'Outside collaborators'. This works well for PUBLIC repositories.
  2. Invite an outside collaborator to your organization and then assign them to your repository. For PUBLIC repositories no license is claimed for PRIVATE repositories 1 license is claimed. No additional costs for adding the same collaborator to multiple repositories.

Questions relating to migration

Problem

I want to request a new Github repository for my project or software product, but I do not know which of the two Deltares organizations I must choose: Deltares or Deltares-research

Solution

You do not need to choose anything, this will be done for you base on the information provided during the registration process.

What is the difference between the two organizations?

Deltares organization: This organization is meant to house all repositories that are linked to a Product Management Team (PMT) and contain production ripe software.

Deltares-research: All repositories that do not fit into the Deltares organization.

Problem

After your repository is moved from https://github.com/Deltares to the new organization https://github.com/Deltares-research, it is possible that you are required to re-authorize the OAuth Application when you perform a GIT action on the command line.

Solution

Follow the following steps to refresh you authorization token:

  1. Open the Credential Manager in Widows. ( type 'Credential Manager')
  2. In Credential Manager select 'Windows Credentials'


  3. Lookup the credentials for git:https://github.com and remove this.
  4. Re-initialise the cred manager in git bash: git config --global credential.helper manager-core
  5. Re-run git pull and follow the pop-up instructions to authenticate in a browser (which happened automatically for me with SSO).


After your repository is moved from https://github.com/Deltares to the new organization https://github.com/Deltares-research, the list of collaborators has been cleared. Each repository is assigned one administrator who is tasked with inviting new collaborators.

Inviting new collaborator can be done by the Administrator using the 'Add people' button.

Invite collaborators using e-mail: It is important to know that when inviting new Deltares collaborators, you must invite them using their Deltares e-mail address. This assures that all members are part of the Deltares domain.

For bigger repositories it is advised to user teams instead of adding individual users. At present it is not possible for administrators to create a Team. In such cases the administrator should send a request to the Github support group: github-support@deltares.nl

Questions relating to applications

In the current Deltares organization, co-pilot has been enabled. There are 24 licenses available, all of which are currently taken. At present co-pilot is not enabled in the Deltares-research organization. This will change once the Deltares organization has been added to the Deltares enterprise.

How we plan to use co-pilot in the future and how we plan to manage the licenses has not yet been worked out. For more information please contact: github-owners@deltares.nl .

Apparently some users can no longer see their repositories in Zenodo. Even when their repositories have not been moved from the Deltares organization. Why this is the case is still unclear however the resolution is that one of the organization owners logs into Zenodo using ones Github account and activates the required repositories.

  • No labels