cti-tac.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kelling <iank@fsf.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Re: Hashing out the scope of work
Date: Thu, 25 Apr 2024 16:06:57 -0400	[thread overview]
Message-ID: <87ttjpurtr.fsf@fsf.org> (raw)
In-Reply-To: <20240424-funny-lemon-starling-8b1aae@lemur>


Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> On Wed, Apr 24, 2024 at 05:15:33PM -0400, Ian Kelling wrote:
>> > 7. Video conferencing (BigBlueButton)
>> >
>> >   a. LF will provide video conferencing to the project using [BigBlueButton][9]
>> >      (BBB), either with a 3rd-party provider or as a fully self-hosted service.
>> >   b. LF will work with the glibc project to set up conference rooms and access
>> >      as required.
>> 
>> Regarding BBB:
>> 
>> Looks like you forgot to include the [9] link.
>> 
>> BBB versions of the last few years have a dependency on nonfree MongoDB
>> versions. I think the LF BBB that CTI has been using is running nonfree
>> MongoDB. The upstream BBB developers announced they are removing
>> MongoDB, but that work does not have a set timeline, I hope it will be
>> done within a year. At FSF, we are migrating to Galène,
>> https://galene.org/ , which has less features but also takes less
>> resources and is much less sysadmin work.
>
> Okay, thank you for bringing that up. Another video conferencing system 
> which we've previously deployed is Jitsi. Are there any similar 
> objections to that platform?
>
> -K

Jitsi should be ok. At FSF, we've had some occasional usability problems
with Jitsi, but no software freedom problems.

But note, this was not an objection, it was pointing out a fundamental
defect that got overlooked.

Consider who's responsibility is it to check the freedom status of
software deployed by LF IT for CTI.

A promise to use free software is one thing, actually living up to it
needs some procedures, procedures that failed or that you don't have in
place.

-- 
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7  DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org

  reply	other threads:[~2024-04-25 20:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 16:45 Hashing out the scope of work Konstantin Ryabitsev
2024-04-24 21:15 ` Ian Kelling
2024-04-25  1:31   ` Konstantin Ryabitsev
2024-04-25 20:06     ` Ian Kelling [this message]
2024-04-26 16:06       ` Siddhesh Poyarekar
2024-05-13 17:28       ` Carlos O'Donell
2024-04-29 14:09 ` Joseph Myers
2024-04-29 15:23   ` Konstantin Ryabitsev
2024-04-29 16:35     ` Joseph Myers
2024-04-29 18:52       ` Siddhesh Poyarekar
2024-04-29 20:47         ` Joseph Myers
2024-04-29 21:01           ` Konstantin Ryabitsev
2024-04-29 21:58             ` Joseph Myers
2024-04-30 12:30               ` Konstantin Ryabitsev
2024-04-30 12:41                 ` Siddhesh Poyarekar
2024-05-02 19:27                 ` Joseph Myers
2024-05-07 20:36                   ` Konstantin Ryabitsev
2024-05-07 21:45                     ` Joseph Myers
2024-05-13 16:31 ` Carlos O'Donell
2024-05-17 21:22 ` Carlos O'Donell

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=87ttjpurtr.fsf@fsf.org \
    --to=iank@fsf.org \
    --cc=cti-tac@lists.linuxfoundation.org \
    --cc=konstantin@linuxfoundation.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 NNTP newsgroup(s).