Re: SoX upstream maintenance

[Claude Warren <claude@xenei.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2991 bytes --]

I am still listening.  I submitted a patch long ago.  Never heard back.


On Wed 22 May 2024, 16:38 Jan Stary, <hans@stare.cz> wrote:

> > >> In general, though, sox's SF issue tracker seems to be ineffective,
> which
> > >> both impacts the quality and functionality of sox, but also
> discourages
> > >> well-intentioned people from contributing to it, as they start out
> > >> enthusiastic, follow what seem like the right steps, and then are
> ignored
> > >> for decades. I am one example of that. I've added log frequency axis
> to
> > >> sndfile-tools' sndfile-spectrogram and would have done the same for
> sox but
> > >> it seemed pointless after the FFTW patches being ignored for so long,
> making
> > >> me have to update them to stride code changes, until I eventually
> gave the
> > >> idea up as wasted work.
> > >>
> > >> There are contributions with patches from 2006, which may or may not
> be
> > >> useful these days. There are patch suggestions that give links to
> github
> > >> repos that have long since been deleted, but the pointless issue
> persists on
> > >> SF.
> > >>
> > >> This gives the public impression to developers is that it is
> abandonware or
> > >> only-us-not-you-ware.
> > >>
> > >> Could the project use some help, as I've been programming since I was
> 13 and
> > >> am now 60 and on a pension so I can choose what I work on, and
> resolving the
> > >> sox SF issues seems worth doing as it is an excellent tool that seems
> > >> neglected in that area.
>
> > > Yes. There has been a void in actual maintainership for a long time.
> > > Is anyone sure what the upstream actualy is? The downstream ports
> > > I care to follow either start at 14.4.2 and stack up their own patches
> > > (including random diffs floating around, or one of the github forks),
> > > or just gave up and chose one github repo or another.
> > >
> > > Is there anyone on this list who considers thamselves to be
> > > a "maintainer" of SoX? Or at least someone who even has the
> > > commit rights to sox.sf.net (the repo, the bugtracker)?
> > > Does anyone of the current users remember what SourceForge was?
> >
> > I have admin access to the SF project.
>
> Do you consider that to be the ultimate upstream of SoX code?
> If so, what is the relation of the SF git master to
> https://github.com/mansr/sox/commits/master/ ?
>
> > Unfortunately, I haven't been
> > able to spend much time on maintenance tasks recently.
>
> sox.sf.net says "Brought to you by: cbagwell, mansr, robs, uklauer"
>
> https://sourceforge.net/u/mansr/activity
> https://sourceforge.net/u/robs/activity
> https://sourceforge.net/u/uklauer/activity
> https://sourceforge.net/u/cbagwell/activity
>
> Is there anyone on these lists
> (cross-posting to both -devel and -users)
> willing to step up and maintain SoX?
>
> Jan
>
>
>
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel
>

[-- Attachment #1.2: Type: text/html, Size: 4609 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