Le maanantaina 11. marraskuuta 2024, 1.06.12 EET Michael Niedermayer a écrit : > > On the other hand, if we assume that it does not get separated, I think > > the lack of activity tells about the impopularity of the library. I don't > > see the point in spending time and/or money if nobody cares anymore, > > unless this is a research project but that does not seem to be what you > > are proposing.
> libpostproc needs bugtracking, selftests, fuzzer support, documentation, > its API would need to be updated to match todays features. > (like any library would need) To summarise my previous message: that is moot. If libpostproc goes on to live (and maybe quietly die) outside FFmpeg.git, then those technical and finance questions do not belong on FFmpeg-devel. You get to raise those questions on libpostproc-devel after you have split the project out. > libpostproc is part of FFmpeg it is not "outside" FFmpeg or "outside" > the STF scope. The question is not if it is in scope of FFmpeg. It can be argued that it is, or at least that it was. With the benefit of hindsight, it is however clear that it won't flourish in FFmpeg.git and on FFmpeg-devel. So if you want to resurrect it, you'd better split it out. And if you do split it out, then the questions about its funding do not belong here. > The reason for me to consider to split libpostproc out is to be able to > work on the code without the eternal debates here. That's one way to put it. -- 雷米‧德尼-库尔蒙 http://www.remlab.net/ _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
