[Development] Qt Welcomed to the Tizen.org Infrastructure

Turunen Tuukka Tuukka.Turunen at digia.com
Tue Dec 17 13:15:37 CET 2013

On 17.12.2013 9.52, "Thiago Macieira" <thiago.macieira at intel.com> wrote:

>On terça-feira, 17 de dezembro de 2013 07:31:44, Turunen Tuukka wrote:
>> Hi,
>> Congratulations!
>> Now that Qt source code is hosted also with tizen.org, how is the plan
>> keep the Qt parts aligned upstream with Qt Project?
>> I do not know all details of tizen.org, but I think the only way to get
>> the modifications done there upstream to Qt Project is for the original
>> authors to contribute these? Or is there some agreement in tizen.org
>> would allow another person to do it? What is the criteria to decide
>> a change belongs to?
>> It is typically very valuable to be well aligned towards upstream,
>> hopefully this is the plan for Qt in tizen.org in the future as well?
>Tomasz asked the question on how to proceed on the Tizen dev mailing list.

Good. After there is decision, would be nice if someone following Tizen
lists send the outcome to Qt Project lists.

>Basically, the idea is that the porting work should happen on
>to be close to upstream (us). Every now and then, he'll pull from qt-
>project.org into tizen.org. Eventually, once things are stabilised, that
>should happen only after Qt releases.

Sounds good.

>Bug fixes might be developed on tizen.org, but they should be upstreamed
>to qt-
>project.org at the earliest opportunity, in the proper form (not as a
>That's more or less how Blackberry and Jolla are doing right now.

The difference is that since there is no corporate contribution agreement
for tizen.org, each fix has to be contributed to Qt Project by the
original author? This is not necessarily a problem if the work is
continuous, but an item we should follow carefully.



>Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list