Open sirinath opened 10 years ago
Hey, I can understand that signing agreements is a hassle, but if you just assume that people accepted you might as well have no agreement at all. A similar project, contributoragreements.org just launched that features new agreements in conjunction with the option/help to create an 'e-signing' process. This allows for easy signing of agreements. You could also take a look at clahub.com for management of contribution agreements/signatures and contributors.
I am not saying they just accept. I am saying if the wording in the agreement says it is accepted on either forking, omitting or sending a pull request.
This distinction really doesn't matter in this case. There are good reasons why the agreement doesn't say something like this. Most of all, at the very least people would have to read it, and then you might as well have an e-signing process. If you have an agreement that says it is accepted on commit/PR without people having actually read it before, you might as well not bother in the first place. And, assuming a FOSS compliant license, you can't require acceptance of anything on forking. If you want to opppose obligations on forks: don't use github/public repo, get a proprietary license.
Signing agreements are a hassle. So is it possible to have an agreement deemed accepted on 1st Commit or PR along with the other options you already provide.