Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: ffmpegagent <ffmpegagent@gmail.com>,
	"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/5] doc/developer: Add subsection about patch submission via FFstaging
Date: Thu, 8 May 2025 11:13:31 +0000
Message-ID: <DM8P223MB036538CF33E822F57AC5C619BA8BA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <pull.76.ffstaging.FFmpeg.1746699749.ffmpegagent@gmail.com>



> -----Original Message-----
> From: ffmpegagent <ffmpegagent@gmail.com>
> Sent: Donnerstag, 8. Mai 2025 12:22
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz <softworkz@hotmail.com>
> Subject: [PATCH 0/5] doc/developer: Add subsection about patch submission via
> FFstaging
> 
> Signed-off-by: softworkz softworkz@hotmail.com
> 
> softworkz (5):
>   doc/developer: Move checklist into Submitting Patches chapter
>   doc/developer: Move codecs/formats checklist into Development Policy
>     chapter
>   doc/developer: Reorder Submission procedures content
>   doc/developer: Merge Review paragraphs and deduplicate
>   doc/developer: Add subsection about patch submission via FFstaging
> 
>  doc/developer.texi | 234 ++++++++++++++++++++++++---------------------
>  1 file changed, 127 insertions(+), 107 deletions(-)
> 
> 
> base-commit: 1b643e3f65d75a4e6a25986466254bdd4fc1a01a
> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-
> 76%2Fsoftworkz%2Fsubmit_website_update-v1
> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-
> 76/softworkz/submit_website_update-v1
> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/76
> --
> ffmpeg-codebot


Forgot so save the cover letter text before submitting:


The https://ffmpeg.org/developer.html (doc/developer.texi) page contains a lot of good information but there's some structural and contentual duplication that is begging for cleanup:

[3 Development Policy](https://ffmpeg.org/developer.html#Development-Policy-1)
[4 Submitting patches](https://ffmpeg.org/developer.html#Submitting-patches-1)
[5 New codecs or formats checklist](https://ffmpeg.org/developer.html#New-codecs-or-formats-checklist)
[6 Patch submission checklist](https://ffmpeg.org/developer.html#Patch-submission-checklist)
[7 Patch review process](https://ffmpeg.org/developer.html#Patch-review-process)

- a Patch submission checklist clearly belongs to the context of  "Submitting Patches"
- a checklist about the requirements for adding new codecs/formats is mostly a matter of policies
- after moving 5 into 3 and 6 into 4,  another duplication can be resolved elegantly as 4 ends with a section about patch reviews which is then adjacent to the current 7 (patch review process)
- inside 4:
  - some duplication between 4's intro and the checklist can be removed
  - the second part becomes "Submission procedures" with three subsections (send-email, format-patch and FFstaging) and the content separated in a more logical way


Thanks
sw
_______________________________________________
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".

  parent reply	other threads:[~2025-05-08 11:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 10:22 ffmpegagent
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 1/5] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 2/5] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 3/5] doc/developer: Reorder Submission procedures content softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 4/5] doc/developer: Merge Review paragraphs and deduplicate softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 5/5] doc/developer: Add subsection about patch submission via FFstaging softworkz
2025-05-08 12:40   ` James Almer
2025-05-08 12:55     ` softworkz .
2025-05-08 11:13 ` softworkz . [this message]
2025-05-08 11:20 ` [FFmpeg-devel] [PATCH 0/5] " Lynne
2025-05-08 11:33   ` softworkz .
2025-05-08 11:59     ` Lynne
2025-05-08 12:26       ` softworkz .
2025-05-08 12:36         ` Lynne
2025-05-08 12:47           ` Nicolas George
2025-05-08 13:12             ` softworkz .
2025-05-09 10:17             ` softworkz .
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 0/4] doc/developer: Restructure docs about patch submission ffmpegagent
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 1/4] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 2/4] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 3/4] doc/developer: Reorder Submission procedures content softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 4/4] doc/developer: Merge Review paragraphs and deduplicate softworkz

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=DM8P223MB036538CF33E822F57AC5C619BA8BA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpegagent@gmail.com \
    /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