From Fedora Project Wiki
(Summary) |
m (internal link cleaning) |
||
Line 19: | Line 19: | ||
** kde-4.5.4 status | ** kde-4.5.4 status | ||
** qt-4.7.x for f13 : where are we? push forward? drop it? | ** qt-4.7.x for f13 : where are we? push forward? drop it? | ||
** [ | ** [[Meeting:Board_meeting_2010-12-06|spin position]] | ||
** [http://dot.kde.org/2010/12/06/kde-announces-calligra-suite Calligra] | ** [http://dot.kde.org/2010/12/06/kde-announces-calligra-suite Calligra] | ||
** [[Features/KDE46]] | ** [[Features/KDE46]] |
Latest revision as of 22:13, 17 September 2016
Meeting Time
- 2010-12-07 14:00 UTC
- #fedora-meeting on freenode
Participants
Agenda
- topics to discuss:
- kde-4.5.4 status
- qt-4.7.x for f13 : where are we? push forward? drop it?
- spin position
- Calligra
- Features/KDE46
- kde-4.5.85 status
- recent bugs:
- qt-x11 (assistant) depends on qt-webkit
- kdevelop broken with kde-4.6beta click here for the bug report, need 4.2 snapshot?
Transcript
Summary
kde-4.5.4 status
- AGREED: to push 4.5.4 to updates-testing
- than to prepare update
- kde-4.5.4 and kdepim-4.4.8 to be grouped in one update
- rdieter_work joined as later - in-transit
qt-4.7.x for f13 : where are we? push forward? drop it?
- we are still not sure we really want to update 4.7 in f13
- +1 by Kevin_Kofler, other folks tend to not update or don't know yet, don't care
- we need list of arguments for FESCo (disagreement - before or after update?)
- QtWebKit security, bugfixes but regressions (any?), backward compatible, new neat features
- no conclussion -> move discussion onlist
Calligra
- http://dot.kde.org/2010/12/06/kde-announces-calligra-suite
- KOffice fork, in short term it looks like winner (more projects joining Calligra over original KOffice)
- Naming? Especially Words (MS concerns)
- Could we ship both? Potential conflicts...
- Ready by KO/Calligra 2.4
qt-x11 (assistant) depends on qt-webkit
- qt-assistant uses qtwebkit to render documentation => new dependency for qt-x11
- than prepared patch to use qtextbrowser
- but it's not as powerfull as qtwebkit (HTML/CSS subset implemented) - should be ok for docs?
- AGREED: on testing patch in rawhide for feedback by our devs/users
- alternative: split qt-assistant and use Provides: qt4-assistant