From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29590] set up BBB instances
Date: Tue, 27 Sep 2022 11:39:09 +0000 [thread overview]
Message-ID: <bug-29590-14326-z0df0PCqC0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29590-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29590
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
There is a discussion on overseers here:
https://inbox.sourceware.org/overseers/YzDegpFE4ZGFRWdP@wildebeest.org/T/
One suggestion was to just have some way to do voice communications using a
mumble server. This is easy to setup with current resources, but might not
cover all requirements.
The use case would be for a monthly developer chat or a weekly patch review
session of a project.
I think the minimal requirements are:
- Be able to join voice only (see others, don't be seen)
- Screen sharing
(although an alternative might be to have a separate website/etherpad/etc)
- One or two simultanious sessions of 6 till 12 participants
(with often just up to 4 using video at the same time)
Nice to have:
- phone dial-in
- be able to scale up to conference size
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-09-27 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 21:07 [Bug Infrastructure/29590] New: " ezannoni at gmail dot com
2022-09-27 11:39 ` mark at klomp dot org [this message]
2023-08-15 22:00 ` [Bug Infrastructure/29590] " mark at klomp dot org
2023-10-14 1:00 ` fche at redhat dot com
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=bug-29590-14326-z0df0PCqC0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).