Skip to content
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

transfer ownership #4

Closed
carandraug opened this issue May 22, 2018 · 6 comments
Closed

transfer ownership #4

carandraug opened this issue May 22, 2018 · 6 comments
Assignees

Comments

@carandraug
Copy link
Member

Hi Tom, could you transfer this repo to us? The way it's done, had Micron's as a fork so we didn't even had the issues there.

@coralmw
Copy link
Contributor

coralmw commented May 22, 2018

Yes, of course, should I transfer it to you/Mick/micron org account?

@coralmw coralmw self-assigned this May 22, 2018
@carandraug
Copy link
Member Author

carandraug commented May 22, 2018 via email

@coralmw
Copy link
Contributor

coralmw commented May 22, 2018

Couple of problems! "MicronOxford/RedPitaya-DSP already exists and You don’t have the permission to create repositories on MicronOxford".

I don't know what the ideal solution is, but if we want the MicronOxford repository to not be a fork it might be best to

  1. delete MicronOxford/RedPitaya-DSP
  2. push from a local repo to MicronOxford/RedPitaya-DSP, creating it anew with whatever history that repository has.

Thoughts?

@carandraug
Copy link
Member Author

carandraug commented May 22, 2018 via email

@coralmw
Copy link
Contributor

coralmw commented May 22, 2018

Makes sense, done. It's under the sysadmin team right now, I figured if there was a permissions structure the members of that team would be able to set it up correctly.

@carandraug
Copy link
Member Author

Makes sense, done. It's under the sysadmin team right now, I figured if there was a permissions structure the members of that team would be able to set it up correctly.

That's perfect. I'll take it from here. Thank you. And do comment on the renaming of the project too if you have a preference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants