Hi, I've been lurking on the discussion and while I don't have much time/energy or practical skills to contribute in the future development, I find it thrilling that plans for the project future are being made.
I think it's alarming, though, that the project facilities (JIRA has been mentioned several times) obstruct rather than support development work. Ensuring project momentum should be the first priority when picking the tools and surroundings to work in. Assuming that there has been no practical synergy benefits with sharing the same bugtracker with Qt Project, I don't see why any other bugtracker couldn't be used for the project (as long as someone is happy to take over the hosting and maintenance responsibilities). Same goes with other facilities as well. If a switch from Gerrit to e.g. GitHub would take place, however, that'd imply a bigger separation from Qt Project itself (due to licensing issues). If you want to do that, I'd warmly recommend having first a discussion with Lars Knoll and esp. Digia's Tuukka Turunen to ensure that they have no objections or alternative proposals. Digia might still be interested in providing commercial support or licenses for PySide, and moving away from Gerrit would prevent them from doing that. Still, even that's just a decision to be made, if the core contributors feel the current Gerrit setup is counterproductive for the project purposes. But at least discuss first with Qt Project and Digia... Cheers, ma. On 10 December 2012 18:26, John Ehresman <j...@wingware.com> wrote: > On 12/10/12 8:38 AM, Hugo Parente Lima wrote: > > Is normal, our the binding generator code base is a mess to > > understand due to various historical events occurred during the > > development, in the ideal world the generator would be written in > > Python with a clean code base, just the helper libraries in C++ > > (libshiboken and libpyside), but this would require a full rewrite > > of the generator :-/. Our typesystem file inherited from Qt-Jambi > > is also not the better way to give hints to the generator about how > > to generate bindings. > > My thought on the code generator was to have the C++ parser write the > parse tree out to some xml file that could then be read by a code > generator written in python. Then the C++ parser could possibly be > replaced with something else and the generator could be more quickly > improved since it's now implemented in python. Changing it would > still require C++ knowledge, though, because it's emitting C++ code. > > > There are a lot of bug reports, but the Jira bug tracker is > > horrible to search bugs, change bug status, etc... > > Is there anyone on this list that knows enough about the bug tracker > to help people learn how to use it effectively? I think I gave up > when I tried to close one of the bugs I reported and couldn't figure > out how to do it. Or should we be looking for another tracker? > > Cheers, > > John > _______________________________________________ > PySide mailing list > PySide@qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside > -- -- Matti Airas +358 50 484 0973
_______________________________________________ PySide mailing list PySide@qt-project.org http://lists.qt-project.org/mailman/listinfo/pyside
