[Cin] Working on adding GPL license attribution for all program files

Andrew Randrianasulu randrianasulu at gmail.com
Fri Jan 6 16:14:04 CET 2023

пт, 6 янв. 2023 г., 17:37 Andrea paz via Cin <cin at lists.cinelerra-gg.org>:

> I feel similarly to IgorBeg. Without going into too much detail about
> Open licensing, so as not to drive Phyllis crazy making she to pursue
> rare data lost in the menadirs of time, I would just leave a general
> Authors window for all the code, without having to put them in every
> file header.

thing is, file WITHOUT such header probably can cause misunderstanding (at
best) down the line .... (not to mention distant possibility of court
action by some wanna-be Microsoft/Apple)

so I think best course of action still fix most glaring omissions when
possible, and then add details as we found them.

> For example, I would say that CinGG uses code from multiple versions
> of Cin and also from external programs. For code derived from CinHV I
> would put a link to the CinHV page; I would do the same for CinCV
> (maybe it is better to ask Igor Vladimirsky, on which page to link)
> and CinCVE (Einar). Instead, the original contributors to CinGG can be
> made explicit clearly in this same authors window.
> In any case, the most competent person to ask is definitely Igor
> Vladimirsky, especially for Cin HV; CV and CVE.
> Finally I would hear suggestions from the various contributors to
> CinGG, for the best method by which to be cited; whether in each
> headers of their code or in general without going into detail.
> --
> Cin mailing list
> Cin at lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230106/34f0fd57/attachment.htm>

More information about the Cin mailing list