On 17.01.2026 16:15, Morgan Aldridge wrote:
On Sat, Jan 17, 2026 at 08:16 Mailing Lists <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Based on Shaun Ren's GH OpenBSD code
(https://github.com/shaunren/chrony <https://github.com/shaunren/
chrony>) I have created a ports package/git
for Chrony 4.8.
There are a few questions that came up.
Regarding Chrony's source code:
First off, the author - Shaun Ren - is for me just a name on a Github
profile, no email or anything else. On www.mail-archive.com <http://
www.mail-archive.com> there is a
Shaun Ren with entries from almost ten years ago on the linux-kernel
mailing list with a @linux.com <http://linux.com> address. I opened
an issue on GH 10 days
ago informing him/her that I did create the port and asked a) if it is
ok and b) if yes, if Shaun would add the copyright to all the files
that
where modified.
What are the rules regarding the copyright of code and contact data
needed from a code owner? Shaun added a copyright to the file
sys_openbsd.c dating back to 2021 but not to now other file modified.
The project's COPYING file declares the license of the project to be GPLv2:
<https://github.com/shaunren/chrony/blob/openbsd/COPYING <https://
github.com/shaunren/chrony/blob/openbsd/COPYING>>
While `sys_openbsd.c` has an added copyright, it didn't change or remove
the GPLv2 license comment in that file:
<https://github.com/shaunren/chrony/blob/openbsd/sys_openbsd.c <https://
github.com/shaunren/chrony/blob/openbsd/sys_openbsd.c>>
I'm no lawyer, but that doesn't appear to change the license and
distributability.
Not being a laywer, I hope that is the case.
And how is it handled that the author is just a name, so not verifiable
nor reachable if no answer on GH should be given?
Morgan
/Thomas
