[kata-dev] Community use cases meeting

Christophe de Dinechin cdupontd at redhat.com
Tue Apr 20 09:29:45 UTC 2021 


> On 20 Apr 2021, at 11:26, Christophe de Dinechin <cdupontd at redhat.com> wrote:
> 
> 
> 
>> On 19 Apr 2021, at 19:12, Ariel Adam <aadam at redhat.com <mailto:aadam at redhat.com>> wrote:
>> 
>> 
>> 
>> On Mon, Apr 19, 2021 at 2:25 PM James Magowan <MAGOWAN at uk.ibm.com <mailto:MAGOWAN at uk.ibm.com>> wrote:
>> Hi Ariel/Samuel, 
>> 
>> Moving Confidential computing Use Case meeting is fine for me. 
>> 
>> Given recent fun with summer savings time and the dates/times in the thread. 
>> 
>> Can we clarify that meetings will be? 
>> every 2 weeks at 12:00 UTC 
>> https://zoom.us/j/98038141932 <https://zoom.us/j/98038141932> 
>> next meetings Thursday 29th April, Thursday 13th May etc. 
>> 
>> 
>> I've moved the meeting 1 week forward to April the 29th and verified that the only invitee is kata-dev mailing list. 
> 
> I still don't see it. So the use of kata-dev may be the problem.
> 
> Do we know for a fact that Google Calendar correctly works with mailing lists?

Actually, I believe that I understand the problem better now.

The issue is that since the invitee is kata-dev, Google does not know how to associate it with my account.

So you need to explicitly look for the calendar invite email, find the ICS file attached to it, open that, manually insert in your calendar, and manually delete the earlier invitation, because the process above cuts the link between what is on your calendar and the original invite. In other words, an update does not update what is on your calendar.

HTH.

