On Mon, 22 Aug 2022, at 14:43, Nicolas George wrote: >> Therefore, I don't think those plans documents are useful: "show us >> the code!". > > Try this with your plumber: “Show me my shower fixed and I'll pay you if > I'm satisfied.” It does not work that way, you have to sign a sales
This is a contract, with paid money and clear objectives. > quote before the plumber gets to work. This is the kind of mechanism I > want to find for FFmpeg. FFmpeg is a volunteer open source project, not a contracting or plumbing initiative. If the SoW is not done, the money is not paid. This does not work for open source communities. > Are you suggesting that I propose the headers and documentation for > AVWriter, that we discuss it and hopefully push it before investing more > time in the implementation? You provide a full header and documentation, and then get it discussed. When there is a consensus for approval of the headers, then, you can code the core of it that matches the headers. That avoids the "I spent time for nothing" issue. -- Jean-Baptiste Kempf - President +33 672 704 734 _______________________________________________ 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".
