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 Packages/Namespaces functionality Design #16

Open
henilp105 opened this issue Mar 2, 2023 · 6 comments
Open

Transfer Packages/Namespaces functionality Design #16

henilp105 opened this issue Mar 2, 2023 · 6 comments

Comments

@henilp105
Copy link
Member

The transfer account functionality allows sudo admins to transfer accounts of inactive/non-maintained packages/namespaces to a different user , to develop this functionality, I have considered the following methods to implement this functionality, this functionality would only be allowed to be executed to sudo admins.

we could directly allow the sudo admin to transfer the account , allow the sudo admin to change username, email, and send a password reset request to new email and all the packages and the namespace access would be directly transferred to the new username and old account would not be deleted and we could show the account has been transferred and redirect them to the new account ( by this method only when the packages are seen on the /users/<username> of the frontend would change , else every where it would be exactly similar to the original.

I would like to request all the Community members to review and add suggestions/discussions of this functionality.

Thanks and Regards,
Henil Panchal

CC @certik @awvwgk @arteevraina @minhqdao @perazz @milancurcic @everythingfunctional

@everythingfunctional
Copy link
Member

Just to clarify, is this proposing to transfer ownership of abandoned user accounts to a new user? Or is it more of a bulk transfer of all of one user's projects and namespaces to another user?

@henilp105
Copy link
Member Author

@everythingfunctional It would be proposing to transfer the ownership of accounts which have inactive/non-maintained packages/namespaces but are of importance to the community , it would be like bulk transfer of all of one user's projects and namespaces to another user.

@everythingfunctional
Copy link
Member

I would just think of it as bulk package/namespace transfer, not account transfer.

@henilp105
Copy link
Member Author

sure, it seems to be more apt to bulk transfer the packages/namespaces than the entire account.

@henilp105 henilp105 changed the title Transfer Account functionality Design Transfer Packages/Namespaces functionality Design Mar 3, 2023
@arteevraina
Copy link
Member

arteevraina commented Mar 7, 2023

@everythingfunctional It would be proposing to transfer the ownership of accounts which have inactive/non-maintained packages/namespaces but are of importance to the community , it would be like bulk transfer of all of one user's projects and namespaces to another user.

In this case, namespace would remain constant and then it won't matter to the fpm client since they need the namespace name and package name to get the packages. Are we just transferring the ownership without changing the namespace or is it like packages listed under namespaceA would be listed now under namespaceB ?

@everythingfunctional
Copy link
Member

In this case, namespace would remain constant and then it won't matter to the fpm client since they need the namespace name and package name to get the packages. Are we just transferring the ownership without changing the namespace or is it like packages listed under namespaceA would be listed now under namespaceB ?

My understanding is it would just be transferring ownership, no names would change.

arteevraina pushed a commit to arteevraina/registry that referenced this issue Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants