From: jbranso@dismail.de
To: "Yasuaki Kudo" <yasu@yasuaki.com>
Cc: "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Video Conference
Date: Sat, 02 Apr 2022 18:34:34 +0000 [thread overview]
Message-ID: <59d6e5f9227d9c9d9a455e62215d8382@dismail.de> (raw)
In-Reply-To: <A7A25EEA-E8FD-4B91-82A5-BFDCB2DCEDA2@yasuaki.com>
April 2, 2022 12:26 AM, "Yasuaki Kudo" <yasu@yasuaki.com> wrote:
> Hi,
>
> 2 years ago, I joined meet.coop , a video conference service cooperative and explored the business
> potential in Japan.
>
> The coop hosted BBB but the gap I discovered was that the potential customers in Japan would not be
> interested unless the service is customized to their exact needs - otherwise they preferred Zoom
> and Google meet.
>
> So ability to to take the video conference service into minimalist components and then reassembling
> is very important 😄
>
Sounds like a worthwhile project. You can always reach out to the BBB or jitsi developers
and see what they think of your proposal.
> -Yasu
>
>> On Apr 2, 2022, at 03:59, jbranso@dismail.de wrote:
>>
>> March 31, 2022 7:53 PM, "Yasuaki Kudo" <yasu@yasuaki.com> wrote:
>>
>>> Hello,
>>>
>>> From time to time, I think about audio/video mixer (.i.e. video conference software like BBB or
>>> Jitsi) , with the intension of making it highly modular that it can be freely remixed and
>>> reinvented by volunteer participants.
>>>
>>> Is anyone interested? Or is can you think about something that already exists?
>>
>> Your proposal sounds a little vague. What are you hoping to accomplish that BBB or Jitsi
>> does not already do?
>>
>>> Cheers,
>>> Yasu
next prev parent reply other threads:[~2022-04-02 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 23:52 Video Conference Yasuaki Kudo
2022-04-01 18:59 ` jbranso
2022-04-02 4:26 ` Yasuaki Kudo
2022-04-02 18:34 ` jbranso [this message]
2022-04-03 21:14 ` Yasuaki Kudo
2022-04-03 21:46 ` Yasuaki Kudo
2022-04-04 2:58 ` Maxim Cournoyer
2022-04-05 11:58 ` Yasuaki Kudo
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=59d6e5f9227d9c9d9a455e62215d8382@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=yasu@yasuaki.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.