Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Virtual/online Buildroot Developers meeting ?
Date: Sat, 11 Jul 2020 18:56:01 +0200	[thread overview]
Message-ID: <20200711165601.GA15448@scaer> (raw)
In-Reply-To: <20200711165315.0c2b5079@windsurf.home>

Thomas, All,

On 2020-07-11 16:53 +0200, Thomas Petazzoni spake thusly:
> We had our last Buildroot Developers Meeting in February, but it is now
> becoming pretty clear that the next physical Buildroot Developers
> Meeting is not going to happen in the near future. The traditional
> "Buildroot summer camp" organized by the core maintainers/developers is
> not going to happen this year. And the Buildroot Developers Meeting
> that traditionally takes place before ELC-E will not happen either, as
> ELC-E 2020 will be a virtual event.

Yes, this whole situation is sad.

> The issue I see with this is that those meetings have always been very
> useful in making progress through the backlog of patches, especially by
> having discussions on some of complex topics and taking decisions.
> 
> As all those physical things (work, conferences, meetings) are now
> replaced by virtual/online ones, I'm wondering if we should do the same
> for the Buildroot Developers Meeting.
> 
> Questions are:
>  - Who would be interested ?

I would.

>  - What format should it take ? One full day once in a while ? Just a
>    few hours here and there ? Multiple days in a row ?

My preference would be to block two or more days in a row. Sun-Mon ro
Sun-Tue would be ideal for me, but I can adapt.

>  - What technical solution do we use ? Is it just about agreeing to all
>    be on IRC at the same time ? Or do we need a video conferencing
>    solution ? Most of our meetings are multiple side discussions taking
>    place at the same time, which doesn't really map well with a single
>    video conference.

This is indeed very tricky. We will probably have to adapt depending on
how many of us are attending.

Also, maybe just audio would be enough (I find video to not be that
interesting in the end, when all we need is discussion).

However, a way to share one's desktop (or an application) would be most
important. A white board too, maybe...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-07-11 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 14:53 [Buildroot] Virtual/online Buildroot Developers meeting ? Thomas Petazzoni
2020-07-11 16:56 ` Yann E. MORIN [this message]
2020-07-13  7:45   ` Arnout Vandecappelle
2020-07-13 11:36     ` Thomas Petazzoni
2020-07-15 19:25       ` Peter Korsgaard
2020-07-17 13:19         ` Matthew Weber

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=20200711165601.GA15448@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox