RTEMS | Adopt a Developer Certificate of Origin and an AI disclosure tag (#5657)

[Amar Takhar (@amar)]

Amar Takhar commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_156949


Sebastian can you open another issue for adding `assisted-by:` Thank you.

 As far as `DCO.txt` we will be signing commits and the same thing applies to signed-off-by we can still be defrauded.  We have a license already, if you add a commit to our repo you accept the license we don't need a separate document to certify this.  As for "AI not being able to sign off"  The developer who is adding the commit is doing it regardless of where the origin is.  Same can be said when you pull a 3rd party commit from a different repository it's not like the committer authored any of the original code and you can't hold the original author liable it's the committer who is.  There is no absoliving yourself of that responsibility because "ai wrote it" or "it's a 3rd party commit".   You are responsible regardless and signed commits will solve this.

>From my point of view I care more about the code / safety / security aspect let lawyers do the legal work.  We picked 2BSD to make things easier and all these asks aren't for the project but for commercial entities.  We have no funding to add extra churn while it's easy for you to ask you're being paid we are not.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_156949
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-0vveeazt7ia6ujh5n8n1uzfnw-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260815/8bc535ea/attachment.htm>