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

TODO Guide: Transitioning ownership of an open source project #273

Open
ashleywolf opened this issue Jan 5, 2022 · 2 comments
Open

TODO Guide: Transitioning ownership of an open source project #273

ashleywolf opened this issue Jan 5, 2022 · 2 comments

Comments

@ashleywolf
Copy link
Member

Creating this issue so we can collaborate on a guide for transitioning ownership of an open source project.

@anajsana
Copy link
Member

anajsana commented Feb 2, 2022

Thanks @ashleywolf ! In order to help you with this guide, I need an answer from the same questions I asked at: #283 (comment)

Also, could you please elaborate more on this TODO guide idea? For instance, proposing a TOC structure and a detailed description in this issue will work 👍

@gyehuda
Copy link
Member

gyehuda commented Feb 11, 2022

@ashleywolf If you put together a TOC I can add some content. For example, you and I penned some of this already where we handled the support process for projects to be archived (or transferred to an employee who left the company) https://yahoo.github.io/oss-guide/docs/promoting/support.html#tier-4-archived-projects and more elaboration of "ownership" when it comes to company managed projects.
https://yahoo.github.io/oss-guide/docs/resources/ownership.html

I'd guess the other case to add is when a company transitions ownership of a project to a foundation -- and each foundation has a process for that.

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

No branches or pull requests

4 participants