4 ms·

Great interface. Questions: > The process for creating and revising the contracts is modeled after an open-source software project Which Open Source Project? C

by darthvader2000 3y ago

Great interface. Questions: > The process for creating and revising the contracts is modeled after an open-source software project Which Open Source Project? Could you link it please? What do you mean by Open Source Contracts? Do you mean community edits & maintains contract templates? Do you have APIs to integrate? Do you have your own way of signing contracts or use third party tools like DocuSign?

jakestein 3y ago
Thanks for these questions, taking each in turn: > The process for creating and revising the contracts is modeled after an open-source software project Which Open Source Project? Could you link it please? We didn't model it after a particular open-source project. Rather, we tried to take lessons learned from open-source software projects in general and apply those lessons to the creation and maintenance of the standard contracts. > What do you mean by Open Source Contracts? Do you mean community edits & maintains contract templates? There's a few elements of what we mean by this: - The contracts are released under the Creative Commons CC BY 4.0 license. It shares a lot of principals and goals with the OSI licenses for software (eg Apache and GPL) but is built for things other than software - Yes, the community edits and creates the agreements. The community members are largely attorneys rather than software developers, and you can see a list of some of the most active members here: https://commonpaper.com/committee/ https://commonpaper.com/committee/ - We have an amazing attorney on our team who is analogous to the maintainer of an open-source project. She solicits and collects feedback from the community and makes the final decision about what does and doesn't get into any particular release. >Do you have APIs to integrate? Yes, and you can see the docs here: https://api.commonpaper.com/docs https://api.commonpaper.com/docs >Do you have your own way of signing contracts or use third party tools like DocuSign? We embed Dropbox Sign (formerly HelloSign) within our product for this step
bengarvey 3y ago
Hi, one of the co-founders here! 1. We didn't model it after a specific open source project, but Jake worked on https://www.singer.io https://www.singer.io. We do take inspiration from Open Source licenses like Apache 2, GPL, MIT, etc. 2. Open source in the sense that the terms of the contract are open source and released under a CCBY license. Terms are available via versioned URLs, github markdown source control, and maintained by a committee of contributors (attorneys). 2. Yes! You can find our REST API docs here: https://api.commonpaper.com/docs https://api.commonpaper.com/docs. It uses the JSONAPI spec. 3. We're currently integrated with Dropbox Sign.

jakestein 3y ago

Thanks for these questions, taking each in turn: > The process for creating and revising the contracts is modeled after an open-source software project Which Open Source Project? Could you link it please? We didn't model it after a particular open-source project. Rather, we tried to take lessons learned from open-source software projects in general and apply those lessons to the creation and maintenance of the standard contracts. > What do you mean by Open Source Contracts? Do you mean community edits & maintains contract templates? There's a few elements of what we mean by this: - The contracts are released under the Creative Commons CC BY 4.0 license. It shares a lot of principals and goals with the OSI licenses for software (eg Apache and GPL) but is built for things other than software - Yes, the community edits and creates the agreements. The community members are largely attorneys rather than software developers, and you can see a list of some of the most active members here: https://commonpaper.com/committee/ https://commonpaper.com/committee/ - We have an amazing attorney on our team who is analogous to the maintainer of an open-source project. She solicits and collects feedback from the community and makes the final decision about what does and doesn't get into any particular release. >Do you have APIs to integrate? Yes, and you can see the docs here: https://api.commonpaper.com/docs https://api.commonpaper.com/docs >Do you have your own way of signing contracts or use third party tools like DocuSign? We embed Dropbox Sign (formerly HelloSign) within our product for this step

bengarvey 3y ago

Hi, one of the co-founders here! 1. We didn't model it after a specific open source project, but Jake worked on https://www.singer.io https://www.singer.io. We do take inspiration from Open Source licenses like Apache 2, GPL, MIT, etc. 2. Open source in the sense that the terms of the contract are open source and released under a CCBY license. Terms are available via versioned URLs, github markdown source control, and maintained by a committee of contributors (attorneys). 2. Yes! You can find our REST API docs here: https://api.commonpaper.com/docs https://api.commonpaper.com/docs. It uses the JSONAPI spec. 3. We're currently integrated with Dropbox Sign.