-
Notifications
You must be signed in to change notification settings - Fork 428
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
Moving this repo to ros-perception? #151
Comments
It sounds like a good idea to me. Are there any disadvantages at all? |
No, there are no disadvantages. The prerequisite is that you need to have "owner" permissions in the The actual transfer will happen like this: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-organization In the meanwhile, I've created a new post on discourse: https://discourse.ros.org/t/moving-imu-tools-to-ros-perception-github-organization/23067 . Let's hope somebody with the proper permissions to |
Unfortunately I do not have nay of those. I can ask to get 'admin' role to this repo. I will let you know. |
Yes, it would be really great if you could do that! |
One of the @robertogl : Could you try again getting the proper permissions? @ehoxha91 : You've mentioned in #94 that you know who might have the proper permissions to this repo. Could you try again asking for the permissions? @idryanov : I know you haven't been active here for a couple of years, but if by any chance you read this, could you give me or @robertogl the permissions? I would hate to fork this repository into ros-perception instead of doing a proper move. We would lose all the github stars, issues and the network of forks, but I guess it's something we have to do at some point if we can't get the permission issue sorted out. |
@mintar I have the password of the account, but the issue is that whenever I’m not in the office I cannot login (2-Factor Authentication and I don’t have the access to the email address to get the code). For some reason I don’t need 2FA when I am in the Lab. As soon as I go in there I will give @robertogl and you the admin privileges. |
@ehoxha91 : Great, please keep us updated!
That's probably because you (or someone else) already logged in from that PC using 2FA. Let's just hope nobody clears the browser cache or reinstalls the machine, otherwise you could lose access to this GitHub organization permanently... I just hope you don't need 2FA to give @robertogl and me the admin privileges... |
@mintar the thing is that the machine I use on lab is a new one, just recently used. This issue started few months ago. If I need 2FA to give the admin privileges then we will need access to one of these emails: "We just sent your authentication code via email to c**************@gmail.com and r**************@gmail.com." |
@ehoxha91 : Any updates? |
@mintar Prof. Xiao is coming to the lab today so I’ll try to do it, and ask him for access to the email too. |
Perfect, thanks! |
Prof. Xiao (@ccny-ros-pkg) has agreed to move this repo to ros-perception. He will either give me admin access or transfer the repository to @clalancette. @clalancette: If you get an invitation email from GitHub that asks whether you want to allow transferring this repo to your user account, could you accept and then move it to ros-perception? I think this detour is necessary because the repo cannot be transferred directly to ros-perception by users without repository creation permissions on ros-perception. The invitation email expires after 1 day, that's why I'm giving you an advance warning. :) |
Yes, I can do that. But do note that I'm away from December 24 - Jan 3, so I may or may not see it during that time. |
Understandable, I'm on vacation during that time as well. This might be the worst time of the year to do this... let's see! |
After many, many discussions and iterations, we've decided not to move this repo to |
Dear @robertogl , what do you think about moving this repo to the official ros-perception GitHub group? We would still be maintainers, all repo and git URLs etc. would continue to function (because GitHub will add a redirect), the issues, forks, stars etc. would also be transferred. The advantages would be:
Also a nice side benefit would be that I could finally get proper permissions to do things like finally update the default branch of the repo. It's still set to
indigo
, which went EOL in 2014. This causes regular bugs when people try to compile from source and don't realize that they are using an outdated version of the repo...The text was updated successfully, but these errors were encountered: