Welcome, Guest
Username: Password:

TOPIC: Withdrawing 2.0a and the reasons behind it

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68727

  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey Team
  • Posts: 986
  • Thank you received: 134
  • Karma: 97
Article cannot be shown
Best regards

Carsten Schmitz
LimeSurvey project leader
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68902

  • joer
  • joer's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 4
  • Karma: 0
Why don't you reconsider your own licensing policy?
Seems to me like LimeSurvey could benefit from that change, given its current state.
It's a relatively mature product, its popularity continues to grow, and it's in desperate need for all the good stuff you put into 2.0.
I believe that such a change could accelerate even further the development and adoption of LimeSurvey.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68904

  • Mazi
  • Mazi's Avatar
  • Online
  • LimeSurvey Team
  • Posts: 5965
  • Thank you received: 364
  • Karma: 259
Licensing is a difficult topic. For our users to be future save we always stated that we will stick to the GPL license and we want to keep our promise.
So what alternative license would you suggest, joer?

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)limesurvey.org'"
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68918

  • joer
  • joer's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 4
  • Karma: 0
I would probably go with something less restrictive such as Apache, BSD, or MIT. This could make it easier for people to develop commercial products around LimeSurvey.
Regarding your past commitment to GPL, why don't you run a poll and see what your community members think?
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68934

  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey Team
  • Posts: 986
  • Thank you received: 134
  • Karma: 97
Joer, as pointed out in the article we can't just change the license.

Past contributors contributed under the GPL license so we are committed to it unless we find out how much contributed stuff is in the current source code and then ask every past relevant contributor if they agree to the license change - which is hardly possible.
Best regards

Carsten Schmitz
LimeSurvey project leader
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68937

  • Mazi
  • Mazi's Avatar
  • Online
  • LimeSurvey Team
  • Posts: 5965
  • Thank you received: 364
  • Karma: 259
So you think GPL is too restrictive? At what parts?

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)limesurvey.org'"
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68944

  • DenisChenu
  • DenisChenu's Avatar
  • Offline
  • Moderator Lime
  • Posts: 8931
  • Thank you received: 1249
  • Karma: 371
joer wrote:
I would probably go with something less restrictive such as Apache, BSD, or MIT. This could make it easier for people to develop commercial products around LimeSurvey.
You can develop commercial product, just you can sell bin without source code.

And LS aren't in AGPL, then you can send housing survey without distribute the source code. I think it's unethical but it's OK.

GPL don't restrict selling of products.

Denis

PS: et comme on dit en français : oh le gros troll GPL vs BSD :laugh:
Last Edit: 4 years 6 months ago by DenisChenu.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68946

  • joer
  • joer's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 4
  • Karma: 0
Yes, for derived work.
In my case there are parts I will be happy to open source and parts that I can't.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68985

  • ltsd
  • ltsd's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 1
  • Karma: 0
If you do have to re-write in a new framework, my vote would definitely be for Yii. This whole issue with the CI license could even turn out for the best in the long run ;)

I do feel sorry for all the people who have put in a lot of hard work developing 2.0 and I do hope all their work will not be in vain.
Last Edit: 4 years 6 months ago by ltsd. Reason: missed something
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68995

  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey Team
  • Posts: 986
  • Thank you received: 134
  • Karma: 97
ltsd: I am tending towards Yii, too - mainly because it has almost the same feature set as Symfony2 but seems a little easier to learn.
Do you have any experience with Yii in comparison to other frameworks?
Best regards

Carsten Schmitz
LimeSurvey project leader
Last Edit: 4 years 6 months ago by c_schmitz.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #68996

  • DenisChenu
  • DenisChenu's Avatar
  • Offline
  • Moderator Lime
  • Posts: 8931
  • Thank you received: 1249
  • Karma: 371
Hello,

I have just a question for the actual distribution LS 2.0a.

Can we have CI with is own Licence, and LS file in GPL licence ?

For example : you have some Windows tools with Open Source licence , but use Proprietary " FrameWork".

I don't know if there are a forum post from CI team for this.

I think it best to take a clean GPL-compatible licence for future, but i ask only for 2.0a actual development.

Thank.

PS:
Yii : BSD licence
Symphony : MIT licence
Last Edit: 4 years 6 months ago by DenisChenu.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #69006

  • holch
  • holch's Avatar
  • Offline
  • LimeSurvey Team
  • Posts: 4895
  • Thank you received: 718
  • Karma: 218
That is really bad news and I was really looking forward to the new 2.0 version. However, on the other hand that still came at a relatively good moment. Imagine being already a year into development and this comes up? Of course, quite a lot of work from the Summer of Code is getting lost, but better have to switch now than later.

Unfortunately I can't be of much help here, as I am not really a developer.
Have a look at the manual! It is a really valuable source for information. Here some helpful links:
Manual (EN) | Question Types | Question Attributes | Workarounds

If you found this answer helpful and it saved you some time please consider a donation to the project to keep Limesurvey going!
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #69010

  • crafter
  • crafter's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 17
  • Thank you received: 1
  • Karma: 0
There are two issues for discussion here. One is the licensing issue and the second the response to the withdrawing version 2

The licensing issue is an issue faced by CI, not Limesurvey, and as I can gather here, there is reluctance to change this. I suggest that issue of licensing be discussed of LimeSurvey, but outside the context of the recent events.

Regarding the version 2.0 changes and the withdrawal, I respect that decision as the feedback seems to suggest that the steps were taken in the best interest of the project.

Under the CURRENT CI licensing, we must assume (but clarify) that the code for 2.0 is licensed under the GPL. If so, then changing the code to fit into another framework should be no big issue.

While discussing the issue of alternative framework, we need to detirmine whether the project move to a new framework for the sake of having a framework.

Why not develop a homegrown MVC framework. I developed a very basic one with about a hundred lines of code. Here are some consideration.
- The framework supplies the mechanism for the separation of code.
- Third party libraries can be added as required. This will replace the
plugins, libraries features of current MVC frameworks.
- Views will be compatible with the CI views (after all, they are just PHP documents, rendered using a simple include_once() ).
- Models can use PDO. No need to complex database abstraction libraries, but that can be provided if required in any case.

I'd like to now what others think.
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #69015

  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey Team
  • Posts: 986
  • Thank you received: 134
  • Karma: 97
Sorry crafter,

but I am not ready to re-invent the wheel here by homegrowing a framework. There are many good alternatives out there.
Best regards

Carsten Schmitz
LimeSurvey project leader
The administrator has disabled public write access.

Withdrawing 2.0a and the reasons behind it 4 years 6 months ago #69029

  • crafter
  • crafter's Avatar
  • Offline
  • Fresh Lemon
  • Posts: 17
  • Thank you received: 1
  • Karma: 0
Then it that case in light of the licensing issue, and in consideration of the framework features and maturity, I will provide favorable votes to :
- cake framework - MIT license
- Yii - BSD license.
Last Edit: 4 years 6 months ago by crafter. Reason: spell
The administrator has disabled public write access.
Time to create page: 0.313 seconds