(This was a comment on #2380, but seems like - though related - is a UI and general process issue)
Here is a concrete example of a useful community process hook, by way of a specific example from a UI element from github.com, and how it is being used.
In my context, people would prefer to use hg to git, and the generality of this seems so broad that I bring it to your attention.
The feature is "Edit" button / option when viewing any file of any arbitrary repository. The action of that "Edit" button would be "fork this repository", so that you instantiate a fork-followed-by-edit on your fork.
To see how this is useful, have a look, for example, at the following document from UMich:
Note the yellow "edit this document" in the lower right. Click, and follow the top link (to the source for that particular page; works with any arbitrary page, linking back to the correct source page in the repository);
NOTE: github.com has a UI element "Edit" - hover over it.
NOW: Forking is up to the user who would like to make an edit / correction. If a user doesn't have a bitbucket account, a path to creating one would be provided.
This has the effect of facilitating a process, and encouraging community participation.
I think this general "EDIT" on any given file, with such an associated action path would be most useful.