Re: [CinCVS] cinelerra gpl license header for review, sketch how to solve the license issues
Nicolas Maufrais wrote: > Hello Christian, > > On Sat, Mar 10, 2007 at 12:44:56AM +0100, Christian Thaeter wrote: >> This file is actually mostly rewritten by me so the 'et al.' is only a >> safety measure, but for other files I don't want to figure who else >> touched them manually. > > Is the 'et al' legal? Couldn't it be, how could I say, "dangerous"? I > mean, it's safer to get an exhaustive name of the people who > worked on the file. That's the way it should be done IMO. However, I > understand you're not sure about who wrote that file apart you... I am not lawyer while I suspect that the legality of such a clause depends on the legislation which is applied. But even if it is not valid it should only invalidate the 'et al.' clause and not the whole license notice. For the worst case, when it invalidates the whole license notice, then at least here in germany that means that the license is void, but copyrights are still at the authors, it will not fall into Public Domain or such. A potential user has to contact the Authors for legal licesnse terms. In the other case I am adding a copyright notice to code which is not completely written by me, this means if a original author gets upset because I forgotten to add him, he could probably sue me an claim that I stole his copyrighted material. With adding a 'et al.' (and this archived mailinglist thread) I could hopefully convince a judge that my intention was not to steal code. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] cinelerra gpl license header for review, sketch how to solve the license issues
Nicolas Maufrais wrote: Hello Christian, On Sat, Mar 10, 2007 at 12:44:56AM +0100, Christian Thaeter wrote: This file is actually mostly rewritten by me so the 'et al.' is only a safety measure, but for other files I don't want to figure who else touched them manually. Is the 'et al' legal? Et al. is completely legal. The only consequence it have it that the first person knows who touched the file and need to ask what should happen in any further license changes. Couldn't it be, how could I say, "dangerous"? I mean, it's safer to get an exhaustive name of the people who worked on the file. That's the way it should be done IMO. However, I understand you're not sure about who wrote that file apart you... IMHO smart - not safe. But don't forget that it won't safe you from death of authors and copyright transfer. If it gets GPL'ed, it will safe you only only because of the license. Stefan ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] cinelerra gpl license header for review, sketch how to solve the license issues
Hello Christian, On Sat, Mar 10, 2007 at 12:44:56AM +0100, Christian Thaeter wrote: > This file is actually mostly rewritten by me so the 'et al.' is only a > safety measure, but for other files I don't want to figure who else > touched them manually. Is the 'et al' legal? Couldn't it be, how could I say, "dangerous"? I mean, it's safer to get an exhaustive name of the people who worked on the file. That's the way it should be done IMO. However, I understand you're not sure about who wrote that file apart you... Anyway, here's a page about that subject which could interest you: http://www.gnu.org/prep/maintain/maintain.html#Legal-Matters Bye, Nicolas Maufrais. -- ~~ ~ BOYCOTT SUSE & NOVELL (C)(TM)(R) MICRO$OFT ~ ~~ ~I DO LIKE AND SUPPORT GPL VERSION 3 ~ ~~ ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] cinelerra gpl license header for review, sketch how to solve the license issues
Sorry, the topic gets boring but I added a license header to a C++
sourcefile (cinelerra/cache.C) I edited which reads:
/*
Copyright (C) Heroine Virtual Ltd.
1996-2006, Jack Crossfire <[EMAIL PROTECTED]>
Copyright (C) CinelerraCV
2007, Christian Thaeter <[EMAIL PROTECTED]>
et al.
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
This file is actually mostly rewritten by me so the 'et al.' is only a
safety measure, but for other files I don't want to figure who else
touched them manually.
I'll go on to add such to all files where I apply non-tivial edits, any
objections?
If anyone feels left out in some file, please notify me, I'll add you.
For future I would suggest the following (already sketched that on irc):
Write a smart script which can deduce licenses by:
- checking the type of file, we only handle text files,
binary files need exception rules
- grepping for copyright/license information in the file
- checking if the directory where the file is has a license file
- check against a manually maintained exception list
if the script can NOT safely figure out the license (ex: detected a
copyright note but no license, ...) then it should notify the user for
human inspection for adding it to the exception list after manual review.
if the script can safely figure out under which license a file falls
then use the SVN history to figure out who edited it when and in which
revision.
We need a list associating revisions with people for exceptional cases,
it could take file patterns(or regex) like this example:
# for all revisions all fonts belong to 'ms'
*: *.ttf:ms
# *:hv denotes a upstream merge,
# foo/bar.C:j6t was also edited by Johannes etc.
r1234: *:hv foo/bar.C:j6t ...
next we need an association of user and the license they usually use
ms FONTSEULA
hv GPL
j6t GPL
maybe also a syntax for exceptional licenses foo/barf.C:j6t!BSD
if the script detects a collision it should notify this for fixing in
the exclusion list.
having all this information (date/person) we can automatically construct
a copyright header including year('s) and person.
This is only a sketch, such a script should have some more logic and
should be applied in a 'dry-run' while developed. At least I think this
approach is much easier than manually reviewing the history of 5000+
files. Further the development and history of this script and its
exception list will be tracked in revision control this gives some open
and reviewable process and I also believe this way is far less prone of
human errors which will happen on a manual review.
Finally we should put a big DISCLAIMER into the sourcetree which
explains this process and note that anyone who spots a problem shall
notify us and it will be fixed.
So, now the bad news: When someone else starts it, I will help to work
out the details. But I will not code it! I will not participate in a
discussion if we could/should do it this way, just do it or leave it.
Christian
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] opening files
On Friday 09 March 2007 20:03, Mark Grieveson wrote: > Hello. I seem to be having problems opening movie files. I was expecting > to see layout of the frames of the movie, accompanied with a layout of the > sound file, but I don't see anything when I open a movie file. Is this > normal, or is something wrong? This is my first time using Cinelerra; so, > I'm not exactly sure what to expect (though, I did expect to see a little > more than nothing.) I'm using the version for Debian Etch > (2.1.02-svn20070221), from the repository given on the cinelerra.org site. Choose an appropriate "insertion strategy" in the file dialog. In any case, you find the files in the "Resources window", section "Media", that's the window that opens at the lower left by default. (See also the Window menu.) From there you can drag them to the timeline. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] opening files
Hello. I seem to be having problems opening movie files. I was expecting to see layout of the frames of the movie, accompanied with a layout of the sound file, but I don't see anything when I open a movie file. Is this normal, or is something wrong? This is my first time using Cinelerra; so, I'm not exactly sure what to expect (though, I did expect to see a little more than nothing.) I'm using the version for Debian Etch (2.1.02-svn20070221), from the repository given on the cinelerra.org site. Mark ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] SoC 2007
Il giorno mer, 07/03/2007 alle 21.30 +0100, Johannes Sixt ha scritto: > On Wednesday 07 March 2007 17:34, giskard wrote: > > i will start reading SoC docs, Johannes (and * project guys) do you are > > ok? > > I think I'm ok. I'm hoping that mentoring a project is not too time consuming. > > My favorite project is to make X11, X11-XV, and X11-GL drivers into a single > driver which decides at runtime which accelerations are available and > dynamically load GL libraries. That way it's not necessary to have separate > builds for OpenGL and non-OpenGL support. And it's also possible to make ATI > drivers work. hello, yesterday we had a meeting in #cinelerra. We talked about all possible project we can mentor for SoC 2007. Here is a "final" list: summary: opengl (j6t), firewire (j6t), unicode (j6), huffyyuv , media/footage management and tagging/filtering (cehteh) (don't sure if this i doable), transparent proxy (herman), And DVD-ready MPEG. (hermanr) i wrote final..but afaik minmax has some idea which wanted tell us. i will send another (bigger) mail today evening. If you want you can read irclogs.. :) -- ciao, giskard signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: [CinCVS] DVpro
Andraž Tori wrote: > On Fri, 2007-03-09 at 09:39 +1300, Edouard Chalaron wrote: >> Hi all >> Simple question : >> is DV50 supported under Cinelerra ? >> Thanks a lot > > simple answer: > no yesterday we talked about Google SoC 2007 projects, DV50 made it into the proprosals, there is some hope. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Blackmagic Intensity card
On Thu, 8 Mar 2007, Aaron Newcomb wrote > Anyone know whether this thing will run under Linux??? I am thinking > about getting an HD camera and would love to go directly in through > HDMI. > > http://www.blackmagic-design.com/products/intensity/ I've written a couple of time to Black Magic Design. They told they this time had got more requests from Linux users than previous. But they don't have plans to support Linux neither with binary drivers nor accept the Linux offer to develope open drivers as I suggeseted next (they are afraid revealing commercially sensitive intellectual property). I therefore stated and replied that Black Magic Design is just as prorietary as Pinnacle was. Once I bought the latter's DV500-DVD solution, but I've dropped it, as there was only support for Windows. Now I'm waiting on Intel's upcoming Santa Rosa (Centrino Pro) laptop platform with GMA X3000 and better video, a graphic solution which Intel does support with open drivers. Terje J. Hanssen - If they don't support Linux, don't support them ... ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
