# Copyright/License issue - Thread: https://externals.io/message/102966 - Original archive: https://news-web.php.net/php.internals/102966 - Started by Christoph M. Becker on 2018-07-24T23:14:39+00:00 - Messages: 3 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #102966 — Christoph M. Becker — 2018-07-24T23:14:39+00:00 URL: https://externals.io/message/102966#102966 Hi! I've just stumbled upon sapi/fpm/fpm/fpm_status.c[1], which claims copyright by Jerome Loyet and doesn't state any license. It seems to me that we must not ship/modify this file. IANAL. [1] -- Christoph M. Becker --- ## #102968 — Jakub Zelenka — 2018-07-25T07:17:49+00:00 URL: https://externals.io/message/102966#102968 · In reply to: #102966 Hi > Hi! > > I've just stumbled upon sapi/fpm/fpm/fpm_status.c[1], which claims > copyright by Jerome Loyet and doesn't state any license. It seems to me > that we must not ship/modify this file > Why do you think that and how is it diffiren to all other fpm files? FPM is BSD licensed (see the LICENSE file) so I think we can modify any file as we want and it's been always like this - we have already modified it anyway. The copyright in the files are for the specific year(s) so I think we should actually add line below with PHP Group copyright or whatever for the years when it was modified but not really sure what's the right way to deal with that... Cheers Jakub --- ## #102969 — Christoph M. Becker — 2018-07-25T09:20:29+00:00 URL: https://externals.io/message/102966#102969 · In reply to: #102968 Hi! > > > > […] > > Why do you think that and how is it diffiren to all other fpm files? FPM is > BSD licensed (see the LICENSE file) so I think we can modify any file as we > want and it's been always like this - we have already modified it anyway. > The copyright in the files are for the specific year(s) so I think we > should actually add line below with PHP Group copyright or whatever for the > years when it was modified but not really sure what's the right way to deal > with that... Thanks! I should have checked this more carefully. The LICENSE file in the folder above may well be sufficient. I would appreciate, though, if there was a short license hint/indicator in each file (at least if there is a copyright notice), and indeed it appears sensible to add copyright lines to indicate that individual files have been modified. -- Christoph M. Becker