Task #10324
Alter Oryx ant buildscript
| Status: | Rejected | Start date: | 2010-10-18 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Rens Admiraal | % Done: | 0% |
|
| Category: | Backend Interface | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Oryx has a built script for the javascript files. We should somehow place the sources outside the normal extension folder (to prefend huge checkouts / extension size), and alter the build process so we can easily alter small Oryx source files if needed.
History
Updated by Rens Admiraal over 2 years ago
Note:
ant build-plugins
ant build-editor-core
Updated by Rens Admiraal over 2 years ago
- Status changed from Accepted to Rejected
No Oryx since we have licensing problems
Updated by Thomas Maroschik over 2 years ago
I thought oryx was licensed under MIT license, which allows even sublicensing? At which point does it confilct with TYPO3 GPL?
Updated by Rens Admiraal over 2 years ago
We need an upgrade to ExtJS 3.2.x or higher to apply to TYPO3 standards or Phoenix / FLOW3 standards if we want to forward port the kickstarter. We also want the prototyping out of it.
We contacted the developers of Oryx and asked if it's possible to upgrade to ExtJS 3.2.x and they said 'no'. ExtJS is published under another license than 2 which conflicts with their MIT license, and they do not have permission (or can not get permission) from all developers of their code to switch their license. So, they're stuck which makes integration a problem.
Updated by Thomas Maroschik over 2 years ago
This is bad news. I thought ExtJs 3 is GPLv3 licensed and the MIT License is according to http://en.wikipedia.org/wiki/MIT_License compatible with that. Maybe they are using
My feeling is rather, that the Oryx Team lost interest in further development. Are we able to fork it and develop it to our own interests?
Greetings,
Tom
Updated by Rens Admiraal over 2 years ago
@forking: it does not seem to be so :(