If you have rebased, updated, improved, or found something interesting regarding any of these, feel free to share with a PR ;)
The rules to make community patches are the same as target's userpatches (extension defines how the patch is applied).
If you have cloned this repo alone and want to use it with other Frogging-Family repos, base dirs should be next to each other for other projects to find community-patches. Example: community-patches linux-tkg wine-tkg-git.
For community-patches supported repos and in case it isn't found, this community-patches repo will be cloned automatically at build time (following the above path logic) if you add an entry to the community-patches array of the project's .cfg file.
You can enable one or multiple patches for their respective target in the .cfg file of the target itself, using the _community_patches option (more detail in the .cfg's)