Commits, Cloning and Collaboration

[joepio]

I love git: it enables cloning a repo, making changes and giving these changes back. That's an incredibly powerful feature to have. Atomic Data already has Commits, and with this Cloning feature there's also Forking. Should it also need a way to merge changes and make suggestions? And should this use Cloning, or is Forking too different?

Let's assume a user wants to improve some piece of data on a webpage - let's call him the changer. Say the local grocery store has an issue in its 'open times' during covid, and a customer wants to edit this. From the perspective of the changer, they could click the data they want to change, make a change, and click 'share suggestion'. What might happen under the hood to enable this?

Clone, change URL, save Commits

• Changer clones original resource from source, changes the URL to something that he controls.
• This creates an initial Commit in the Users Store, which contains a reference to the HTTP url and Commit hash on which that Commit is built.
• The User makes changes the the resource as usual, adding Commits.
• If the User wants to make these changes to the original resource, the Commits will no longer make sense, because the subject has changed.

Store Commits, create merge request

• User creates Commits to the resouce and stores them in their own Server.
• User creates a Merge Request at the target server. This merge request is a resource containing the sequence of Commits.
• The Source owner opens some inbox