Hello Nithya! I'm curious about how open source projects generally come to life in a large organization like AWS. It makes sense for me to think some of them are conceived with open source in mind since their inception (SDKs, CLIs, etc), but are you all periodically reviewing the internal tooling developed by engineers to make them public? Are teams that developed these encouraged to proactively nominate their tools/code through a defined process?
Follow up in case the second question above is somewhat on point with the way things work there:
Are engineers that used to work on them encouraged to dedicate part of their work hours to maintain them? Or does maintainer tasks on these (think feature requests, folks asking questions, etc) becomes a responsibility of a dedicated team?
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.
Hello Nithya! I'm curious about how open source projects generally come to life in a large organization like AWS. It makes sense for me to think some of them are conceived with open source in mind since their inception (SDKs, CLIs, etc), but are you all periodically reviewing the internal tooling developed by engineers to make them public? Are teams that developed these encouraged to proactively nominate their tools/code through a defined process?
Follow up in case the second question above is somewhat on point with the way things work there:
Are engineers that used to work on them encouraged to dedicate part of their work hours to maintain them? Or does maintainer tasks on these (think feature requests, folks asking questions, etc) becomes a responsibility of a dedicated team?
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.