Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL? Josef -- Josef Reidinger Appliance Toolkit team maintaining parts of webyast and SLMS author of rubygems - studio_api and net_observer (coauthor) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday 25 of August 2011 13:52:27 Josef Reidinger wrote:
Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL?
MIT or LGPL sound good. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday 25 of August 2011 14:29:52 Thomas Goettlicher wrote:
On Thursday, August 25, 2011 01:52:27 pm Josef Reidinger wrote:
Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL? Josef
I talked to our licenses expert and want to summarize the outcome of the discussion: There are a lot of different possibilities and GPL v3 fits well for yast++. Libraries could be LGPL v3 if they are used by others. Otherwise GPL v3 is also appropriate.
Do we want others to use our framework libraries and do not open the code? Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday, August 25, 2011 01:52:27 pm Josef Reidinger wrote:
Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL? Josef I talked to our licenses expert and want to summarize the outcome of the discussion: There are a lot of different possibilities and GPL v3 fits well for yast++. Libraries could be LGPL v3 if they are used by others. Otherwise GPL v3 is also appropriate.
Cheers, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday, August 25, 2011 08:44:08 am Stanislav Visnovsky wrote:
On Thursday 25 of August 2011 14:29:52 Thomas Goettlicher wrote:
On Thursday, August 25, 2011 01:52:27 pm Josef Reidinger wrote:
Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL? Josef
I talked to our licenses expert and want to summarize the outcome of the discussion: There are a lot of different possibilities and GPL v3 fits well for yast++. Libraries could be LGPL v3 if they are used by others. Otherwise GPL v3 is also appropriate.
Do we want others to use our framework libraries and do not open the code? LGPL might help to distribute yast++ among different system. Anyways I think GPLv3 should be sufficient.
BTW: Your time settings seems to be wrong. Is your workstation's clock correct? Cheers, Thomas
Stano
-- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Thomas Goettlicher write:
On Thursday, August 25, 2011 08:44:08 am Stanislav Visnovsky wrote:
On Thursday 25 of August 2011 14:29:52 Thomas Goettlicher wrote:
On Thursday, August 25, 2011 01:52:27 pm Josef Reidinger wrote:
Hi, second question related to yast++. What license we should use? As I plan to create initial package, I need specify license ( and packaging tasks include explicit license checker ). What suggestion do you have? MIT, BSD or some kind of GPL? Josef
I talked to our licenses expert and want to summarize the outcome of the discussion: There are a lot of different possibilities and GPL v3 fits well for yast++. Libraries could be LGPL v3 if they are used by others. Otherwise GPL v3 is also appropriate.
Do we want others to use our framework libraries and do not open the code? LGPL might help to distribute yast++ among different system. Anyways I think GPLv3 should be sufficient.
BTW: Your time settings seems to be wrong. Is your workstation's clock correct?
Cheers, Thomas
Stano
Because both agents and yast++ libraries will be libraries which will be fine if use our customers for theirs solutions I found LGPL useful license. I try to discuss it on monday with jsrain and decide some license ( as long as we don't have external contributor we can freely change license ). I want initial version to create initial package for introduction and testing. Josef -- Josef Reidinger Appliance Toolkit team maintaining parts of webyast and SLMS author of rubygems - studio_api and net_observer (coauthor) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Josef Reidinger -
Stanislav Visnovsky -
Thomas Goettlicher