Feature Request: Memorial Accounts for Deceased GitHub Users

[ghost1372]

Discussion Type

Product Feedback

Discussion Content

Introduce a Memorial Account feature for GitHub users who have passed away.

Similar to memorialization features on other platforms, this would allow a deceased developer's account to remain available as a permanent tribute to their work and contributions.

Possible features include:

Memorial Badge: Display a special badge or label on the user's profile indicating that the account has been memorialized in honor of its owner.

Account Protection: Lock the account to prevent unauthorized access, changes, or deletion while keeping its public profile and repositories accessible.

Repository Preservation: Keep the owner's public repositories, issues, discussions, and contributions available so future developers can continue learning from their work.

Respectful Profile Notice: Display a small, respectful message indicating that the account is being preserved in memory of its owner.

Memorialization Request: Provide a process for family members or other authorized representatives to request memorialization, with appropriate verification.

Why Is This Important?

Open-source development is built on the contributions of people from all over the world. Some developers spend years creating libraries, tools, and projects that benefit thousands of people, often without recognition beyond the community that uses their work.

When a developer passes away, their GitHub account can become more than just an inactive profile. It becomes a lasting record of their creativity, knowledge, and contributions.

Deleting such an account could mean losing valuable repositories, historical discussions, and a part of open-source history. A memorial account would help preserve that legacy while showing respect for the person behind the code.

Final Thoughts

GitHub is not just a platform for hosting code; it is also a place where developers leave a lasting mark on the world.

A memorial account feature would be a meaningful way to honor those who are no longer with us, protect their work from accidental loss, and allow the community to continue benefiting from what they created.

Our code can outlive us. GitHub could help ensure that our contributions, and the people behind them, are not forgotten.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