[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jfw] Contributor Agreement
I like the idea. I could detail scope of legal risk-but to me thats to much mumbo jumbo, your suggestion is the equivalent of a online signature that does stand in court. We have a entire team of developers that would not allow risky code in our repos (I hope). If we had our structure correct, we would be doing risk mitigation at the commit level. Meaning someone/attorney geek - would be scrubbing our code for litigation risk. We should not be accepting any code the the main trunk that is a possible litigation risk or not clearly labeled as compatible license. I do not think we need a attorney to tell us this how to maintain our own code or use code within our FOSS structure.
If the project wanted to keep the signature process, it would be easier if they financed a service like Ecosign or other like service to host the signed PDF contributor agreements. This way we can send developers a link, have them sign, and go.
At the end of the day, we are not sure who has signed the agreement, and who at the commit level is doing the compare of signed contracts to what code is accepted in the repo. Im guessing that we do not even have a proxy setup like this or tracking within our source. So the thoughts of getting people to agree inline with the repo and connected to the GITHUB system would be more of a safe and organized bet to keep our developers agreeing to our license structure.
Framework source code: https://github.com/joomla/joomla-framework
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+unsubscribe AT googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-framework.