Closed jmertic closed 5 years ago
Thanks for this advice! This was supposed to implement the Lite version, which upon further consideration seems more difficult than the one you describe. Until we better understand the DCO -- and decide whether or not we actually want it -- we've switched to the basic inbound=outbound model.
I'm happy to help you understand the DCO more if you'd like - ping me at jmertic at linuxfoundation dot org.
Thank you again for your willingness to help, and sorry for the delayed response. I've brought this to the attention of one of our open-source coordination folks.
No worries @nsadeveloper789 - keep me posted on any way I could help.
Hi!
Looking at the contributing guideslines at https://github.com/NationalSecurityAgency/ghidra/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-dco-process, I saw you are using the DCO ( which is great! ). That said, looking at the approach, it seems a bit kludgy:
Typically when DCO agreements are done, it's a signoff on the commit. Here's an example from a project I work on ( https://github.com/AcademySoftwareFoundation/tac/blob/master/process/contributing.md ):
Then there are nice tools like DCO bot and a local integration that makes the process super easy.
Happy discuss further online or offline if you like!