-
Notifications
You must be signed in to change notification settings - Fork 28.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gcc warning in inspector protocol implementation #32357
Comments
@sam-github you should mark the patch as ready for review |
OK, I figured out how to do that. Obviously if I want someone else to review something... I have to "start review". 🤕 |
@targos I'd have to find who in IBM has legal authority to sign a contributor agreement for me, but honestly, I'm not sure if its worth it. I might get to it next week, but maybe you want to PR the fix? I give the code to you if you want it. |
@sam-github since IBM already have folks contributing to V8, you probably already have a signed agreement. If that's the case, using your IBM email shot be enough. |
I can't see any way to change the owner of a CL, and it looked like I needed a agreement that specifically mentioned me, and my company.EDIT: I abandoned the CL, its easier for the maintainers to just fix it than to go through the CL process with an external contributor. Sorry, @targos. |
They might not push the changes since you proposed it first to avoid any legal issues (I know, I know). Hopefully that's not the case.
Not possible AFAIK, you would need to resubmit it.
Larger companies usually have a company-wide signed CLA with open source projects, and discourage (or disallow) individual signatures. Of course, maybe IBM handles this differently, but having a company-wide signature is also recommended by the "Legal Stuff" they referenced: "All contributors must complete the contributor license agreement. For individual contributors, please complete the Individual Contributor License Agreement online. Corporate contributors must fill out the Corporate Contributor License Agreement and send it to us as described on that page." |
The text was updated successfully, but these errors were encountered: