-
Notifications
You must be signed in to change notification settings - Fork 96
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 OSPO Ambassador] Request - Thomas Steenbergen #350
Comments
Thanks for your interest to joining the TODO Ambassador Program @tsteenbe I will froward this issue to the SC members to review your proposal and will get back to you! |
/vote |
Vote created@justaugustus has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
Vote closedThe vote passed! 🎉
Summary
Binding votes (4)
|
Thanks for your patience @tsteenbe . We are glad to inform that the SC members review your proposal, and final vote was in favor to approve your application to become a TODO Ambassador 🎉 Welcome! Please allow 3-4 business days for me to start the onboarding process. An email with instructions and more details will be sent to you 🙂 |
Approved by TODO Steering Committee in [1]. [1]: todogroup/governance#350 Signed-off-by: Thomas Steenbergen <opensource@steenbe.nl>
Approved by TODO Steering Committee in [1]. [1]: todogroup/governance#350 Signed-off-by: Thomas Steenbergen <opensource@steenbe.nl>
Approved by TODO Steering Committee in [1]. [1]: todogroup/governance#350 Signed-off-by: Thomas Steenbergen <opensource@steenbe.nl>
TODO OSPO Ambassador Request
This is an issue created to request to become an OSPO Ambassador. If you (as individual) are interested to apply, please make sure you have (1) read the TODO OSPO Ambassador Program documentation
and (2) fulfil the requirements from the Pre-submission checklist.
Pre-submission checklist:
Contact Information
We would need the following information about you to get in contact if elected:
Current involvement in TODO Community
I have been actively engaged with the TODO group since 2017, officially joining in February 2018 as the Open Source Program Lead at HERE Technologies and from 2023 as Head of Open Source at EPAM. Over the years I have regularly contributed to the TODO community by delivering talks at various conferences, collaborating on whitepapers, news letters and the OSPO mindmap, and co-founding both the European Chapter of the TODO group and the OSPOlogy.live initiative. Most recently, I served on the TODO steering committee from 2022 to 2023, further solidifying my commitment to advancing open source operations knowledge sharing and fostering community engagement/growth.
Who are you?
REQUIRED: What do you expect from TODO Group as an TODO OSPO Ambassador? How would you help the community to thrive?
My extensive involvement with TODO has focused on facilitating knowledge, best practices, and information exchange in open source operations among organizations and projects. The open source operations landscape presents numerous challenges, many of which are shared across the industry, while others are unique to specific organizations or sectors.
During my tenure on the TODO steering committee (2022-2023), I collaborated to establish OSPOlogy and OSPOlogy.live, initiatives aimed at enhancing our community’s capacity to share knowledge about existing projects and engage in discussions around emerging trends and best practices. These initiatives are designed to address the specific needs of various regions, recognizing that every OSPO has its own context and requirements.
The OSPOlogy.live event series builds upon my previous efforts in Germany, where I co-organized events to foster the growth of OSPOs within local companies. Alongside fellow members from established German OSPOs, I provided complimentary talks on critical topics such as launching and scaling an OSPO, open-sourcing code, and creating and consuming Software Bill of Materials (SBOMs). These sessions were particularly valuable for professionals in the German auto industry, where there are open source supply chain challenges that necessitate establishing common open source best practices. Our experience shows that private talks can significantly assist individuals seeking to establish an OSPO by providing them with the external support needed to influence their leadership.
Having recently relocated from Berlin to Amersfoort in the Netherlands, I recognize a gap in open source operations competency among prominent Dutch organizations. As a result, I have resumed offering private talks. During a recent discussion at the Open Source Summit in Vienna with several OSPO peers, we conceptualized developing a 'private talks' framework akin to OSPO.live.
As a TODO ambassador, I aim to strengthen outreach to organizations that are not yet familiar with our community and collaborate with fellow ambassadors to create and develop this "private talk" framework. As a TODO ambassador I would like to focus helping OSPO communities / organizations thrive with open source in the Netherlands, Belgium and Germany as I speak Dutch and German and have good network with these countries.
The text was updated successfully, but these errors were encountered: