All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Virtual/online Buildroot Developers meeting ?
Date: Wed, 15 Jul 2020 21:25:00 +0200	[thread overview]
Message-ID: <87imeo1sz7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200713133634.350b9d23@windsurf.home> (Thomas Petazzoni's message of "Mon, 13 Jul 2020 13:36:34 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Mon, 13 Jul 2020 09:45:43 +0200
 > Arnout Vandecappelle <arnout@mind.be> wrote:

 >> [Yes, I'm still alive :-) ]

 > Awesome, some of us were wondering ! :-)

So am I, sorry about the slow response.


 >> >>  - 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.  
 >> 
 >> I also think it's easier to organise at least one and maybe several days in a
 >> row. For that, you clear your calendar, while if it's just for a couple of hours
 >> you tend not to do the effort.

 > On my side, I agree that doing full days is going to be easier than
 > just a few hours here and there. It also allows to focus on something a
 > bit more complex than what can be done in just 2-3 hours.

Indeed.

 > However, the question is whether we want a few full days spread over
 > time, or grouped together. Or perhaps just have 2 meetings of 2 days
 > each, a few weeks apart ?

I think 1, max 2 days is easiest to plan in. I have some free time late
next week / early the week after, and will be away on holiday from 30/7
to 14/8.

 >> Here are the candidates that I've used and think are suitable (in no particular
 >> order):
 >> 
 >> - jitsi
 >> - zoom
 >> - Google meet
 >> - discord
 >> - whereby

 > If that's needed, Bootlin has its own Jitsi installation, which we can
 > use. We've used it successfully to deliver 4 hours training courses,
 > over several days, and it works fine.

I don't really have any preferences.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2020-07-15 19:25 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
2020-07-13  7:45   ` Arnout Vandecappelle
2020-07-13 11:36     ` Thomas Petazzoni
2020-07-15 19:25       ` Peter Korsgaard [this message]
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=87imeo1sz7.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 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.