A clear path to send patches for PKGBUILDS

Idea proposal 💡

Checks

NOTE: The below check boxes must be checked before the accompanying idea will be considered.

• I have checked that the idea is not directly tied to a specific project For example: "Show label icons in the package overview web page" must be a feature request in the ArchWeb repository
• I have carefully checked this idea is not already covered by any open or closed ideas.
• I understand that I hold no copyright claims and that this idea can be adapted and used by Arch Linux in any arbitrary shape or form.

Summary

A mechanism to send patches or merge requests or similar for packages.

Motivation

I've often had a small fix for some package, but it's unclear how to send it. Shall I email a patch to the maintainer? Do they keep their PKGBUILDS in a git repo somewhere? Should I email all the maintainers, or just one? Does a git-patch even apply on svn?

This varies dramatically, and the fact that there's no clear/obvious way to submit patches hinders contributions. A clearly defined path motivates contributions from the community at large.

Specification

A list with patches for [community] and another with patches for [core] could make sense. It's a clear way for users to contribute, and gives good visibility to patches. On top of that, it provides a clear place for discussion/feedback to happen, or for others to follow up (or even find out if something has been discussed already).