3 ms·
The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's p
by arohner 15y ago
The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc.
i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be.
It seems like Github should add this feature, (open source, with whitelisted contributors) and then the need for the JIRA mess all goes away.
- dhconnelly 15y agoWhy couldn't pull requests just be kept on hold until the contributor signs the agreement?
- TeHCrAzY 15y agoMy guess would be the sheer volume of commits would be unmanageable unless the process was somehow automated
- arohner 15y agoThe real issue is verifying that the person has a CA at all. You don't want to scan a list for a person's name on every merge. In JIRA, it's easier for the committer, because only contributors have the correct permissions to submit a patch at all. GitHub currently has no analogue.
- rjurney 15y agoThis sounds like a workable solution. Github adds a feature, apache opens to github. Compromise?
- rjurney 15y agoWait, this is a checkbox on jira, is it not?