Hi people,
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
Cheers, Frank
Am 08.04.2011 18:18, schrieb Frank Lanitz:
Hi people,
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
I never heard of licenses for newsletters.
Best regards.
Am Freitag, den 08.04.2011, 18:28 +0200 schrieb Thomas Martitz:
Am 08.04.2011 18:18, schrieb Frank Lanitz:
Hi people,
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
I never heard of licenses for newsletters.
Me neither.
On Friday 08 April 2011 01:54:13 pm Dominic Hopf wrote:
Am Freitag, den 08.04.2011, 18:28 +0200 schrieb Thomas Martitz:
I never heard of licenses for newsletters.
Me neither.
Well, it is written material, and, automatically (iiuc, according to the Berne Treaty) subject to copyright (i.e., it is copyrighted). So, who/how do you want to allow anyone else to use it?
That's what a license is. If you don't specify a license, I guess (I think) no one has a right to copy and use it for any purpose, but, ianal (i am not a liar^H^H^H^Hlawyer).
So, you can certainly apply a license, and that would seem to be better than not applying a license, with possible arguments after someone has done something with the content which you (collectively) don't wish done.
Randy Kramer
On Fri, 8 Apr 2011 13:45:12 -0500 Randy Kramer rhkramer@gmail.com wrote:
On Friday 08 April 2011 01:54:13 pm Dominic Hopf wrote:
Am Freitag, den 08.04.2011, 18:28 +0200 schrieb Thomas Martitz:
I never heard of licenses for newsletters.
Me neither.
Well, it is written material, and, automatically (iiuc, according to the Berne Treaty) subject to copyright (i.e., it is copyrighted). So, who/how do you want to allow anyone else to use it?
That's what a license is. If you don't specify a license, I guess (I think) no one has a right to copy and use it for any purpose, but, ianal (i am not a liar^H^H^H^Hlawyer).
Yepp. That is issue I had in my mind.
Cheers, Frank
Le 08/04/2011 18:18, Frank Lanitz a écrit :
Hi people,
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
I'd be fine with it. Actually, I don't care much as far as it allows free redistribution (with or without modifications, I know the arguments for both and here don't have an opinion).
Cheers, Colomban
On 04/08/11 09:18, Frank Lanitz wrote:
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
Anything with free distribution seems reasonable. I'm not sure why modification permissions would need to available, just for the sake of keeping each issue "a slice in time" and/or not to be mangled out of context, but it's probably no big deal anyway.
http://creativecommons.org/choose/
Cheers, Matthew Brush
On 9 April 2011 08:39, Matthew Brush mbrush@codebrainz.ca wrote:
On 04/08/11 09:18, Frank Lanitz wrote:
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
Anything with free distribution seems reasonable. I'm not sure why modification permissions would need to available, just for the sake of keeping each issue "a slice in time" and/or not to be mangled out of context, but it's probably no big deal anyway.
Well IIUC without modification I couldn't use just part of the newsletter, so I couldn't just distribute the tutorials for example, I 'd have to distribute the whole thing.
Cheers Lex
http://creativecommons.org/choose/
Cheers, Matthew Brush _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sat, 9 Apr 2011 10:01:25 +1000 Lex Trotman elextr@gmail.com wrote:
On 9 April 2011 08:39, Matthew Brush mbrush@codebrainz.ca wrote:
On 04/08/11 09:18, Frank Lanitz wrote:
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
Anything with free distribution seems reasonable. I'm not sure why modification permissions would need to available, just for the sake of keeping each issue "a slice in time" and/or not to be mangled out of context, but it's probably no big deal anyway.
Well IIUC without modification I couldn't use just part of the newsletter, so I couldn't just distribute the tutorials for example, I 'd have to distribute the whole thing.
But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like flavor of CC.
I don't think NC or ND is making any big sense.
Cheers, Frank
But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like flavor of CC.
Yes, CC-BY allows modification. IIUC CC-BY-SA would preclude any more than "fair use" quantities of material anywhere that is not itself licensed by CC_BY_SA. For example this might preclude use of newsletter articles on software blogging sites if they have non-CC-BY-SA licenses. So I am not in favor of CC-BY-SA.
If using CC-BY how should attribution be required? Perhaps "Geany newsletter team" and (if online) link to Geany website.
I don't think NC or ND is making any big sense.
Agree, the point of the newsletter is to get distributed.
Cheers Lex
On Sat, 9 Apr 2011 11:17:20 +1000 Lex Trotman elextr@gmail.com wrote:
But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like flavor of CC.
Yes, CC-BY allows modification. IIUC CC-BY-SA would preclude any more than "fair use" quantities of material anywhere that is not itself licensed by CC_BY_SA. For example this might preclude use of newsletter articles on software blogging sites if they have non-CC-BY-SA licenses. So I am not in favor of CC-BY-SA.
Well, I think its not 100% true. Short, you can do what every you want with it if you keep points in mind: BY and redistribute derivates and the original by CC-BY-SA. This is not enforcing you to move your whole blog to CC.
If using CC-BY how should attribution be required? Perhaps "Geany newsletter team" and (if online) link to Geany website.
Yepp, that's what I had in my mind.
Cheers, Frank
On 9 April 2011 18:31, Frank Lanitz frank@frank.uvena.de wrote:
On Sat, 9 Apr 2011 11:17:20 +1000 Lex Trotman elextr@gmail.com wrote:
But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like flavor of CC.
Yes, CC-BY allows modification. IIUC CC-BY-SA would preclude any more than "fair use" quantities of material anywhere that is not itself licensed by CC_BY_SA. For example this might preclude use of newsletter articles on software blogging sites if they have non-CC-BY-SA licenses. So I am not in favor of CC-BY-SA.
Well, I think its not 100% true. Short, you can do what every you want with it if you keep points in mind: BY and redistribute derivates and the original by CC-BY-SA. This is not enforcing you to move your whole blog to CC.
Quote CC-BY-SA "All new works based on yours will carry the same license,", IIUC a blog that contains significant content becomes a derivative work, and so has to have CC-BY-SA as well. But most blog sites (especially ones hosted by others, usually have other licenses and terms and conditions that make it hard to change just one blog to a different license.
Cheers Lex
If using CC-BY how should attribution be required? Perhaps "Geany newsletter team" and (if online) link to Geany website.
Yepp, that's what I had in my mind.
Cheers, Frank -- http://frank.uvena.de/en/
Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On 04/08/11 17:01, Lex Trotman wrote:
On 9 April 2011 08:39, Matthew Brushmbrush@codebrainz.ca wrote:
On 04/08/11 09:18, Frank Lanitz wrote:
I just want to ask about which license we shall use for the newsletter in future. I'd like to prefer to put it under terms of one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most IMHO. What's your opinion?
Anything with free distribution seems reasonable. I'm not sure why modification permissions would need to available, just for the sake of keeping each issue "a slice in time" and/or not to be mangled out of context, but it's probably no big deal anyway.
Well IIUC without modification I couldn't use just part of the newsletter, so I couldn't just distribute the `rm -rf /` tutorials for example, I'd have to distribute the whole thing.
Gotcha. As far as any contributions I have/will make, any of those licenses are fine with me.
Cheers, Matthew Brush