-
Notifications
You must be signed in to change notification settings - Fork 32
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
CNCF TAG-Runtime Discussion/Presentation #950
Comments
Hi Nikhita, very happy to do this (+ @miao0miao @t-lo)! However, I'll be traveling on Feb 2. We can schedule for the next meeting (Feb 16) if you are OK to squeeze two project updates into one meeting, otherwise Mar 2 would work too. Let us know! |
@ahrkrak great to hear! We typically don't do two projects in one meeting because each project usually ends up taking an hour. We can also do a meeting on Feb 9th, but if you prefer March 2nd, that would work too. Let us know what you prefer! |
@ahrkrak 👋 Hi Andrew, just wanted to follow up to check if you'd like to present on Feb 9th or March 2nd. |
Hi Nikhita, sorry I didn't see the note, I had github notifications off... |
@t-lo that sounds rough, hope you feel better soon! 🙏 |
Thanks @nikhita for the invitation. I updated the meeting notes with a link to the slides. |
Hi Flatcar maintainers,
I'm part of CNCF TAG Runtime. I think it would be great for you to present/discuss Flatcar at one of our meetings, especially also since you've applied for Incubation (cncf/toc#991).
For example, it would be great to learn things like the roadmap, tech, community and the general overview of the project. The last time Flatcar was presented in TAG Runtime was in September 2020. It would also be good to know how the project has changed since then.
Let me know if this is something you'd be interested in doing. Additionally, would 2nd February work for you to present this?
If yes, please feel free to add it to our agenda or reach out to us in the #tag-runtime channel on the CNCF slack.
Thanks!
cc @raravena80
The text was updated successfully, but these errors were encountered: