I agree with this…
my experience with Axoloti:
we have the same model (for 3 years?) as norns now has, so a community git, but the ability for 3rd party git repos to be added as additions. (we also have local libraries which are not sync’d)
(oh, we also have a ‘factory’ git, which contains all the axoloti supplied stuff)
our prefs to view libs
adding/editing lib:

(obviously things like sync, sync all , are on the menus)
most users do not want or need to know anything about git…
in the UI, I gave them the ability to sync (one or all) , add/remove library (=repo) , reset.
(note: for ‘contributors’ , sync is bi-directional!)
reset is important, its my ‘get out of jail free card’, after a warning (about backing up your changes) it deletes directories, and re-clones from git.
users like the simplicity of this… as for most users it just ‘sync’ that they use.
the issue with git is if you’re not careful, and don’t have a defined workflow, users will start changing things in directories , that will later (days, weeks, months!) cause merge conflicts that they (non-developers) will have no idea how to fix (and is nigh impossible to ‘automate’)
this is why we have a ‘partitioned’ community repo, but honestly now I probably would not do this - Id probably force all contributors into having their own repos - maintain a community repo long term is not much fun.
the other issue you will need to address with a ‘workflow’ is versioning of scripts so that when there is an API change in norns, you don’t break existing scripts - last thing you want is, new releases/scripts breaking existing uses - we did this with branches, which is hidden from the end users (as app supplies branch version to use on repo)
it’s actually worked pretty well for us, as git has all the versioning/sync support you need.
that said…
Ive quite enjoyed the simplicity of the Organelle patch installation,
Im starting to think for linux based systems, that my ‘next solution’ might be to have ‘patches’ as (debian) packages , as it not only handles versioning and syncing, but also dependency management… very useful for patches using libraries, or when you go beyond patches, and need other OS packages.
distribution then for online users is done by your own apt-server, but you can also provide offline installs (e.g. pkgs on a usb stick)