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

[Chris Johns (@chris)]

Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_157008


The DCO 1.1 from LF and the processes that support it are sound and valid when properly managed and supported. Adding a DCO statement is one part of this process and it works if you know the sign off is valid. You can audit and collect names but are they valid?

I have not seen how you propose the project ensures sign-offs are valid and I am interested in your view to management of this processes? Sorry if I have missed this.

How is this DCO process and related compliance by this project better or advantageous over the GitLab MRs we have now?

I also am not sure the title of this issue is right as it joins DCO and AI disclosure and implies DCO is the only means of achieving AI disclosure?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5657#note_157008
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-c10eaub3cx56tvtjscmlu6p8l-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/20260817/8a0ec703/attachment.htm>