From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] doc: add spi.txt
Date: Wed, 18 Oct 2023 23:46:48 +0200
Message-ID: <ZTBSSJFLzY1vC5bm@mariano> (raw)
In-Reply-To: <F72F92F3-B5B7-4B14-B6C2-6CD69AA4FED7@gmail.com>
On date Tuesday 2023-10-17 14:41:00 +0200, epirat07@gmail.com wrote:
>
>
> On 17 Oct 2023, at 9:29, Stefano Sabatini wrote:
>
> > On date Monday 2023-10-16 06:34:45 +0200, Lynne wrote:
> >> Oct 16, 2023, 00:50 by michael@niedermayer.cc:
> >>
> >>> This explains how to request refunds and what can be funded by SPI
> >>>
> >>> Co-Author: Stefano Sabatini <stefasab@gmail.com>
> >>> ---
> >>> doc/spi.txt | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>> 1 file changed, 73 insertions(+)
> >>> create mode 100644 doc/spi.txt
> >>>
> >>> diff --git a/doc/spi.txt b/doc/spi.txt
> >>> new file mode 100644
> >>> index 0000000000..ff4af8f42b
> >>>
> >>
> >> Again, I think this belongs on the website, not in our codebase.
> >
> > Given that this is a sort of internal memo, and that is targeted at
> > developers rather than final users, I see no value into exposing this
> > in the website (and we have similar documents - e.g. community.texi -
> > already in doc).
> >
> > OTOH given that this clarifies how donations are spent, there is also
> > a value into making this more transparent to users/donors, but I don't
> > see this as blocking (we can publish it here and then move it to the
> > website once the process has been consolidated).
>
> IMO this would be much more discoverable on the website, it would
> never occur to me to look for such information in the FFmpeg source
> tree doc folder.
I'm fine with either, I'll let Michael decide the final target repository.
_______________________________________________
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:[~2023-10-18 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 22:49 Michael Niedermayer
2023-10-16 4:34 ` Lynne
2023-10-17 7:29 ` Stefano Sabatini
2023-10-17 12:41 ` epirat07
2023-10-18 21:46 ` Stefano Sabatini [this message]
2023-10-18 22:15 ` Stefano Sabatini
2023-10-19 1:29 ` Lynne
2023-11-07 20:16 ` Michael Niedermayer
2023-11-07 22:01 ` Lynne
2023-10-17 7:22 ` Stefano Sabatini
2023-11-08 11:35 ` Alexander Strasser
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=ZTBSSJFLzY1vC5bm@mariano \
--to=stefasab@gmail.com \
--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