Dear Pyside2 contributors,
As you might know, Pyside was originally developed for Nokia while it was the owner of the Qt technology. When Nokia sold Qt to Digia (and now The Qt Company), all the copyrights over the original Pyside code for Qt 4 got transferred to The Qt Company as well.
For different reasons, it was not possible for The Qt Company to push Pyside forward as much as we would have wished over the last few years. Fortunately this changed now, and The Qt Company is today in a position, where it can and will invest into Pyside. The goal is to ensure Pyside becomes a fully supported part of the Qt product family, with a similar development and licensing model as the rest of Qt. We want to make sure Pyside works on new Qt releases when they come out and are committed to invest long term into the technology.
To do so, requires us to be able to license Pyside in the same way as Qt itself, ie. under both open-source (LGPLv3) and commercial licensing terms. As you probably know, the Qt Company is doing this for Qt by developing the product together with the community/ecosystem on qt-project.org. The reason that development happens on qt-project.org is that patches pushed to it fall under a contribution agreement (see http://www.qt.io/contributionagreement/), allowing the Qt Company to also have a commercially supported version of Qt, which then funds a lot of the further development of the product. Please note that the contribution agreement is not a copyright assignment, so you as a contributor keep the full rights to the code you developed.
Pyside1 has always been hosted on qt-project.org. To make Pyside available for Qt 5 and a fully supported part of the Qt family will require us to develop it on qt-project under the Qt Contribution Agreement. Including the Pyside2 work in this project, would be a great way to kick start it and create a good and open ecosystem around it from the start.
We, Christian Tismer and the Qt Company, have already agreed to move Christian’s changes over and to work with the community to achieve this. We would like to ask you as a contributor to Pyside2 to also consider contributing your changes to this effort.
We believe there will be many advantages to the Pyside community with this move:
We sincerely hope you can help us by agreeing to contribute your changes to Pyside2 to this project, so that we can create the best Qt support for Python ever.
Please don’t hesitate to ask on this list, if you have any further questions. We would appreciate if you could provide us with feedback on this list or in private.
To show your support please create a Qt account under https://login.qt.io/register. Once the registration is complete you can use the Qt account credentials and log into Qt’s codereview tool where you have to accept the Contributor agreement. The acceptance process is described in http://www.qt.io/contributionagreement/.
We will then contact each of you individually with details on how to sign off on your own work within Qt’s code review system.
Thank you very much.
With best regards,
Lars Knoll Christian Tismer
Qt Chief Maintainer Main Pyside 2 Contributor
CTO, The Qt Company
Dear Pyside2 contributors,
As you might know, Pyside was originally developed for Nokia while it was the owner of the Qt technology. When Nokia sold Qt to Digia (and now The Qt Company), all the copyrights over the original Pyside code for Qt 4 got transferred to The Qt Company as well.
For different reasons, it was not possible for The Qt Company to push Pyside forward as much as we would have wished over the last few years. Fortunately this changed now, and The Qt Company is today in a position, where it can and will invest into Pyside. The goal is to ensure Pyside becomes a fully supported part of the Qt product family, with a similar development and licensing model as the rest of Qt. We want to make sure Pyside works on new Qt releases when they come out and are committed to invest long term into the technology.
To do so, requires us to be able to license Pyside in the same way as Qt itself, ie. under both open-source (LGPLv3) and commercial licensing terms. As you probably know, the Qt Company is doing this for Qt by developing the product together with the community/ecosystem on qt-project.org. The reason that development happens on qt-project.org is that patches pushed to it fall under a contribution agreement (see http://www.qt.io/contributionagreement/), allowing the Qt Company to also have a commercially supported version of Qt, which then funds a lot of the further development of the product. Please note that the contribution agreement is not a copyright assignment, so you as a contributor keep the full rights to the code you developed.
Pyside1 has always been hosted on qt-project.org. To make Pyside available for Qt 5 and a fully supported part of the Qt family will require us to develop it on qt-project under the Qt Contribution Agreement. Including the Pyside2 work in this project, would be a great way to kick start it and create a good and open ecosystem around it from the start.
We, Christian Tismer and the Qt Company, have already agreed to move Christian’s changes over and to work with the community to achieve this. We would like to ask you as a contributor to Pyside2 to also consider contributing your changes to this effort.
We believe there will be many advantages to the Pyside community with this move:
- The Qt Company will commit some developers full time, to help develop Pyside further.
- The goal is to make Pyside an integral part of new Qt releases.
- Pyside will get a lot more exposure to developers and end users when it becomes part of the officially supported Qt packages
- The Qt Company will invest into the required testing, QA infrastructure and people
- Full bug tracking through the Qt bug tracking system
...
This is huge!
About that elephant in the room, what will happen to PyQt?
--
You received this message because you are subscribed to the Google Groups "pyside-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyside-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Christian Tismer :^) tis...@stackless.com Software Consulting : http://www.stackless.com/ Karl-Liebknecht-Str. 121 : https://github.com/PySide 14482 Potsdam : GPG key -> 0xFB7BEE0E phone +49 173 24 18 776 fax +49 (30) 700143-0023
[copied from pysid...@googlegroups.com -- replies go there]
- The Qt Company will help to make sure that Pyside always works with the latest Qt releases
- Of course we will keep Pyside available under open source licensing terms, just as free as Qt itself
- Companies who require this can purchase a commercially licensed version of Pyside including commercial support
- More exposure and visibility to the people working on and contributing to Pyside
We sincerely hope you can help us by agreeing to contribute your changes to Pyside2 to this project, so that we can create the best Qt support for Python ever.
Please don’t hesitate to ask on this list, if you have any further questions. We would appreciate if you could provide us with feedback on this list or in private.
To show your support please create a Qt account under https://login.qt.io/register. Once the registration is complete you can use the Qt account credentials and log into Qt’s codereview tool where you have to accept the Contributor agreement. The acceptance process is described in http://www.qt.io/contributionagreement/.
We will then contact each of you individually with details on how to sign off on your own work within Qt’s code review system.
Thank you very much.
With best regards,
Lars Knoll Christian Tismer
Qt Chief Maintainer Main Pyside 2 Contributor
CTO, The Qt Company
--
You received this message because you are subscribed to the Google Groups "pyside-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyside-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
_______________________________________________
PySide mailing list
PyS...@qt-project.org
http://lists.qt-project.org/mailman/listinfo/pyside
Dear Pyside2 contributors,
[...]