Open Source Projects that are released by companies start their lives in many diff ways. You are right, some start with open source in mind like SDKs, CDKs etc. Some are often developed inside, but seek support to open source it. All companies use some due diligence on what makes it out and help developers release it to open source. The OSPO works hard to make sure that the developers understand their responsibilities once released and to set aside time to set up the project correctly and to support it. The reality is that sometimes, developers change roles, companies and interests and may stop supporting. The OSPO tries to find projects that are not supported and either find other maintainers inside the company or outside or archive it. Yes, we strongly encourage developers to set aside time to maintain their projects. In some cases, we will have whole teams that are dedicated to maintaining a project we release.
For further actions, you may consider blocking this person and/or reporting abuse
A community for COSS builders, founders, consumers, investors, and fans.
Open Source Projects that are released by companies start their lives in many diff ways. You are right, some start with open source in mind like SDKs, CDKs etc. Some are often developed inside, but seek support to open source it. All companies use some due diligence on what makes it out and help developers release it to open source. The OSPO works hard to make sure that the developers understand their responsibilities once released and to set aside time to set up the project correctly and to support it. The reality is that sometimes, developers change roles, companies and interests and may stop supporting. The OSPO tries to find projects that are not supported and either find other maintainers inside the company or outside or archive it. Yes, we strongly encourage developers to set aside time to maintain their projects. In some cases, we will have whole teams that are dedicated to maintaining a project we release.