Hi, 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.
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. :-) Cheers, ma. On 11 July 2013 23:27, John Ehresman <j...@wingware.com> wrote: > At the sprint in Austin, a few of us discussed moving the git repository > where changes are made to github. We would still limit who could push > to a core group of approvers and require someone else to review changes > in almost all cases. The goal is to move away from gerrit / gitorious > to the github tools. Each of us has limited time to contribute to > PySide and we'd rather spend that time improving PySide rather than > learning how to use tools we don't otherwise use. > > What to do with the bug tracker is less clear. It probably would > migrate to github's tracker or another tracker because the current > tracker doesn't work well, but OTOH no one is particularly impressed > with github's tracker. > > We decided to float this idea on email and see what the response was. > Any transition wouldn't happen for a few weeks and all patches should be > submitted via Gerrit until then. > > Cheers, > > John > _______________________________________________ > PySide mailing list > PySide@qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside >
_______________________________________________ PySide mailing list PySide@qt-project.org http://lists.qt-project.org/mailman/listinfo/pyside
