All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de
Subject: Re: [ANN / RFC] Regular community calls?
Date: Mon, 13 Jan 2025 13:30:35 -0600	[thread overview]
Message-ID: <20250113193035.GA3476@bill-the-cat> (raw)
In-Reply-To: <CAFLszTjDx3bBwgnvB2v6ow70a4-XS-fR5UHFdFQNn7Fdytba8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

On Mon, Jan 13, 2025 at 12:10:35PM -0700, Simon Glass wrote:
> Hi Tom,
> 
> On Mon, 13 Jan 2025 at 11:34, Tom Rini <trini@konsulko.com> 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.
> 
> So do you mean the first one will be in two weeks (i.e. Tues 28th January
> America/Europe, Wed for Asia?)

Yes, thanks for the clarification.

> Here are the running notes
> <https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a5-o/edit?tab=t.0>
> from the previous series.

Meeting minutes are good, but perhaps we should send them out via email
so they're more accessible.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-01-13 19:30 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 [this message]
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
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=20250113193035.GA3476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=sjg@chromium.org \
    --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.