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

GitHub Deceased User Successor policy and target settings #35407

Closed
1 task done
ShaneCurcuru opened this issue Nov 24, 2024 · 2 comments
Closed
1 task done

GitHub Deceased User Successor policy and target settings #35407

ShaneCurcuru opened this issue Nov 24, 2024 · 2 comments
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@ShaneCurcuru
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories

What part(s) of the article would you like to see updated?

How can a user submit either a GH Organization as a successor, or submit more than one GH User account as a successor?

When making succession planning, it's often helpful to be able to choose multiple successors - for example a traditional will/trust will have successor executors in case the first one is unable to serve. Ensuring that an ordered list of GH Successor users could be added to a single account would better mirror traditional estate planning norms.

Similarly, many open source projects start with one person, but grow to have a major impact on software organizations. Being able to list an Organization object, where any Admin from that Organization could then apply to become the successor (either as the Organization or as an individual) would be immensely valuable for many FOSS Foundations and the like.

Apologies if this is a policy question that should best be answered elsewhere; please feel free to redirect me to the right place!

Additional information

No response

@ShaneCurcuru ShaneCurcuru added the content This issue or pull request belongs to the Docs Content team label Nov 24, 2024
Copy link

welcome bot commented Nov 24, 2024

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Nov 24, 2024
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Nov 25, 2024
@nguyenalex836
Copy link
Contributor

@ShaneCurcuru Hello! 👋 That is a great question!

While our team is unfamiliar with the details of that process, our wonderful support team is best equipped to assist ✨ They'll be happy to help!

If there's anything else in the documents that you have suggestions for updating, please feel free to open an issue 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

No branches or pull requests

2 participants