Hi Niklas On Sun, Mar 22, 2026 at 06:59:25PM +0100, Niklas Haas via ffmpeg-devel wrote: > > On Sun, Mar 22, 2026, at 4:23 PM, Michael Niedermayer via ffmpeg-devel wrote: > > Hi Martin > > > > On Sat, Mar 21, 2026 at 11:15:06PM +0200, Martin Storsjö via ffmpeg-devel > > wrote: > >> On Sat, 21 Mar 2026, Michael Niedermayer via ffmpeg-devel wrote: > >> > >> > > Nothing requires a dependency on external infrastructure. > >> > > >> > The imported tree clearly points users and contributors to external > >> > infrastructure: > >> > > >> > +tests/checkasm/ext/docs/getting-started.md:url = > >> > https://code.videolan.org/videolan/checkasm.git > >> > +tests/checkasm/ext/docs/getting-started.md:git submodule add -b release > >> > https://code.videolan.org/videolan/checkasm subprojects/checkasm > >> > +tests/checkasm/ext/docs/introduction.md:- [**GitLab > >> > Repository**](https://code.videolan.org/videolan/checkasm) > >> > +tests/checkasm/ext/docs/introduction.md:- [**Issue > >> > Tracker**](https://code.videolan.org/videolan/checkasm/issues) > >> > +tests/checkasm/ext/docs/introduction.md:- [VideoLAN > >> > Homepage](https://www.videolan.org/) > >> > +tests/checkasm/ext/src/html_data/body.html: This report was > >> > created using the <a id="checkasm-version" > >> > href="https://code.videolan.org/videolan/checkasm";>checkasm</a> > >> > > >> > So even if you do not consider that a hard technical dependency, it is > >> > still an integration centered around external infrastructure and > >> > external project entry points. > >> > >> So if you are bothered by those files, > > > > I am not concerned about those files merely existing. > > I am concerned about FFmpeg importing code in a form that points users > > and developers away from FFmpeg infrastructure. > > > > Whether this is done as a git subtree, a linked libcheckasm library, or > > some other mechanism is a secondary technical question. > > My main concern is that checkasm, if used by FFmpeg as part of our > > testing infrastructure, > > should be hosted and maintained in a way that FFmpeg can control on > > code.ffmpeg.org. > > And do you agree that having a checkasm repo on FFmpeg forgejo would > alleviate those concerns?
If you mean that checkasm would be hosted on code.ffmpeg.org, then yes, that would address the main concern I raised. If you have a more specific setup in mind, please elaborate. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The greatest way to live with honor in this world is to be what we pretend to be. -- Socrates
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
