diff options
-rw-r--r-- | meeting-logs/kde-project-meeting-summary-20090521.txt | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/meeting-logs/kde-project-meeting-summary-20090521.txt b/meeting-logs/kde-project-meeting-summary-20090521.txt index 30f2add..8b52f4f 100644 --- a/meeting-logs/kde-project-meeting-summary-20090521.txt +++ b/meeting-logs/kde-project-meeting-summary-20090521.txt @@ -58,3 +58,125 @@ so far done -> bugs from ppl with @sabayonlinux.org will be handled legitimely as our bugs and we will reflect them as HTs for kde team so we dont have recheck reported things (aka we trust sabayon devs :}) +------------------------------------------------ +Qt topics +------------------------------------------------ + +Rollcall Qt herd +---------------- + +- hwoarang, tampakrap, yngwin present +- carlo absent +- recruits wired, Pesa and spatz present + + +Meeting length +-------------- + +The KDE Project meeting was going on for too long, all agreed. It was suggested +that it would be good to have more frequent and shorter meetings. Also, Qt +topics could be discussed early in the meeting. Details will be discussed at +another time. + + +Phonon issues +------------- + +KDE herd has asked us to introduce a kde useflag for ebuilds depending on:: + || ( x11-libs/qt-phonon media-sound/phonon ) +so that media-sound/phonon can be preferred for KDE users, as a workaround for +current portage shortcomings. yngwin will work out a proposal for affected Qt +ebuilds. + +Also, the suggestion was offered to split the backends from phonon into +separate packages (gstreamer from qt-phonon, and xine from kde's phonon), so we +could have one phonon core package (most likely x11-libs/qt-phonon). It was +decided that this is worth looking into. + + +Recruits +-------- + +As to the status of recruits for the Qt team: + +- wired is done with the quizzes, so he only needs grilling by a recruiter and + can be expected to become a full dev within the next few weeks +- Pesa has been very active already in contributing +- spatz just joined us as newest recruit +- sping is busy with GSoC and will continue recruitment process after that, he + is especially interested in Qt3/KDE3 maintenance + + +Qt status in tree +----------------- + +- bug 266201: 4.5.1 is going stable, but arches are taking their time (only + alpha and ppc so far) +- bug 270475: bug in the eclass about the platform switch, which affects + chroots and some arches like ppc, a solution is being worked on in the + overlay +- bug 235685: webkit sigbus on sparc, we will try to get upstream to fix it, in + the meantime we can use a patch on sparc only (and maybe on other arches like + alpha) +- bug 270769: ppc rendering fix will be fast-tracked for stabilization +- bug 209626: make qt eclasses ready for eclass-manpages, hwoarang offered to + take care of this +- bug 224951: qt4-qtruby has been hardmasked for a while, so we should fix or + remove the package; decided we'll work on it to see if it's fixable, + otherwise ask ruby herd to agree with removal; yngwin will commit his + intermediate work to overlay +- bug 236341: Pesa and hwoarang will work on removing automagic deps from PyQt4 +- bug 43827: qvfb and related embedded ebuilds could be proxy-maintained, we + will approach users that might be interested + + +Overlay +------- + +As mentioned during the discussion of the KDE overlay's CODE document, we +should start using similar commit policies, especially starting the commit +message with $PN. + +Both 4.5.9999 and 4.9999 versions of Qt ebuilds in overlay are actively +maintained and used, so status is OK. + +A lot of packages are being moved from overlay to the official tree, so work +there is progressing well. Pesa will work with ali_bush to get the latest +version of qtjambi into the tree. + + +Eclasses +-------- + +There has been discussion on -dev ML about blocking mixed Qt versions. Paludis +doesn't handle the blocks and dependencies the same way portage does, but it +was concluded that the proposal currently in overlay, which works fine with +portage, is the best solution so far, so we will go ahead and implement that in +the official tree as well. + +It was also decided to remove the custom-cxxflags useflag and the default +strip-flags from the qt4-build.eclass, as testing has shown that Qt is not as +sensitive to optimized flags anymore. We will let this change coincide with +committing the 4.5.2 (next release) ebuilds into the official tree. + +There has been a lot of development going on in the qt4-edge.eclass (the +overlay version of qt4.eclass). We have implemented additional default phases +for src_configure and src_install, the eqmake4 function has seen a lot of +improvements, and there is experimental functionality for handling translation +files. + +We decided to add that as a new eclass to the official tree, once the ongoing +work on eqmake4 and translations crystalizes. We will then mark the old eclass +as deprecated and open a tracker bug for migration of packages to the new +eclass. There was some brainstorming about naming the new eclass, but +bikeshedding is to be continued outside of the meeting. + + +Elected Qt team lead +-------------------- + +As we are now a fast growing team, yngwin felt the need to bring up the issue +of elections for a Qt team lead, as he assumed the position when no one was +looking after qt herd. The decision was this is not needed, as the team members +are unanimously happy with the current situation of yngwin being the de facto +leader. |