3 ms·
Facebook first needs to bring HHVM up to full compatibility before they try altering the spec. I also discovered Facebook makes all their "contributors" (anyon
by ck2 12y ago
Facebook first needs to bring HHVM up to full compatibility before they try altering the spec.
I also discovered Facebook makes all their "contributors" (anyone who does a pull request) sign an agreement with them, which seems weird and not cool. https://code.facebook.com/cla https://code.facebook.com/cla
- skymt 12y agoIt's not unprecedented. GNU projects require contributors to sign over the copyright for their code. Facebook's requirement of copyright and patent license is relatively restrained.
- dragonwriter 12y ago> Facebook first needs to bring HHVM up to full compatibility before they try altering the spec. Defining a spec (there isn't a pre-existing spec that is being "altered") is an important part of moving to acheive compatibility, since its how you know what the target is. HHVM spawning a spec effort for PHP is a lot like Rubinius spawning RubySpec.
- spicyj 12y ago> I also discovered Facebook makes all their "contributors" (anyone who does a pull request) sign an agreement with them, which seems weird and not cool. https://code.facebook.com/cla https://code.facebook.com/cla This is standard for virtually any open-source project backed by a large company and for many that are independent (e.g., all Apache projects: http://www.apache.org/dev/new-committers-guide.html#cla http://www.apache.org/dev/new-committers-guide.html#cla).
- madeofpalk 12y agoThese CLA are fairly common arent they, esp. among largercompanies that have/run open source projects? ? e.g. https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md https://github.com/angular/angular.js/blob/master/CONTRIBUTI...