2.6 avisynth.h is temporarily under full GPL

IanB · 8th May 2007, 08:51

Dear Fellow Developers,

I have temporarily removed the GPL exemption from my latest Avisynth.h.

This means anybody publishing software that uses my code from these versions of Avisynth.h must also publish the full source code.

I do this because I am about to rip the guts out of the interface and I want access to the source of any published 2.6 plugins while development is progressing.

When I get the new code correct I will restore the normal avisynth GPL exemption.

The licences conditions of other versions of Avisynth.h, including my earlier contributions, are unchanged.

Thank you for your support,
IanB

Fizick · 8th May 2007, 11:01

Ian,
please create some tag or branch at CVS with current state of 2.6 sources (before exemptions removing).
Can you say how do you want to break Avisynth 2.6 pre-alpha?

Ignus2 · 8th May 2007, 19:42

Could you also update the avisynth C interface file? It is missing some declarations, for example the Y8 video format related defines and functions.

That would be a nice thing, as we're using the C interface for all our plugins.

--
Greets,
I.

d'Oursse · 12th May 2007, 06:38

Why not using the LGPL ? As Avisynth is a library, with the LGPL, it can be linked wih other projects using non GPL licence

Fizick · 12th May 2007, 13:53

d'Oursse,
GPL was Ben's decision. We may not to change it.

d'Oursse · 12th May 2007, 14:07

did you keep any part of his code ? If not, you are free to change the licence, if I'm not mistaken

MfA · 12th May 2007, 20:15

Meh, if someone is hard up for using the library under the LGPL license let them do all the work of tracking down the sources of all the code and asking them for permission. It's not like it's a small task.

stickboy · 21st May 2007, 07:29

Why not ask developers not to write plug-ins against the unstable interface yet?

It's not like you can stop people from writing plug-ins against a different version of avisynth.h (2.6 or otherwise) that contains the exemption. If those plug-ins become broken, it's the authors' own fault for not listening.

Changing the licensing terms (and then changing them back) seems like a strange and heavy-handed way of doing this. IMO, it'd potentially upset people on the way in (anyone who doesn't actively read this forum would think it's a clandestine attempt at shoving the GPL down people's throats) and on the way out (potentially someone could modify avisynth.h in the interim unaware of the intended exemption). The latter case admittedly is contrived, since in practice only a handful of people would be touching avisynth.h (and possibly only you), but it seems like a can of worms better left avoiding if possible.

8th May 2007, 08:51	#1 \| Link
IanB Avisynth Developer Join Date: Jan 2003 Location: Melbourne, Australia Posts: 3,167	2.6 avisynth.h is temporarily under full GPL Dear Fellow Developers, I have temporarily removed the GPL exemption from my latest Avisynth.h. This means anybody publishing software that uses my code from these versions of Avisynth.h must also publish the full source code. I do this because I am about to rip the guts out of the interface and I want access to the source of any published 2.6 plugins while development is progressing. When I get the new code correct I will restore the normal avisynth GPL exemption. The licences conditions of other versions of Avisynth.h, including my earlier contributions, are unchanged. Thank you for your support, IanB

8th May 2007, 11:01	#2 \| Link
Fizick AviSynth plugger Join Date: Nov 2003 Location: Russia Posts: 2,183	Ian, please create some tag or branch at CVS with current state of 2.6 sources (before exemptions removing). Can you say how do you want to break Avisynth 2.6 pre-alpha? __________________ My Avisynth plugins are now at http://avisynth.org.ru and mirror at http://avisynth.nl/users/fizick I usually do not provide a technical support in private messages.

12th May 2007, 13:53	#5 \| Link
Fizick AviSynth plugger Join Date: Nov 2003 Location: Russia Posts: 2,183	d'Oursse, GPL was Ben's decision. We may not to change it. __________________ My Avisynth plugins are now at http://avisynth.org.ru and mirror at http://avisynth.nl/users/fizick I usually do not provide a technical support in private messages.

8th May 2007, 19:42	#3 \| Link
Ignus2 Registered User Join Date: Dec 2005 Posts: 250	Could you also update the avisynth C interface file? It is missing some declarations, for example the Y8 video format related defines and functions. That would be a nice thing, as we're using the C interface for all our plugins. -- Greets, I.

12th May 2007, 06:38	#4 \| Link
d'Oursse Mushroomeur Join Date: Jun 2003 Location: Mushrooms of Paris Town Posts: 267	Why not using the LGPL ? As Avisynth is a library, with the LGPL, it can be linked wih other projects using non GPL licence

12th May 2007, 14:07	#6 \| Link
d'Oursse Mushroomeur Join Date: Jun 2003 Location: Mushrooms of Paris Town Posts: 267	did you keep any part of his code ? If not, you are free to change the licence, if I'm not mistaken

12th May 2007, 20:15	#7 \| Link
MfA Registered User Join Date: Mar 2002 Posts: 1,075	Meh, if someone is hard up for using the library under the LGPL license let them do all the work of tracking down the sources of all the code and asking them for permission. It's not like it's a small task.

21st May 2007, 07:29	#8 \| Link
stickboy AviSynth Enthusiast Join Date: Jul 2002 Location: California, U.S. Posts: 1,267	Why not ask developers not to write plug-ins against the unstable interface yet? It's not like you can stop people from writing plug-ins against a different version of avisynth.h (2.6 or otherwise) that contains the exemption. If those plug-ins become broken, it's the authors' own fault for not listening. Changing the licensing terms (and then changing them back) seems like a strange and heavy-handed way of doing this. IMO, it'd potentially upset people on the way in (anyone who doesn't actively read this forum would think it's a clandestine attempt at shoving the GPL down people's throats) and on the way out (potentially someone could modify avisynth.h in the interim unaware of the intended exemption). The latter case admittedly is contrived, since in practice only a handful of people would be touching avisynth.h (and possibly only you), but it seems like a can of worms better left avoiding if possible.