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

Amar Takhar (@amar) gitlab at rtems.org
Fri Jul 24 03:28:14 UTC 2026




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


This is something we're looking to add for enforcement in the future when we get tighter reins on security.  We've deliberately not had it because it's utterly useless.  We can't verify who anyone is.  A Signed-off-by statement only asserts the text not the person.  Yes, for some we know who but we also know that already so why an extra step?  Eventually we'll have signed commits from developers which makes it even more useless.

This is too much bandwidth for the project right now in the future, if we can secure funding to help with these activities we'll do it but for now we can only do what we have already which is ask for a deceleration.  

I'll create an Epic for this eventually to collect all these issues but I don't see any movement on this at the moment.  Thanks for the suggestion.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_155309
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-4txg420pur1mln02q317nxyk0-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/20260724/e65a690c/attachment.htm>


More information about the bugs mailing list