From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: Contributor meeting notes 19-Jan-21
Date: Wed, 20 Jan 2021 18:25:46 -0500 [thread overview]
Message-ID: <2a4b043a-ba50-8a56-26c1-ad8164576f90@gmail.com> (raw)
In-Reply-To: <b78f81c8-5d67-1fea-8ff2-6673c423da94@samsung.com>
On 1/20/21 6:18 PM, Jaehoon Chung wrote:
> Hi,
>
> On 1/20/21 3:54 AM, Simon Glass wrote:
>> 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
>
> In South Korea, it will be almost am 01:30.
> Frankly, i can't speak English very well..If it doesn't matter, i hope to attend sometime. :)\
One option could be to alternate times. E.g. one meeting pick a time
best for one hemisphere, and another call pick a time best for the
other. For example, the next meeting could be at 4:30 UTC (since we just
met at 16:30 UTC)
--Sean
>
> Best Regards,
> Jaehoon Chung
>
>> - Simon might send out survey
>> - Send invitation to maintainer group - DONE
>> [Simon] New sequence numbers
>> [Heinrich] Online docs
>> - https://protect2.fireeye.com/v1/url?k=93d7f10b-cc4cc86e-93d67a44-000babff32e3-8edc69528000b522&q=1&e=ae252977-3a7b-4c4a-ab06-1c4711467fc0&u=https%3A%2F%2Fu-boot.readthedocs.io%2F
>> - Accept a merge request only with docs included?
>>
>> Next meeting Tuesday 2 Feb.
>>
>> [1] https://protect2.fireeye.com/v1/url?k=030f1752-5c942e37-030e9c1d-000babff32e3-e989b91a6d0ade29&q=1&e=ae252977-3a7b-4c4a-ab06-1c4711467fc0&u=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUgV-hiR88a5-o%2Fedit%23
>>
>> Regards,
>> Simon
>>
>
next prev parent reply other threads:[~2021-01-20 23:25 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
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 [this message]
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=2a4b043a-ba50-8a56-26c1-ad8164576f90@gmail.com \
--to=seanga2@gmail.com \
--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