Yesterday, Apr 6th, during the Architecture Committee meeting, we discussed the possibility of having the community use cases meeting split, and I assigned myself the action item to create a doodle and send an email. Well, let me start saying that I may have failed in the doodle thing, but I still am dropping the email with what I heard as a feedback and what I would like to suggest. I got the feedback, from more than one person, that the time for the community use cases meeting is not exactly optimal for everyone, and that is right. For instance, it may be too early for folks in some parts of the US, while it is still too late for folks in Australia. With this in mind, I would like to ask whether there is the interest to split the meeting, allowing then the involved parts to talk to each other in a time that suits them best. So, this message is for everyone, but here I am explicitly looking for feedback from folks interested in: * K8S CI/CD pipeline with kata containers - Here we have people interested from the US and Australia, so maybe a late meeting in the US time zone would benefit the folks in Australia. * Performance isolation - Here we have people interested from the US and China, so maybe a late meeting in the US time zone would benefit the folks in China. If the parts involved in this have the interest to do so, let me know and then I will try to organise a doodle, set an official time, etc, etc, etc. We, as the community facilitating this communication, are here to facilitate the communication in a way that it will be beneficial for all the involved parts. Best Regards, -- Fabiano Fidêncio