Hallo Alle,
zur Info:
Wie ist Eure Meinung?
Eine laufende Diskussion findet Ihr auch im englischen Forum.
Gruß,
Thomas E.-E.
zur Info:
All,
With some of you we already had discussions around the GPL license of openHAB and that this is quite restrictive. From the start we made sure to have the option to move to the less restrictive EPL license one day. Well, we think this day might have come - the main reason for the GPL license (the fact that the KNX Calimero library was only available under GPL without a classpath exception) is obsolete for a while and so we are considering moving openHAB to the EPL license and would like to have your feedback on this.
Actually, we have the opportunity to go even a step further than just switching the license - we have the chance to move the core framework of openHAB to the Eclipse Foundation altogether.
Eclipse is currently expanding in the IoT/M2M space (see Eclipse M2M Initiative Gains Momentum with New Projects, Members and Commercial Adoption) and we are in talks to propose a new "Eclipse Smart Home" project with the openHAB core as the initial contribution.
The idea is to have all core/framework things at Eclipse - things like the ItemRegistry, PersistenceManager, editors, etc. More or less what is part of the runtime and designer distribution files. Having a new home at Eclipse for these things would not only mean that they are under EPL, but also that there is a strict IP check on them and that they are "safe" to use open source code - for inclusion in products, research and whereever. We had many complaints that the current GPL prevents using (and thus contributing to) openHAB due to rules by many legal departments. Code hosted at the Eclipse Foundation in contrast can be generally considered to be safe to use. Besides these aspects, being part of the Eclipse Foundation will definitely bring a lot more publicity to the project.
openHAB would still continue to exist and it would host all addons (bindings, actions, persistence services, etc.) and provide a full distribution just as today. The code of a few strategic addons might also be moved to Eclipse, but many of them include third-party libraries that possible would never be possible to have in an Eclipse project, so openHAB is a much better place for them. The effect on openHAB would be that - similar as it currently makes use of the Eclipse Modelling Framework, Eclipse Xtext, Eclipse Jetty, etc -, it would make use of Eclipse Smart Home and thus have less code itself. Together with this refactoring we would still switch the openHAB (addons) code to EPL and possibly also change to GitHub or BitBucket and a Git repository (as this is another demand from many users).
All of this would happen AFTER the 1.3 release, which is planned for September.
I would be very interested in your opinion, if this is an interesting path to follow and if you all would support us with this approach!
Kind regards,
Kai
With some of you we already had discussions around the GPL license of openHAB and that this is quite restrictive. From the start we made sure to have the option to move to the less restrictive EPL license one day. Well, we think this day might have come - the main reason for the GPL license (the fact that the KNX Calimero library was only available under GPL without a classpath exception) is obsolete for a while and so we are considering moving openHAB to the EPL license and would like to have your feedback on this.
Actually, we have the opportunity to go even a step further than just switching the license - we have the chance to move the core framework of openHAB to the Eclipse Foundation altogether.
Eclipse is currently expanding in the IoT/M2M space (see Eclipse M2M Initiative Gains Momentum with New Projects, Members and Commercial Adoption) and we are in talks to propose a new "Eclipse Smart Home" project with the openHAB core as the initial contribution.
The idea is to have all core/framework things at Eclipse - things like the ItemRegistry, PersistenceManager, editors, etc. More or less what is part of the runtime and designer distribution files. Having a new home at Eclipse for these things would not only mean that they are under EPL, but also that there is a strict IP check on them and that they are "safe" to use open source code - for inclusion in products, research and whereever. We had many complaints that the current GPL prevents using (and thus contributing to) openHAB due to rules by many legal departments. Code hosted at the Eclipse Foundation in contrast can be generally considered to be safe to use. Besides these aspects, being part of the Eclipse Foundation will definitely bring a lot more publicity to the project.
openHAB would still continue to exist and it would host all addons (bindings, actions, persistence services, etc.) and provide a full distribution just as today. The code of a few strategic addons might also be moved to Eclipse, but many of them include third-party libraries that possible would never be possible to have in an Eclipse project, so openHAB is a much better place for them. The effect on openHAB would be that - similar as it currently makes use of the Eclipse Modelling Framework, Eclipse Xtext, Eclipse Jetty, etc -, it would make use of Eclipse Smart Home and thus have less code itself. Together with this refactoring we would still switch the openHAB (addons) code to EPL and possibly also change to GitHub or BitBucket and a Git repository (as this is another demand from many users).
All of this would happen AFTER the 1.3 release, which is planned for September.
I would be very interested in your opinion, if this is an interesting path to follow and if you all would support us with this approach!
Kind regards,
Kai
Eine laufende Diskussion findet Ihr auch im englischen Forum.
Gruß,
Thomas E.-E.
Kommentar