From: Alex Sadovsky <nable.maininbox@googlemail.com>
To: u-boot@lists.denx.de
Subject: Contributor meeting notes 19-Jan-21
Date: Wed, 20 Jan 2021 03:25:57 +0300 [thread overview]
Message-ID: <456f84c9-8bf2-774a-ef13-636718ee8a47@googlemail.com> (raw)
In-Reply-To: <CAPnjgZ20QWOTaRC+qt1UPzVk5pMf7LMH3qAqGVOize9YmoFJbA@mail.gmail.com>
Hi Simon,
I think I should add my $0.02 here.
> 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,
Jitsi is a free and lightweight solution: it's free/open-source and there's also a free public server (more than one, strictly speaking: 1 official cluster + several 3rd party public servers).
It doesn't require installing anything (just a web browser), it doesn't require registration (although anyone can use self-hosted instance and configure access control lists as they wish), it doesn't limit meeting duration. As far as I know, it's also not blocked in China (while most commercial solutions are blocked for years, google products are among them, although they're popular and VPN helps sometimes), this is beneficial too.
I wanted to suggest Jitsi during previous discussion as I'm using it for several years and it does its job pretty well (just one job, though: no built-in file sharing, no fancy chat formatting, just audio+video meetings and plain-text chat).
It's quite sad for me to see so many people prefering that proprietary Z**m thing and struggling with its limitations last year while there are mostly better free products that are enough for most use-cases but just didn't get enough attention.
Cheers,
Alex
next prev parent reply other threads:[~2021-01-20 0: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 [this message]
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
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=456f84c9-8bf2-774a-ef13-636718ee8a47@googlemail.com \
--to=nable.maininbox@googlemail.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