This is certainly a valid point. So I guess this means that a decision about whether a feature should be contributed to Qt or kept as a 3rd party addon should be made early on. Il 28 giu 2016 10:09 AM, "Kai Koehne" <kai.koe...@qt.io> ha scritto:
> -----Original Message----- > From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org] > On Behalf Of Marco Piccolino > Sent: Tuesday, June 28, 2016 9:07 AM > To: Shawn Rutledge <shawn.rutle...@qt.io> > Cc: interest@qt-project.org > Subject: Re: [Interest] 5.8 Features? > > I see inclusion into Qt as a second step and only for functionality that will be > needed by nearly everybody working on mobile. I meant that being it github > projects, everyone can contribute. Well, the problem is that if you/we decide after some time to move some of the code into Qt, we'd need every single contributor to sign the Qt Contribution Agreement. This can be hard especially for github contributions, where all you have of a contributor at times is the github account. That's why it's highly encouraged to use the Qt project infrastructure from the start. This doesn't mean that it instantly has to be part of Qt releases, or follow the Qt release schedule. We also have lots of 'playground' modules. See also https://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt Regards Kai
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
