unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: jbranso@dismail.de
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Video Conference
Date: Sat, 2 Apr 2022 13:26:25 +0900	[thread overview]
Message-ID: <A7A25EEA-E8FD-4B91-82A5-BFDCB2DCEDA2@yasuaki.com> (raw)
In-Reply-To: <278c66f3a3e4b2940e150363a63a79c1@dismail.de>

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 😄

-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


  reply	other threads:[~2022-04-02  4:26 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 [this message]
2022-04-02 18:34   ` jbranso
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A7A25EEA-E8FD-4B91-82A5-BFDCB2DCEDA2@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@dismail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).