From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: Contributor meeting notes 19-Jan-21
Date: Thu, 21 Jan 2021 09:14:24 +0100 [thread overview]
Message-ID: <e955ef8a-98da-08e2-1335-e23bfb1eb270@denx.de> (raw)
In-Reply-To: <2da0eb4e-e92e-23d4-3ffa-7b1ac9f4ccc7@denx.de>
Hi Simon, Tom,
On 20.01.21 16:05, Marek Vasut wrote:
> On 1/20/21 12:44 AM, Simon Glass wrote:
>> Hi Marek,
>
> Hi,
>
> [...]
>
>>> On 1/19/21 7:54 PM, Simon Glass wrote:
>>>> Hi,
>>>
>>> Hi,
>>>
>>>> Thank you for attending!
>>>>
>>>> Full notes at [1]
>>>>
>>>> Tuesday 19 January 2021
>>>>
>>>> Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean
>>>> Anderson, Simon Glass, Walter Lozano
>>>>
>>>> Notes:
>>>> [all] Introductions
>>>> [all] Timing of call
>>>> - Current time is the best across US, Europe, India. But not any good
>>>> for East Asia
>>>> - Simon might send out survey
>>>> - Send invitation to maintainer group - DONE
>>>> [Simon] New sequence numbers
>>>> [Heinrich] Online docs
>>>> - https://u-boot.readthedocs.io/
>>>> - Accept a merge request only with docs included?
>>>>
>>>> Next meeting Tuesday 2 Feb.
>>>>
>>>> [1]
>>>> https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a5-o/edit#
>>>>
>>>
>>> - Can we use e.g. jitsi meet next time , or even better IRC ?
>>
>> We already IRC a lot. This is partly about getting to know each other.
>>
>> What is the benefit of jitsi? I believe I am permitted to use it,
>
> It seems Alex covered this part already pretty well.
>
Indeed - DENX has already set a server with Jitsi for videoconference,
and we are actively using to communicate with customers. DENX can offer
to host the meeting for U-Boot (Wolfgang has already agreed) - we have
all advantages reported by Marek and Alex. Simon, Tom: is it this
suitable for you ? We can switch to Jitsi since next meeting.
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2021-01-21 8:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210119185647epcas1p28c1e9198cc00381af05c0e205ce8077b@epcas1p2.samsung.com>
2021-01-19 18:54 ` Contributor meeting notes 19-Jan-21 Simon Glass
2021-01-19 20:27 ` Marek Vasut
2021-01-19 23:44 ` Simon Glass
2021-01-20 0:25 ` Alex Sadovsky
2021-01-20 15:05 ` Marek Vasut
2021-01-21 8:14 ` Stefano Babic [this message]
2021-01-27 21:31 ` Simon Glass
2021-01-28 9:24 ` Stefano Babic
2021-02-09 4:29 ` Simon Glass
2021-01-27 21:31 ` Simon Glass
2021-01-20 1:55 ` Bin Meng
2021-01-21 10:41 ` Heinrich Schuchardt
2021-01-21 10:48 ` Michal Simek
2021-01-20 7:46 ` Michal Simek
2021-01-20 15:44 ` Simon Glass
2021-01-20 15:50 ` Michal Simek
2021-01-21 4:11 ` Simon Glass
2021-01-21 8:09 ` Michal Simek
2021-01-26 5:14 ` Heiko Schocher
2021-01-20 10:08 ` Igor Opaniuk
2021-01-20 10:12 ` Michal Simek
2021-01-20 10:19 ` Lukasz Majewski
2021-01-20 23:18 ` Jaehoon Chung
2021-01-20 23:25 ` Sean Anderson
2021-01-21 3:26 ` Simon Glass
2021-01-21 4:09 ` Jaehoon Chung
2021-01-21 8:05 ` Michal Simek
2021-01-21 9:13 ` Jaehoon Chung
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=e955ef8a-98da-08e2-1335-e23bfb1eb270@denx.de \
--to=sbabic@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox