On Mon, Mar 16, 2026 at 02:28:39PM +0000, marcos ashton via ffmpeg-devel wrote: > Add contributing.html covering building FFmpeg, submitting > patches via Forgejo, the review process, and writing FATE > tests for libavutil, libavfilter, and libavcodec.
I am only an occasional contributor to ffmpeg, but it seems to me that this information is redundant with information in https://ffmpeg.org/developer.html and in particular https://ffmpeg.org/developer.html#Submitting-patches-1 Also, I think that a useful information that I see nowhere and should be, in my opinion, said somewhere, is whether merge commits are the preferred way to merge Pull Requests (PR) or whether the PR should be rebased on master and force pushed. In the case of the rebase, there should be a complementary policy that there should be only one developper pushing on a PR branch or repository. Another issue, diverse developers seem to have different levels of rights. This should probably be documented somewhere (possibly with links to external documentation) such that newcommers with low levels of rights do not try to do something they can't do, based on documentation found elsewhere. To give a concrete example, I would like to add labels to a PR I did, but it seems that I can't, my wild guess is that I don't have the rights, but it would be nice if I did not lose time by trying to understand how I can do it when I can't. -- Pat _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
