You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an organization would like to create their OSPO use case and publish this in TODO, they should provide some details about their OSPO initiative, so we can help build the use case and use the same format for each one.
The ideal format should be a Q&A design, like:
Organization name, region, and industry
Contact information to reach out
What's the official name of your OSPO?
Could you please share a brief story of the organization's Open Source Journey?
Why did your organization decide to invest in an OSPO?
Is your Organization a TODO Member?
If so, how does TODO help your OSPO?
How is your OSPO structured?
What achievements and milestones have your OSPO accomplished so far?
Would you like to share any upcoming news about your OSPO? (upcoming releases, talks etc)
Closing Conditions
Elaborate a content for todo's case-study-guidelines.md
Create use-case-proposal.yml file
Review and merge
The text was updated successfully, but these errors were encountered:
I like the idea of using a guideline doc similar to CNCF that points to a proposal form (in TODO's case, to a GH issue form).
I'm planning to elaborate a content proposal for a potential todo case-study-guidelines.md and add it to this issue for review, as well as a questionnaire draft for the GH issue form 👍
Goal
Ease new OSPO use cases contributions
Description
If an organization would like to create their OSPO use case and publish this in TODO, they should provide some details about their OSPO initiative, so we can help build the use case and use the same format for each one.
The ideal format should be a Q&A design, like:
Closing Conditions
use-case-proposal.yml
fileThe text was updated successfully, but these errors were encountered: