<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">сб, 7 янв. 2023 г., 03:02 Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">phylsmith2017@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"></div><div dir="auto">I mean LGPL is Library GPL a bit differently type of license from just GPL .</div></div></blockquote><div><span class="gmail_default" style="font-size:small">Andrew:</span></div><div><span class="gmail_default" style="font-size:small">Fixed and checked into GIT the corrections. I had just grabbed one GPL header and did not read it. So now "library" replaced by "program" and "Lesser" now gone. (I should be more careful).</span></div><div dir="auto"><span class="gmail_default" style="font-size:small"></span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Well, I think in general template message is correct, just we need pay attention when more than one author worked on it. You can look into ffmpeg's sources for some examples. Dates for (c) usually not exact, but at least year or range of years provided.</div></blockquote><div style="font-size:small" class="gmail_default">Also, corrected the dates as best as I could.</div><div style="font-size:small" class="gmail_default">Next I want to add the "Contributors CV" line but I have not yet found the "merge" tar of around March 21, 2016 where CV, HV, and 5.0 were merged that was made for Beta testing of 5.1 and submitted (AND REJECTED) to Cinelerra-CV. But I have not looked very hard yet other than in the email here. I need this in order to determine the exact files that were used from CV.<br></div><div style="font-size:small" class="gmail_default">Question? did you come up with a good date for CV contributors? Or should I use 2007-2016?<br></div></div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Cinelerra CV was active as project since early 2003 (cinelerra 1.1.* days!) first in cvs, then in svn, then in git.</div><div dir="auto"><br></div><div dir="auto">Try to download full history via git clone </div><div dir="auto"><br></div><div dir="auto"><a href="https://github.com/cinelerra-cv-team/cinelerra-cv" rel="noreferrer noreferrer" target="_blank">https://github.com/cinelerra-cv-team/cinelerra-cv</a><br></div><div dir="auto"><br></div><div dir="auto">git log in it, and then press "end" on keyboard.</div><div dir="auto">you will see lines like r2, r9, r11 - those are ancient CVS revisions.</div><div dir="auto"><br></div><div dir="auto">Now, one can wonder how much of this work survived into 2016? Files were merged with HV (and sometimes back) but for example autoconf-based build system was developed there and quite distinct from script HV uses. So, _as a team_ I think their contributions still alive even if it be quite hard to find exact lines from that time in current code. Yet, translations were merged there, manual in 2007 too.</div><div dir="auto"><br></div><div dir="auto">I wonder if manual a bit distinct and in our case heavy for referring from source code tree? I mean, files like AUTHORS put in root of source tree exactly because they more likely to read this way.</div><div dir="auto"><br></div><div dir="auto">Originally (if you check r2 by copying its git hash as argument to 'git checkout -b r2 hash') you will see AUTHORS was empty and was filled up lately</div><div dir="auto"><br></div><div dir="auto"><div dir="auto">commit 19c569148c0c2742a9dabb42ee281bf498eee291</div><div dir="auto">Author: Johannes Sixt <<a href="mailto:johannes.sixt@telecom.at">johannes.sixt@telecom.at</a>></div><div dir="auto">Date: Tue Jan 23 21:34:33 2007 +0000</div><div dir="auto"><br></div><div dir="auto"> r985: Fill in the AUTHORS file with useful information.</div><div dir="auto"><br></div><div dir="auto"> This file is used by a svn to git converter; hence, it must have this particular syntax, which maps svn committer logins to names and emails.</div><div dir="auto"><br></div><div dir="auto"> On the other hand, since this file lists only the svn logins, it is by no means a complete list of authors. Many people have contributed, but are not mentioned here. If you think you deserve attribution in this list, it will be no problem to add your name, too (with some fake login name).</div><div dir="auto"><br></div><div dir="auto">=====</div><div dir="auto">I think we do not plan to downgrade to SVN so our file might be simpler in organization. Just authors, contact. (contact is email or website)</div><div dir="auto"><br></div><div dir="auto">please also try to git log in unpacked google code archive, it provides some info on merges before attempted beta release ( I'll look up email archive at date you found)</div></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="auto"><div style="font-size:small" class="gmail_default"></div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>
</blockquote></div></div></div>