-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organization to contain software packages? #47
Comments
I agree. MUTIS for example is already under https://github.com/IAA-CSIC organization. Would that work? |
I agree, @rlopezcoto, can you create the VHEGA organization? I have to check what happens with the zenodo DOI. |
I think we should have a VHEGA organization, independently of whether IOP4 goes in it or in the IAA-CSIC one. It also needs to be an organization where I can create repositories, for GitHub to be able to transfer (so we would have to ask IAA-CSIC). |
do you know who is the admin of the IAA-CSIC organization? |
Probably @bultakoo. |
https://github.com/organizations/VHEGA/ I'm setting permissions and so on, please check if you have admin privilegies and so on |
@juanep97, @morcuended I made you owners of VHEGA, please let me know if you need anything else to be set up (or you can do it yourselves, I think that now we should have the same permissions) |
Hi, since this software is meant to be published in a refereed publication and so on, it always looks better if it is contained in a "permanent" organization instead of a personal github repo.
I suggest that we can create the "vhega" organization and migrate libraries like this one (maybe also MUTIS) The migration should be transparent for owners/admins and so on, but it will just be contained under a different URL that will make it look more permanent.
The text was updated successfully, but these errors were encountered: