From: "Måns Rullgård" <firstname.lastname@example.org>
Subject: Re: upstream
Date: Mon, 19 Mar 2018 11:41:21 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <20180318205049.GA7155@www.stare.cz> (Jan Stary's message of "Sun, 18 Mar 2018 21:50:49 +0100")
Jan Stary <firstname.lastname@example.org> writes:
> On Mar 18 14:56:31, email@example.com wrote:
>> > what is the upstream of SoX nowadays?
>> > I use git://git.code.sf.net/p/sox/code
>> > which had its last commit three years ago.
>> > https://sourceforge.net/projects/sox/ says
>> > Brought to you by: cbagwell, robs, uklauer
>> > https://sourceforge.net/u/cbagwell/profile/
>> > https://sourceforge.net/u/robs/profile/
>> > https://sourceforge.net/u/uklauer/profile/
>> > Is any of you guys around here, and still active in maintaining SoX?
>> > My impression is that Mans and Pascal are mostly the maintainers now
>> > - do you have commit rights to toe SF repo?
>> I have no rights to the SF repo.
> Do you know somebody who does?
The people you listed above, all of them missing.
>> > Is that the right repo?
>> Define right.
> I probably mean the one which will spawn the next release.
If the old maintainers don't come back, we'll have to create a new home
for the project before thinking about releases.
>> > What is the right place to send PRs?
>> > Is there a point opening tickets on SF?
>> Probably not. If you open issues on my github repo, I'll at least see
>> them. Maybe I'll even fix them.
> The oldest ones in the SF issue tracker are from 2006.
> Was there any effort since https://sourceforge.net/projects/sox/
> was abondoned to go through them?
Not by me.
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
SoX-devel mailing list
next prev parent reply other threads:[~2018-03-19 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 14:40 upstream Jan Stary
2018-03-18 14:56 ` upstream Måns Rullgård
2018-03-18 19:41 ` upstream Eric Wong
2018-03-19 11:31 ` upstream Måns Rullgård
2018-03-18 20:50 ` upstream Jan Stary
2018-03-18 22:05 ` upstream Eric Wong
2018-03-19 20:19 ` upstream Rob Sykes via SoX-devel
2018-04-25 8:03 ` upstream Eric Wong
2018-04-25 9:55 ` upstream Måns Rullgård
2018-04-26 10:27 ` upstream Rob Sykes via SoX-devel
2018-03-19 11:41 ` Måns Rullgård [this message]
2018-03-22 2:21 ` upstream Jan Stary
2018-03-22 16:37 ` upstream Sonny Ray
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:
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 \
* 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
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).