From: Tom Rini <trini@konsulko.com>
To: Michal Simek <monstr@monstr.eu>
Cc: u-boot@lists.denx.de
Subject: Re: [ANN / RFC] Regular community calls?
Date: Tue, 14 Jan 2025 10:40:04 -0600 [thread overview]
Message-ID: <20250114164004.GI3476@bill-the-cat> (raw)
In-Reply-To: <31e9cdb8-72a1-401d-bd7b-6be8ef403507@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Tue, Jan 14, 2025 at 03:21:09PM +0100, Michal Simek wrote:
> Hi
>
> On 1/13/25 19:34, Tom Rini wrote:
> > Hey all,
> >
> > It's been suggested again a few times recently that we should try and
> > have some sort of regular open call / video chat as that might help
> > clear up some issues. To that end, I'd like to propose we have the first
> > one at 9am -0600 UTC (3pm +0 UTC) via Google Meet. This will be a day
> > after the v2025.04-rc1 release, and I'll include a link in the release
> > email. If this works out well, we can make it a regular thing for the
> > day after a release and also try rotating the time, or having a second
> > meeting much later in my day that's at a better time for other parts of
> > the world.
>
> +1
> TBH would be the best to send meeting invitation to have a record in a calendar.
I agree in theory, but Google is being a bit of a challenge at making a
public calendar link. I'm trying to avoid doing things that will result
in a higher spam potential. How far in advance would it be good to send
the meeting invite out do you think?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-01-14 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 18:34 [ANN / RFC] Regular community calls? Tom Rini
2025-01-13 19:10 ` Simon Glass
2025-01-13 19:30 ` Tom Rini
2025-01-13 19:38 ` Michael Nazzareno Trimarchi
2025-01-13 19:39 ` Simon Glass
2025-01-13 19:48 ` Tom Rini
2025-01-14 14:21 ` Michal Simek
2025-01-14 16:40 ` Tom Rini [this message]
2025-01-15 5:57 ` Neha Malcom Francis
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=20250114164004.GI3476@bill-the-cat \
--to=trini@konsulko.com \
--cc=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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.