From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"
Date: Tue, 24 Jun 2025 14:09:40 -1000
Message-ID: <20250624140940.00000a53@hawaiiantel.net> (raw)
In-Reply-To: <mailman.4203.1750753363.1384.ffmpeg-devel@ffmpeg.org>
On Tue, 24 Jun 2025 10:22:26 +0200, Kieran Kunhya via ffmpeg-devel
wrote:
> On Tue, 24 Jun 2025, 09:28 compn, <ff@hawaiiantel.net> wrote:
>
> > On Tue, 24 Jun 2025 07:48:30 +0100, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > On Tue, 24 Jun 2025, 07:00 compn, <ff@hawaiiantel.net> wrote:
> > >
> > > > On Mon, 23 Jun 2025 21:20:56 +0100, Derek Buitenhuis wrote:
> > > >
> > > > > This was pushed with outstanding reservations, with no positive
> > > > > affirmation or review from any other devs, and without a push noticed
> > > > > to say it was going to be pushed.
> > > > >
> > > > > Further, the wallet is controlled by a single individual, and not
> > > > > FFmpeg.
> > > >
> > > > ffmpeg is not an organization nor registered group. it cannot own
> > > > anything because it is not a legal entity.
> > > >
> > > > much like everything in the project, parts of ffmpeg are owned by
> > > > individual developers.
> > > >
> > > > -compn
> > > >
> > >
> > > You know perfectly well this wallet could be converted to USD and sent to
> > > SPI but is being held as bitcoin purely out of ideological beliefs.
> > >
> > > Kieran
> > >
> > > >
> >
> > I recommend anyone looking to do this to consult with an attorney, an
> > accountant, and review all local and international laws and treaties, as
> > well as the SPI ToS. It is not as easy as you say.
> >
> > -compn
> >
>
> None of what you wrote justified one person doing this unilaterally.
>
> It's interesting that Michael claims this wallet is owned by the community
> but won't be upfront about who owns avcodec.org.
ffmpeg admins have used the avcodec domain since 2011 due to historical
reasons. fabrice still owns the ffmpeg domain, all these 23 years
later. literal ffmpeg.org is not owned by ffmpeg, but an ffmpeg
developer. fabrice registered ffmpeg.org unilaterally!
why not stop beating around the bush and just come out with whatever
you are trying to say ? lay it all out here. once and for all.
what is the issue? and would you please rate the importance of the
issue to us. that will help us all to understand your position.
please. thank you.
-compn
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-06-25 0:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 20:20 Derek Buitenhuis
2025-06-24 1:12 ` Michael Niedermayer
2025-06-24 4:29 ` Kieran Kunhya via ffmpeg-devel
2025-06-24 5:14 ` Vittorio Giovara
2025-06-24 5:24 ` Derek Buitenhuis
2025-06-24 14:53 ` Michael Niedermayer
2025-06-24 14:59 ` Kieran Kunhya via ffmpeg-devel
2025-06-24 17:48 ` Vittorio Giovara
2025-06-24 15:02 ` Michael Niedermayer
2025-06-24 15:06 ` Michael Niedermayer
2025-06-24 5:59 ` compn
2025-06-24 6:48 ` Kieran Kunhya via ffmpeg-devel
2025-06-24 7:28 ` compn
2025-06-24 8:22 ` Kieran Kunhya via ffmpeg-devel
2025-06-25 0:09 ` compn [this message]
2025-06-25 0:31 ` Kieran Kunhya via ffmpeg-devel
2025-06-24 14:06 ` softworkz .
[not found] ` <CABGuwE=5LbscbsJKi2XQTO31_Pn1459txrtkE1KnjDmGKqOQWA@mail.gmail.com>
2025-06-24 22:14 ` Kieran Kunhya via ffmpeg-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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250624140940.00000a53@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git