[PySide] Move PySide development to github?
jpe at wingware.com
Fri Jul 12 17:49:29 CEST 2013
On 7/12/13 4:16 AM, Matti Airas wrote:
> Just note that moving from Qt's Gerrit to Github means moving away from
> the Qt Project: if the contributors don't go through the license
> agreement click-through at Gerrit, code pushed to Github cannot later on
> be merged back to Github.
Yes, this is correct: to maintain the current code licensing scheme we'd
need to make sure anyone who contributes code to Github had clicked
through the license agreement on Gerrit. I like to switch to Github
even if we do this. I could also see opening thing up a bit more with
PySide so that simple fixes could be accepted from the bug tracker (yes,
I realize that there's no clear definition of "simple").
> Having said that, I agree that Github works well and is used very widely
> in the community, and since Digia seems to have no interest in
> supporting PySide, the move probably would have a net positive effect
> for PySide development. Just wanted to make sure you're making a
> conscious decision about this. :-)
While I appreciate the help that the Qt project has given us, I don't
see it as a requirement that PySide remain under the Qt project umbrella.
More information about the PySide