Planned maintenance has been done but it did not solve the problem. So work will continue on this and a new time for trying updates will be announced asap.
Publish customized/forked component library under LGPL
fiddlingAround last edited by
I am not a professional developer, but I like experimenting with different technologies.
After doing some scripting in Python I came to Qt for a small amateur project.
My project is a library of GUI components based on the source of the discontinued library "Symbian Components" by Nokia.
I cloned the repository and started to customize most of the components and made them work with Qt5. Some of the source files remained untouched.
May I call it a fork? There are some other sources, too.
In the distant future I would like to publish this derivative work under the LGPL so other people can use my components to create GUIs.
Currently my project is mixture of differently licenced sources.
Only some selected examples:
Symbian Components by Nokia, discontinued
Button.qml, License: BSD
SDeclarativeImageProvider, License: BSD
Qt Quick Components by Digia
QQuickRangeModel, License: LGPL/GPL
QQuickFolderListModel, License: LGPL/GPL
Ubuntu UI Toolkit by Canonical Ltd.
QuickUtils, License: LGPL/GPL
I copied miscellaneous features into my project, because it is not possible to ensure their availability on all platforms out-of-the-box and without installing additional dependencies.
To cut a long story short:
Is it possible to "relicence" my customized "mixture" under LGPL? What do I have to consider before release? What should the ?new? licence headers look like in my source files?
I found a similar question in the forums, which refers to discontinued parts of the Qt framework itself and not projects using Qt.
"Licensing for discontinued Qt Solutions projects"
Thanks in advance
PS: I love Qt very much and appreciate the outstanding work on it! Keep on rocking!