savannah-register-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #16553] Submission of sox_ng


From: Ineiev
Subject: [task #16553] Submission of sox_ng
Date: Fri, 14 Jun 2024 03:03:06 -0400 (EDT)

Follow-up Comment #3, task #16553 (group administration):

[comment #2 comment #2:]
...
> There may be other ways to achieve this, like making other group members
also admins of the project, but that may be too much. If I can privately give
the keys to its admin mail and site logins to one or two people whose trust
level is high but who may no longer be active SoX developers, that seems a
more reliable way to achieve this.

I don't think it's harder to pass private keys and other credentials to other
people (which isn't an ideal practice, anyway) than to make them admins of the
Savannah group, I would say the opposite.  At the same time, separating
identities definitely has essential advantages.

> INSTALL says that the optional libraries it can use are:
> 
...
> AO                http://xiph.org/ao                    GPL
> FLAC              http://flac.sourceforge.net           BSD

This means that you'll have to check what the real licenses are, and update
INSTALL (or SoX programs if they turn out GPL-incompatible).  For example,
'GPL' may mean GPLv2-only, making it non-compliant with Savannah hosting
requirements.

> and its COPYING file reads:
> ---------------
> SoX source code is distributed under two main licenses. The two
> licenses are in the files LICENSE.GPL and LICENSE.LGPL.

(By the way, GPLv3-only is also incompatible with our requirements.  This
point in SoX licensing needs clarifying.)

> I would appreciate guidance on how we could license a hard fork to comply
with its current situation and best move forward.

I'm afraid I have to repeat that Savannah admins can't afford effectively
becoming part of maintainer team of newly registered packages and keeping them
in the right legal shape.  We have to rely on the existing maintainers.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?16553>

{savane: Include the next line when replying by email.}
{savane: user = savannah-register-public@gnu.org; tracker = task; item = 16553}

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]