> 
>> 
>> The meeting will be at 12:00 UTC and happen every 2 weeks.
>> I will also make sure to send a reminder a day before the meeting (every 2 weeks).
>> 
>> Lastly, I'm reminding everyone that this time slot is mainly for the confidential computing use case and the CI/CD and performance use cases will be discussed at other times. 
>> 
>> Thanks. 
>>  
>> 
>> Thanks, 
>> 
>> James
>> Mobile: 44-7808-247946 | Phone: 44-1962-817235
>> E-mail: MAGOWAN at uk.ibm.com <mailto:MAGOWAN at uk.ibm.com>	
>> Hursley Park
>> Hursley, Hampshire SO212JN
>> United Kingdom
>> IBM United Kingdom Limited
>> Registered in England and Wales with number 741598
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
>> 
>> 
>> 
>> 
>> From:        Ariel Adam <aadam at redhat.com <mailto:aadam at redhat.com>> 
>> To:        Samuel Ortiz <sameo at linux.intel.com <mailto:sameo at linux.intel.com>>, Eric Ernst <eric.g.ernst at gmail.com <mailto:eric.g.ernst at gmail.com>>, Peng Tao <bergwolf at antfin.com <mailto:bergwolf at antfin.com>>, kata-dev <kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>> 
>> Date:        18/04/2021 18:42 
>> Subject:        [EXTERNAL] Re: [kata-dev] Community use cases meeting 
>> 
>> 
>> 
>> Since you're leading the confidential computing use case which we agreed Thursday's time slot would be used for then to me that makes sense. 
>> 
>> Does anyone object to moving the meeting by 1 week (as usual every 2 weeks from there)? 
>> 
>> Also, a few people pointed out that they don't see the meeting or still see it every 2 weeks instead of 1 week. We basically sent an invite to the kata-dev for every 2 weeks so if anyone has a better idea on how to do that please let us know :-). 
>> 
>> Thanks.  
>> 
>> On Sun, Apr 18, 2021 at 8:32 PM Samuel Ortiz <sameo at linux.intel.com <mailto:sameo at linux.intel.com>> wrote:
>> Ariel,
>> 
>> Next week's meeting (04/21), I will be out of the office and won't be
>> able to attend the meeting. Would anyone object if we shift that one to
>> 04/28 instead ?
>> 
>> Cheers,
>> Samuel.
>> 
>> On Wed, Apr 14, 2021 at 01:27:54PM +0300, Ariel Adam wrote:
>> > Hi everyone.
>> > Going back to this mail thread.
>> > Talking with Samuel it will be hard for him to move the time slot for the
>> > confidential computing use case (currently on Thursday every 2 weeks 8AM
>> > EST).
>> > 
>> > What we suggest is the following:
>> > 
>> >    - *Confidential computing* - will keep the current timeslot, please ping
>> >    Samuel directly if you would like to attend and this is a problem for you
>> >    - *CI/CD use case* - in practice it's only RH and IBM cloud thus we will
>> >    work mainly through mails (and ping me if you are also interested in this)
>> >    - *Performance isolation* - Tao will work on a different time slot to
>> >    fit people who would like to attend as well (such as Eric)
>> > 
>> > As pointed, we will ask to provide a status on the use cases progress
>> > during the AC meetings if time permits.
>> > 
>> > Comments are welcomed.
>> > 
>> > Thanks.
>> > 
>> > 
>> > On Wed, Apr 7, 2021 at 5:08 PM Eric Ernst <eric.g.ernst at gmail.com <mailto:eric.g.ernst at gmail.com>> wrote:
>> > 
>> > > Makes sense to me, and I appreciate the change!
>> > >
>> > > Eric
>> > >
>> > > On Apr 7, 2021, at 6:26 AM, Ariel Adam <aadam at redhat.com <mailto:aadam at redhat.com>> wrote:
>> > >
>> > > 
>> > > Given that Tao agrees this makes sense I checked with Samuel as well.
>> > >
>> > > What we suggest is that each use case leads (Ariel, Samuel, Tao) will send
>> > > a separate doodle poll for their use case.
>> > > That way each of the use case teams can decide on a time that fits the
>> > > majority of participants and also on the cadence of the meetings (every 1
>> > > or 2 weeks).
>> > >
>> > > We will also propose to give a short update on the progress of the
>> > > different use cases on the weekly AC meeting (if time permits).
>> > >
>> > > Let us know if anyone has any objections before we send out the doodle
>> > > polls.
>> > >
>> > > Thanks.
>> > >
>> > >
>> > > On Wed, Apr 7, 2021 at 3:03 PM Peng Tao via kata-dev <
>> > > kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>> wrote:
>> > >
>> > >> Thanks for bringing it to the list Fabiano! I am interested in the
>> > >> performance isolation use case and would love to see US folks present
>> > >> their thoughts and ideas too. So I am all for it to split the use case
>> > >> meeting and relocate to a time that works better for US folks.
>> > >>
>> > >> Cheers,
>> > >> Tao
>> > >>
>> > >> On 2021/4/7 16:26, Fabiano Fidêncio wrote:
>> > >> > 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,
>> > >> >
>> > >>
>> > >> --
>> > >> Into something rich and strange.
>> > >>
>> > >> _______________________________________________
>> > >> kata-dev mailing list
>> > >> kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>
>> > >> http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev>
>> > >>
>> > > _______________________________________________
>> > > kata-dev mailing list
>> > > kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>
>> > > http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev>
>> > >
>> > >
>> 
>> > _______________________________________________
>> > kata-dev mailing list
>> > kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>
>> > http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev>
>> _______________________________________________
>> kata-dev mailing list
>> kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>
>> http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev> 
>> 
>> 
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number 741598. 
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>> _______________________________________________
>> kata-dev mailing list
>> kata-dev at lists.katacontainers.io <mailto:kata-dev at lists.katacontainers.io>
>> http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katacontainers.io/pipermail/kata-dev/attachments/20210420/de48e329/attachment-0001.html>

More information about the kata-dev mailing list