I'm trying to get someone with xkcd 1597-level understanding of Git comfortable with using the Fedora Docs workflow. This involves forking the primary repositories and making pull requests.

It's not unmanageable for the first edit, but if someone makes some change and then comes back six months later and has more edits, the fork is likely completely behind upstream, and then it becomes ... really, rather a lot. Deleting the fork and recreating is probably the easiest, but that's a lot of steps. And setting an upstream for a local clone of your fork and going through all that is also a lot of steps plus a lot of opportunities for mistakes.

Look at this on gitlab: https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#repository-mirroring

Or less automatic but still nice from github: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

I think we need something like this in order to really grow Docs contributions.

Of course, the same thing would be useful for dist-git forks.