Switch From CLA to DCO

[bensternthal]

It looks like the CHIPS CLA was mistakingly enabled for OpenPRoT. According to the charter:

All new inbound contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;

This issue tracks turning off CLA and enabling the DCO bot.

I have permissions to disable the CLA on the backend of LFX but can not enable DCO for this organization. If someone from the project can reach out to myself or @wendallkaters we can coordinate on the change.

[FerralCoder]

Hi @bensternthal and @wendallkaters, sorry I missed this issue when it came in. I can help with this.

[bensternthal]

@FerralCoder great, when would be a good time to make this change. We don't have to do this exactly at the same time but it would be a good idea if DCO is enabled shortly after the CLA is turned off, so the same day or day after is ideal.

[bensternthal]

@FerralCoder can you make me a temporary admin on the OpenPRoT organization. I can enable the DCO bot for you.

[bensternthal]

@FerralCoder based on understanding this more. I think that your charter might be incorrect in specifying DCO. (Should have been caught in review).

The project is defined as:

The mission of the Project is to create and maintain both a specification and an open-source implementation of a standards-based Platform Root of Trust firmware stack.

As such the DCO is not adequate and you need the CLA with OWFa

Let me know if you are in agreement on the above and we will get the boilerplate language from legal.

[FerralCoder]

OK, if CLA is the right mechanism to use, lets go ahead with the correction to the charter.