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.
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel
