RTEMS | cpukit/telnetd/pty.c: Amend comments for grammar/spelling & cpukit/libcrypt: Changed 'memset' to 'explicit_bzero' (!674)

[Wayne Thornton (@wmthornton-dev)]

Wayne Thornton commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/674#note_128958


Thank you for the insight. I was able to review issue rtems#33 and now have a handle on what exactly is being discussed. I'd agree with @joel that it may be simpler to pull down the code from the FreeBSD repositories, although the updated FreeBSD files contain a lot of code not utilized here. It would make more sense (to me, as the outsider) to own the code as RTEMS' codebase and to make the modifications necessary to remove FreeBSD-specific references and defines in the file. My understanding vis-a-vis the issue regarding modification of 3rd-party code is that it is allowed by virtue of the BSD-2-Clause license being employed so long as the original copyright notice is retained and the file is not re-licensed under a different license. As the documentation for licensing found here: https://docs.rtems.org/docs/main/eng/license-requirements.html states, this license is preferred by the project so modifying shouldn't be an issue. 

On a more direct note, should the project decide to own the code, I would be willing to become the codeowner for telnetd subsystem and take responsibility for these changes moving forward. Although this MR constitutes my first contribution to the project, and they are relatively minor contributions, that is the result of my seeking to find a project to join and start with simple, easy to digest commits as I learn the intricacies of how the project works and the processes in place for developers.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/674#note_128958
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250818/cf688c0c/attachment-0001.htm>