[GH-ISSUE #294] Git for contracts in Documenso #79

Open
opened 2026-02-26 18:45:16 +03:00 by kerem · 2 comments
Owner

Originally created by @chrisvont on GitHub (Aug 23, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/294

I am currently signing a couple of individual legal entities in a larger deal. We have a deal room (signing 35+ documents with DocuSign) in Nextcloud and I have so much communication overhead for every change we make. Having a git for contracts to be signed would make the process so much smoother. Right now I do the changes in the next cloud and write a change log via e-mail. Ultimately, the customer still needs to trust me that these are the only changes I made. Of course, I could use the version control of Microsoft, but that adds a lot of complexity to it.

Open signing infrastructure could handle the whole process end to end. In more complex mid-market and enterprise deals, negotiations are also a huge part of the Deal UX.

Originally created by @chrisvont on GitHub (Aug 23, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/294 I am currently signing a couple of individual legal entities in a larger deal. We have a deal room (signing 35+ documents with DocuSign) in Nextcloud and I have so much communication overhead for every change we make. Having a git for contracts to be signed would make the process so much smoother. Right now I do the changes in the next cloud and write a change log via e-mail. Ultimately, the customer still needs to trust me that these are the only changes I made. Of course, I could use the version control of Microsoft, but that adds a lot of complexity to it. Open signing infrastructure could handle the whole process end to end. In more complex mid-market and enterprise deals, negotiations are also a huge part of the Deal UX.
Author
Owner

@OmarMcAdam commented on GitHub (Aug 24, 2023):

This would be a HUGE boost to workflows.

Most "Legal teams" would rather use docx, so export/import parse of docx would still be needed. The files are encoded in xml and meta-data can be parsed from them.

Having an audit log, version history, and notifications of changes would remove a significant amount of overhead in the process.

<!-- gh-comment-id:1691144881 --> @OmarMcAdam commented on GitHub (Aug 24, 2023): This would be a HUGE boost to workflows. Most "Legal teams" would rather use docx, so export/import parse of docx would still be needed. The files are encoded in xml and meta-data can be parsed from them. Having an audit log, version history, and notifications of changes would remove a significant amount of overhead in the process.
Author
Owner

@raikasdev commented on GitHub (May 1, 2024):

Could be interested with working on this in the future, right now bit busy. Found Pandiff library (well, more of a "CLI wrapper") built on top of Pandoc which possibly could be used for this. This would support pretty much most of the document formats available from Markdown to wikitext 😄

Is running CLI-commands in the background fine for these kind of operations, probably yes? The library will probably need use-case specific modifications. Pandoc seems to support reading documents from a file, URL or from stdin, which would be preferable?

<!-- gh-comment-id:2088960278 --> @raikasdev commented on GitHub (May 1, 2024): Could be interested with working on this in the future, right now bit busy. Found [Pandiff](https://github.com/davidar/pandiff) library (well, more of a "CLI wrapper") built on top of Pandoc which possibly could be used for this. This would support pretty much most of the document formats available from Markdown to [wikitext](https://en.wikipedia.org/wiki/Help:Wikitext) :smile: Is running CLI-commands in the background fine for these kind of operations, probably yes? The library will probably need use-case specific modifications. Pandoc seems to support reading documents from a file, URL or from stdin, which would be preferable?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#79
No description provided.