From: SeongJae Park <sj@kernel.org>
To: damon@lists.linux.dev
Cc: SeongJae Park <sj@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: DAMON Beer/Coffee/Tea chat reminder for the week of 2025-05-12
Date: Fri, 9 May 2025 17:27:46 -0700 [thread overview]
Message-ID: <20250510002746.58427-1-sj@kernel.org> (raw)
Hello,
This is yet another reminder of upcoming DAMON Beer/Coffee/Tea chats
(https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing)
for the week of 2025-05-12.
We will have the two meetings in the week as usual.
I'm also considering merging any-topic and dedicated-topic discussions since
apparently people prefer dedicated topic discussions. For any-topic, I'm
thinking about creating a Slack-like casual messaging systems. Nothing has
decided so far. I'm just thinking about options. Please let me know if you
have any concerns or suggestions for that.
Any-topic discussions
---------------------
Next three time slots for any topic (no reservation is required) are scheduled
as below:
- 2025-05-12 (Mon) 18:00 PT (https://meet.google.com/ndx-evoc-gbu)
- 2025-05-28 (Wed) 09:30 PT (https://meet.google.com/ndx-evoc-gbu)
- 2025-06-09 (Mon) 18:00 PT (https://meet.google.com/ndx-evoc-gbu)
Dedicated-topic discussions
---------------------------
Next three time slots that I reserved in advance for possible future dedicated
topic discussions are as below.
- 2025-05-14 (Wed) 09:30 PT (not yet reserved)
- 2025-05-26 (Mon) 18:00 PT (not yet reserved)
- 2025-06-11 (Wed) 09:30 PT (not yet reserved)
Please reach out to me (sj@kernel.org or whatever) to reserve the
not-yet-reserved time slots for your topics. The reservation is made in a
First-Come First-Served way, and I will send a Google Meet link to
reservation-confirmed attendees.
Please note that other time slots are also available on demands.
Shared Calendar
---------------
You can get the schedule via this shared Google Calendar:
https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
You can also get the past and upcoming schedules via
https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing
Thanks,
SJ
next reply other threads:[~2025-05-10 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 0:27 SeongJae Park [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-23 22:52 DAMON Beer/Coffee/Tea chat reminder for the week of 2025-05-12 SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250510002746.58427-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.