On terça-feira, 17 de dezembro de 2013 12:15:37, Turunen Tuukka wrote: > >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.
Well, I'm the person who replied, so I just repeated here what I said there :-) > >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 > >hotfix). > > > >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. Patches should be upstreamed by authors whenever possible, and those authors need the right permissions if they developed something on behalf of a company. So maybe think of SailfishOS instead of Jolla: if someone other than a Jolla employee makes a fix for SailfishOS, the Jolla CCLA does not apply. That's how it will work for Qt on Tizen, since the people doing work there are doing on their own time, not sponsored by any company. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
