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

Compare with Current View Page History

« Previous Version 21 Next »

Questions regarding co-creation

Questions relating to migration

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

No there is not.

When you have questions regarding the new GITHUB environment you can post them to the GITHUB support team. We can then try to connect you to people who already have experience with GITHUB. Otherwise we suggest you contact your department head for funding.

There is no fixed definition of 'production-ripe' software. It is up to the Product Management Teams (PMT) to decide if they wish to designate certain repositories / products as production ripe or as research. 

All repositories under the Deltares organisations should be linked to one of the PMT;s. If unsure about the status of your repository please contact the PMT and discuss with them where your repository fits best.

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.

I want to use my own Github account that I've used thus far (linked to my private e-mail address). Can I do that and if yes, how?


It is possible to use your existing GITHUB account. However if you work for Deltares, you will have to assign your Deltares email to your GITHUB account. All Deltares employees will be invited their Deltares email address.

  • No labels