-
Notifications
You must be signed in to change notification settings - Fork 47
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
[OSPO Associate] Request - CURIOSS #226
Comments
Thank you @claredillon and CURIOSS, for your interest in becoming a TODO Associate! Your submission has been shared with our Steering Committee for review 🙂 Please allow up to 5-10 business days for the Steering Committee to review cast their vote |
@claredillon the vote poll fro SC members has been created in the TODO governance repo and you can follow the progress here: todogroup/governance#370 |
congrats! the vote passed and we can start the onboarding process to welcome CURIOSS as the newest TODO OSPO Associates! On behalf of TODO, we are excited to keep working with the CURIOSS community. Please allow 2-3 business days for us to add CURIOSS to the landscape and draft a blog announcement for you to review and introduce CURIOSS to the TODO community. |
Thanks for your patience @claredillon ! We have successfully merged the addition of CURIOSS as new associate in the TODO landscape and changes will be visible in the web app in less than 24h #229 What is missing?
|
TODO OSPO Associate Request
This is an issue created to request to become an OSPO Associate. If your organization is interested to apply, please make sure you have (1) read the OSPO Associate Program documentation
and (2) fulfil the requirements from the Pre-submission checklist.
Pre-submission checklist:
Contact Information
CURIOSS
REQUIRED: Benefits for the OSPO Ecosystem
CURIOSS is a community for those that work in university and research institute OSPOs
What do you expect from TODO Group as an OSPO Associate?
Where and how could TODO Group help your organization and community?
The text was updated successfully, but these errors were encountered: