Other Open Source programs use to put the name of the developers/authors in an AUTHORS file. I think it is more convenient than writing them to each individual file, NOW. If a developer will write a new Plugin He will write His name inside, I think. For example, take a look at Scribus https://github.com/scribusproject/scribus For the GPL license we have COPYING file https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra... IgorBeg Il 06/01/2023 01:07, Andrew Randrianasulu via Cin ha scritto:
чт, 5 янв. 2023 г., 23:19 Phyllis Smith <[email protected] <mailto:[email protected]>>:
I don't know anything about License and GPL but I think that in Cinelerra-GG there is the About window where you can write all the Developers/Authors you want, without including them in every Cinelerra's file (.h, .C, .inc,...).
for seeing this window you must have successful compile, and if compile was not successful you look into source files ( I think this might be part of rationale about putting them there ). Each source file usually worked on by some developers, so knowing who works (worked) on specific part is also important (when you have 1000+ files). Putting ALL program authors in EACH file obviously wrong, but making sure relevant names appear in files you get right after unpacking source considered good tone....