From: Martin Guy <martinwguy@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Offering to step up as new SoX maintainer
Date: Tue, 4 Jun 2024 13:21:16 +0200 [thread overview]
Message-ID: <38f0bb7c-ed17-4049-833e-be4db65e7553@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1521 bytes --]
I am willing to step up as the new maintainer of SoX, to:
- make a new release of SoX, 14.4.3, including fixes to all known
bugs(*) and spelling errors but no more
- after that, open the flood gates to new developments and features
towards a non-backwards-compatible release 15.0.0
If this cannot be done on sox.sf.net, I will make a hard fork, sox_ng,
and invite contributers to work on that instead. I already have most of
the pieces in place for this and would just need to make it public.
On a personal note, I have only made one proper release of a open-source
project so far, at start of year, and it took me three months, so I can
understand the current maintainer(s) being shy of doing it. It is a lot
of boring work. That one took so long because I also had to learn
autotools and fix all user-visible bugs instead of fiddling with it and
starting new features and improvements. This one should be easier
because "configure" is done, the roadmap for the first release is clear
and I can count on community help for the bugs.
That said, the fork would be on codebase.org which is a much more modern
platform than sourceforge and it can coexist peacefully with sox proper
(installing sox_ng.h, libsox_ng.so, play_ng etc) so packagers, if they
decide to switch, can make symlinks from the old names to the new and
things should work as before.
Suggestions are welcome
M
(*) There are 28 CVEs open against sox-14.4.2, not the 18 that Debian
has patches for.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next reply other threads:[~2024-06-04 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 11:21 Martin Guy [this message]
2024-06-04 16:03 ` Offering to step up as new SoX maintainer Jan Stary
2024-06-04 16:38 ` Jan Stary
2024-06-04 22:53 ` Eric Wong
2024-06-05 10:29 ` Martin Guy
2024-06-05 20:55 ` Jan Stary
2024-06-06 10:29 ` Martin Guy
2024-06-06 11:10 ` Jan Stary
[not found] ` <d0c3c795-95df-4143-bbfb-5f1a06d63d43@gmail.com>
2024-06-06 12:06 ` Jan Stary
2024-06-06 17:18 ` Martin Guy
2024-06-05 4:54 ` Rob Sykes via SoX-devel
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38f0bb7c-ed17-4049-833e-be4db65e7553@gmail.com \
--to=sox-devel@lists.sourceforge.net \
/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://80x24.org/mirrors/sox.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).