Changing the KDE Edu module maintainer
Hi, I have been the assigned KDE Edu module maintainer for the past years but due to family life (aging parents, husband being often away for his work, kids,…) I have not been active in the past 2 years and things will be very busy until at least mid-September so I will not contribute again to KDE until at least this time. I cannot go to the Randa meeting nor Akademy due to already planned events (we’ll celebrate our 30th anniversary on the 10th of August for example!). Aleix Pol will take over as module maintainer as he has been in charge since I stepped down. I’d like to thank him along with all the other amazing people working on KDE educational apps (in particular Andreas Cord-Landwehr). I did not realise I had a formal role as maintainer which is needed for allowing new apps in KDE Edu, otherwise I would have stepped down earlier. Of course I hope to contribute again and I still follow what’s happening through the mailing lists so don’t think you’ll get rid of me for good ;-) Best regards to all and thanks to everyone for what you brought me so far. Anne-Marie aka annma
Re: KF5 Update Meeting Minutes 2013-w25
Hi, I won't be able to redo my patch for https://git.reviewboard.kde.org/r/110907/ because my laptop has a power supply problem and I won't be able to accede to my KF5 build for some time. So it's free for someone to pick it up. Sorry about that, best regards, Anne-Marie - Mail original - De: Kevin Ottens ervin+bluesyst...@kde.org À: kde-frameworks-devel@kde.org Cc: kde-core-de...@kde.org Envoyé: Mardi 18 Juin 2013 17:23:15 Objet: KF5 Update Meeting Minutes 2013-w25 Hello everyone, This is the minutes of the Week 25 KF5 meeting. As usual it has been held on #kde-devel at 4pm Paris time. Announcements: * Tomorrow no new patch should be started, instead we get all the pending ones integrated so that dfaure can do a merge on thursday morning; * On June 22nd, a KF5 mini-sprint will be held in the Blue Systems Barcelona office; * sebas computed progress data number: * Qt contributions 67% done; * KDEUI Crumble 50% done; * kdelibs splitting around 40% done (on hold and will grow though); * kdelibs cleanup 73% done; * cmake 81% done; Were present: dgilo, dfaure, sebas, apol, ben2367, steveire, wojtask9, R_Rios scarpino, afiestas, and myself. Topics discussed: * dfaure is making progresses on the KIO split; * sebas is resuming the work on KPluginFactory; * conditional QML imports is scheduled as post KF 5.0 as a contribution to Qt; * cmake cleanup in plasma-framework is almost done; * apol will spearhead the efforts around KGlobalSettings; * ben2367 is working on kassistantdialog and kcrash; * ben2367 is trying to fix some of the missing copyrights; * steveire is working on cmake features we might use like the easier creation of interface properties on installation so that some of the features we got used to works nicely out of build too; * wojtask9 is working on KWallet and plans to pick KCompletion after that; * R_Rios just joined (welcome!) and will pick more tasks; * scarpino is almost done with the ECM_SourceIncompatibleChanges, ready to pick crumble tasks; * afiestas is working on the animation flag for Qt, and will pick up some tasks related to our QPA plugin; * dgilo is still working on removing our time_t uses; * QFileDialog changes are almost ready to get in Qt; * ervin is trying to get rid of the kdecore left overs; * Priority for the coming week is still the KDEUI Crumble. Action items still open: * [sandsmark] Finish the work on KPtyProcess * [steveire] Write a CMake for frameworks guideline in the wiki * [sebas] Look at cleaning up the CMake files in plasma-framework (almost there) * [steveire] investigate why kde4support isn't usable from outside kdelibs (issue with the cmake file) If you got questions, feel free to ask. Regards. -- Kévin Ottens, http://ervin.ipsquad.net Sponsored by BlueSystems and KDAB to work on KDE Frameworks ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110478: Move KButtonGroup to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110478/ --- (Updated June 11, 2013, 1:30 p.m.) Status -- This change has been marked as submitted. Review request for KDE Frameworks and Kevin Ottens. Description --- Port kcupsoptionspageswidget.ui to QGroupBox (I edited the .ui file in Designer from Qt5 for this hence the changes) Move class files Move test Change export in header and ad deprecated comment Diffs - kdeui/CMakeLists.txt cfa29ef kdeui/dialogs/kconfigdialogmanager.cpp 405799b kdeui/dialogs/kcupsoptionspageswidget.ui d2494c7 kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/kbuttongrouptest.h cd9130a kdeui/tests/kbuttongrouptest.cpp 93dd05e kdeui/widgets/kbuttongroup.h 5bc89dd kdeui/widgets/kbuttongroup.cpp c4d918d kdewidgets/kde.widgets aa07c0f kdewidgets/kdedeprecated.widgets 3adc0b2 staging/kde4support/src/CMakeLists.txt a8e0a0c staging/kde4support/src/kdeui/kbuttongroup.h PRE-CREATION staging/kde4support/src/kdeui/kbuttongroup.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 4115688 staging/kde4support/tests/kbuttongrouptest.h PRE-CREATION staging/kde4support/tests/kbuttongrouptest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110478/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110907: Move kdeprintdialog.h and kcups* to kde4support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110907/ --- (Updated June 9, 2013, 1:54 p.m.) Review request for KDE Frameworks and David Faure. Changes --- Forgot to update the exports in kdeprintdialog.h Description --- Move kdeprintdialog.h and kcups* to kde4support Fix compilation Mark as deprecated Things I am unsure of: the change in khtml/khtmlview.cpp and in kdeui/dialogs/kshortcutseditor.cpp, some CMakeLists moves as well are to be checked. Diffs (updated) - staging/kde4support/src/kdeui/kdeprintdialog.h PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110907/diff/ Testing --- Build Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110478: Move KButtonGroup to KDE4Support
On May 21, 2013, 10:35 a.m., Kevin Ottens wrote: Hm for the kcupsoptionspageswidget.ui don't we need to also introduce a QButtonGroup on the C++ side? So that the radio buttons keep being mutually exclusive. Radio buttons are autoExclusive by default (from doc) which I verified in the .ui file. kdeui/dialogs/kconfigdialogmanager.cpp will be removed from the commit. Another error in the initial patch is that kbuttongrouptest should be moved to staging/kde4support/autotests/ (and not staging/kde4support/tests) being initially in KDEUI_UNIT_TESTS. - Anne-Marie --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110478/#review32875 --- On May 16, 2013, 7:24 p.m., Anne-Marie Mahfouf wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110478/ --- (Updated May 16, 2013, 7:24 p.m.) Review request for KDE Frameworks and Kevin Ottens. Description --- Port kcupsoptionspageswidget.ui to QGroupBox (I edited the .ui file in Designer from Qt5 for this hence the changes) Move class files Move test Change export in header and ad deprecated comment Diffs - kdeui/CMakeLists.txt cfa29ef kdeui/dialogs/kconfigdialogmanager.cpp 405799b kdeui/dialogs/kcupsoptionspageswidget.ui d2494c7 kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/kbuttongrouptest.h cd9130a kdeui/tests/kbuttongrouptest.cpp 93dd05e kdeui/widgets/kbuttongroup.h 5bc89dd kdeui/widgets/kbuttongroup.cpp c4d918d kdewidgets/kde.widgets aa07c0f kdewidgets/kdedeprecated.widgets 3adc0b2 staging/kde4support/src/CMakeLists.txt a8e0a0c staging/kde4support/src/kdeui/kbuttongroup.h PRE-CREATION staging/kde4support/src/kdeui/kbuttongroup.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 4115688 staging/kde4support/tests/kbuttongrouptest.h PRE-CREATION staging/kde4support/tests/kbuttongrouptest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110478/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 Update Meeting Reminder 2013-w23
Hi, I can't make it unfortunately. I am a bit mixed up with my KNumInput patch and will need further guidance (maybe on IRC?), sorry about that. I'll read the meeting report. Anne-Marie - Mail original - De: David Faure fa...@kde.org À: kde-frameworks-devel@kde.org Envoyé: Mardi 4 Juin 2013 00:50:11 Objet: KF5 Update Meeting Reminder 2013-w23 Next meeting will be Tuesday 4 June. Exact time to be announced later (I won't be available at the usual 4pm CEST). Let's say 6pm CEST, I hope we'll be done by then. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110418: Move KNumInput to KDE4Support
On May 29, 2013, 11:50 a.m., David Faure wrote: Apar from the KConfigDialogManager issue below, it looks good. However, please wait until next week to commit it, to give people time to update their qt5.git build, since you use new API from there (QSpinBox::setDisplayIntegerBase). I promised Aaron that the use of new API in Qt would only happen after the first monday after the qt5 update. I'll wait until next Monday evening. On May 29, 2013, 11:50 a.m., David Faure wrote: kdeui/dialogs/kconfigdialogmanager.cpp, line 146 http://git.reviewboard.kde.org/r/110418/diff/2/?file=146814#file146814line146 Do we need to register KIntNumInput into KConfigDialogManager from the outside, i.e. from a Q_CONSTRUCTOR_FUNCTION in kintnuminput.cpp (kde4support)? Otherwise existing code with KIntNumInput + KConfigDialogManager will break. I think there were other commits to KConfigDialogManager earlier whicih might have the same issue. If there isn't one, we might need to add a public method for registering a class and its associated signal. There is no method to register a class. I think it's above my league to add one. Either someone else does it or I go over the moved classes and re-add what was removed. - Anne-Marie --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110418/#review33350 --- On May 28, 2013, 7:45 p.m., Anne-Marie Mahfouf wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110418/ --- (Updated May 28, 2013, 7:45 p.m.) Review request for KDE Frameworks, David Faure and Kevin Ottens. Description --- Move KNumInput to KDE4Support, use QSpinBox or QDoubleSpinBox instead. Test moved as well. Diffs - kdeui/dialogs/kconfigdialogmanager.cpp 87c3e48 kdeui/dialogs/kinputdialog.cpp 6cbd881 kdeui/dialogs/kinputdialog_p.h dcdff3f kdeui/tests/krulertest.h fc677c6 kdeui/tests/krulertest.cpp 9686421 staging/kde4support/src/kdeui/kcolordialog.cpp 041c06a Diff: http://git.reviewboard.kde.org/r/110418/diff/ Testing --- Build tested Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110418: Move KNumInput to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110418/ --- (Updated May 28, 2013, 7:44 p.m.) Review request for KDE Frameworks and Kevin Ottens. Changes --- Use setDisplayIntegerBase(base) from QSpinBox as it reached Qt5. Description --- Move KNumInput to KDE4Support, use QSpinBox or QDoubleSpinBox instead. Test moved as well. Diffs (updated) - kdeui/dialogs/kconfigdialogmanager.cpp 87c3e48 kdeui/dialogs/kinputdialog.cpp 6cbd881 kdeui/dialogs/kinputdialog_p.h dcdff3f kdeui/tests/krulertest.h fc677c6 kdeui/tests/krulertest.cpp 9686421 staging/kde4support/src/kdeui/kcolordialog.cpp 041c06a Diff: http://git.reviewboard.kde.org/r/110418/diff/ Testing --- Build tested Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110418: Move KNumInput to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110418/ --- (Updated May 28, 2013, 7:45 p.m.) Review request for KDE Frameworks, David Faure and Kevin Ottens. Description --- Move KNumInput to KDE4Support, use QSpinBox or QDoubleSpinBox instead. Test moved as well. Diffs - kdeui/dialogs/kconfigdialogmanager.cpp 87c3e48 kdeui/dialogs/kinputdialog.cpp 6cbd881 kdeui/dialogs/kinputdialog_p.h dcdff3f kdeui/tests/krulertest.h fc677c6 kdeui/tests/krulertest.cpp 9686421 staging/kde4support/src/kdeui/kcolordialog.cpp 041c06a Diff: http://git.reviewboard.kde.org/r/110418/diff/ Testing --- Build tested Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110464: Move KEditListBox to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110464/ --- (Updated May 23, 2013, 9:50 a.m.) Status -- This change has been marked as submitted. Review request for KDE Frameworks and Kevin Ottens. Description --- KEditListBox - KEditListWidget Move KEditListBox to KDE4Support Move test Fix export, header was already marked as deprecated, add since 5.0 Diffs - kdeui/CMakeLists.txt 7b115a5 kdeui/dialogs/kconfigdialogmanager.cpp 405799b kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/keditlistboxtest.cpp 5239ab9 kdeui/widgets/keditlistbox.h 539f506 kdeui/widgets/keditlistbox.cpp 23a9052 kio/kfile/kurlrequester.h 9fe6ae4 kio/kfile/kurlrequester.cpp 97d592d kio/tests/kurlrequestertest_gui.cpp f096cec staging/kde4support/src/CMakeLists.txt a8e0a0c staging/kde4support/src/kdeui/keditlistbox.h PRE-CREATION staging/kde4support/src/kdeui/keditlistbox.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 4115688 staging/kde4support/tests/keditlistboxtest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110464/diff/ Testing --- It builds Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110464: Move KEditListBox to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110464/ --- Review request for KDE Frameworks and Kevin Ottens. Description --- KEditListBox - KEditListWidget Move KEditListBox to KDE4Support Move test Fix export, header was already marked as deprecated, add since 5.0 Diffs - kdeui/CMakeLists.txt 7b115a5 kdeui/dialogs/kconfigdialogmanager.cpp 405799b kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/keditlistboxtest.cpp 5239ab9 kdeui/widgets/keditlistbox.h 539f506 kdeui/widgets/keditlistbox.cpp 23a9052 kio/kfile/kurlrequester.h 9fe6ae4 kio/kfile/kurlrequester.cpp 97d592d kio/tests/kurlrequestertest_gui.cpp f096cec staging/kde4support/src/CMakeLists.txt a8e0a0c staging/kde4support/src/kdeui/keditlistbox.h PRE-CREATION staging/kde4support/src/kdeui/keditlistbox.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 4115688 staging/kde4support/tests/keditlistboxtest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110464/diff/ Testing --- It builds Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110477: Move KTimeComboBox to KDE4Attic
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110477/ --- Review request for KDE Frameworks and Kevin Ottens. Description --- Move KTimeComboBox to KDE4Attic Move test: it was in KDEUI Unit Tests but there's no such section in the staging/kde4attic/tests/CMakeLists.txt so it's now in executable which might be wrong. Diffs - kdeui/CMakeLists.txt cfa29ef kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/ktimecomboboxtest.h 793bffb kdeui/tests/ktimecomboboxtest.cpp 4aaadef kdeui/widgets/ktimecombobox.h 21094b2 kdeui/widgets/ktimecombobox.cpp e1a9322 kdewidgets/kde.widgets aa07c0f kdewidgets/kdedeprecated.widgets 3adc0b2 staging/kde4attic/src/CMakeLists.txt 2fe1b8c staging/kde4attic/src/ktimecombobox.h PRE-CREATION staging/kde4attic/src/ktimecombobox.cpp PRE-CREATION staging/kde4attic/tests/CMakeLists.txt 1305d63 staging/kde4attic/tests/ktimecomboboxtest.h PRE-CREATION staging/kde4attic/tests/ktimecomboboxtest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110477/diff/ Testing --- It builds Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110478: Move KButtonGroup to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110478/ --- Review request for KDE Frameworks and Kevin Ottens. Description --- Port kcupsoptionspageswidget.ui to QGroupBox (I edited the .ui file in Designer from Qt5 for this hence the changes) Move class files Move test Change export in header and ad deprecated comment Diffs - kdeui/CMakeLists.txt cfa29ef kdeui/dialogs/kconfigdialogmanager.cpp 405799b kdeui/dialogs/kcupsoptionspageswidget.ui d2494c7 kdeui/tests/CMakeLists.txt cd055d5 kdeui/tests/kbuttongrouptest.h cd9130a kdeui/tests/kbuttongrouptest.cpp 93dd05e kdeui/widgets/kbuttongroup.h 5bc89dd kdeui/widgets/kbuttongroup.cpp c4d918d kdewidgets/kde.widgets aa07c0f kdewidgets/kdedeprecated.widgets 3adc0b2 staging/kde4support/src/CMakeLists.txt a8e0a0c staging/kde4support/src/kdeui/kbuttongroup.h PRE-CREATION staging/kde4support/src/kdeui/kbuttongroup.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 4115688 staging/kde4support/tests/kbuttongrouptest.h PRE-CREATION staging/kde4support/tests/kbuttongrouptest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110478/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110437: Move KTextBrowser to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110437/ --- Review request for KDE Frameworks and Kevin Ottens. Description --- Replace KTextBrowser with QTextBrowser, move KTextBrowser to KDE4Support, move test as well. Diffs - kdeui/CMakeLists.txt db4c1d5 kdeui/dialogs/kaboutapplicationdialog.cpp bf0c9de kdeui/dialogs/kconfigdialogmanager.cpp 620f0b5 kdeui/dialogs/ktip.cpp 3ea2dca kdeui/shortcuts/kcheckaccelerators.cpp 612c90d kdeui/tests/CMakeLists.txt d0c8b42 kdeui/tests/ktextbrowsertest.cpp 606886c kdeui/widgets/kcharselect.cpp 2e43d0d kdeui/widgets/ktextbrowser.h 71aa7e7 kdeui/widgets/ktextbrowser.cpp 37918c0 kdewidgets/kde.widgets 6ccdcb65 kdewidgets/kdedeprecated.qrc 6152a80 kdewidgets/kdedeprecated.widgets cda6929 kdewidgets/kdewidgets.qrc 0a741e5 staging/kde4support/src/CMakeLists.txt 354a278 staging/kde4support/src/kdeui/ktextbrowser.h PRE-CREATION staging/kde4support/src/kdeui/ktextbrowser.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt e3e42ba staging/kde4support/tests/ktextbrowsertest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110437/diff/ Testing --- It builds Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110452: Change API doc for KTextBrowser
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110452/ --- Review request for KDE Frameworks and David Faure. Description --- Change API doc in KTextBrowser: mark as deprecated, inform how to port. I could not find out what QTextBrowser signal to use instead of KTextBrowser::mailClick though. Diffs - staging/kde4support/src/kdeui/ktextbrowser.h 5e5daf9 Diff: http://git.reviewboard.kde.org/r/110452/diff/ Testing --- Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110418: Move KNumInput to KDE4Support
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110418/ --- Review request for KDE Frameworks and Kevin Ottens. Description --- Move KNumInput to KDE4Support, use QSpinBox or QDoubleSpinBox instead. Test moved as well. Diffs - kdeui/CMakeLists.txt 3e18c2a kdeui/dialogs/kconfigdialogmanager.cpp 620f0b5 kdeui/dialogs/kinputdialog.cpp 6cbd881 kdeui/dialogs/kinputdialog_p.h dcdff3f kdeui/tests/CMakeLists.txt 69be059 kdeui/tests/knuminputtest.h 5c41e28 kdeui/tests/knuminputtest.cpp 6387337 kdeui/tests/krulertest.h fc677c6 kdeui/tests/krulertest.cpp 9686421 kdeui/widgets/knuminput.h 06d1ebd kdeui/widgets/knuminput.cpp 8a288a5 kdewidgets/kde.widgets 6ccdcb65 kdewidgets/kdedeprecated.qrc 6152a80 kdewidgets/kdedeprecated.widgets cda6929 kdewidgets/kdewidgets.qrc 0a741e5 staging/kde4support/src/CMakeLists.txt 354a278 staging/kde4support/src/kdeui/kcolordialog.cpp 041c06a staging/kde4support/src/kdeui/knuminput.h PRE-CREATION staging/kde4support/src/kdeui/knuminput.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt e3e42ba staging/kde4support/tests/knuminputtest.h PRE-CREATION staging/kde4support/tests/knuminputtest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110418/diff/ Testing --- Build tested Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: R: Re: kde review kartesio
Hi, I think Kartesio is not ready to move: - the GUI is not so good - lack of tooltips - I am not happy with some strings and they lack context info - the standard C++ code is not so good either (this rm for example) - lack of testing I suggest you do a release first so we can test translations and you can get some users feedback and have time to move the code to Qt classes. This is my suggestion only, others may disagree Best regards, Anne-Marie
Re: R: Re: kde review kartesio
Hi, Hi, actually I have not prepared any binary package. Anyway, you can install Kartesio downloading the source code from the git repo (https://projects.kde. org/projects/kdereview/kartesio), installing the library libzorbaneural (https: //www.gitorious.org/zorbaneural/zorbaneural/trees/master/binary- packages/libzorbaneural-0.1), and running the build.sh script you find in the Kartesio root folder. Why is this build.sh script needed? Is it because I did not run it that I got my build error? Also, you should have installed the program maxima (just the program, dev libraries are not needed) to have Kartesio fully working. If there are some troubles in building Kartesio, just ask me. I have this error: /home/kde-devel/kartesio/src/calculations.cpp:278:1: error: control reaches end of non-void function [-Werror=return-type] cc1plus: some warnings being treated as errors Best regards, Anne-Marie
Re: kde review kartesio
Hi,
In general, you're mixing a lot of plain C / stdlib stuff into Qt
code. Is there a reason for that? For example, in
calculations.cpp:148
you take text from a text field, convert it to a byte array, convert
it to a char* and then pass it to a function. Why not just pass the
QString? You can iterate over a QString like
foreach ( const QChar c, myqstring ) { ... }
or also
for ( int i = 0; i myqstring.size(); i++ ) { ... }
if you like that better, and you can also index it like a char*, as
in
mystring[i+1] or so.
Yes, this is an heritage from the older version of Kartesio, that was
based
mainly on plain ANSI C++. Those mixing are just an hack to make
Kartesio work
immediately. If I'll have time, I will translate everything into
Qt, but
first of all I would like to apply other features.
You asked for an inclusion in KDE and we are reviewing Kartesio. There is
already a big amount of work to be done from the comments you got. I don't
think adding features now is a smart move, review is a phase where your program
should reach KDE standards. Using Qt libs wherever possible is the priority and
getting all the required fixes will make you busy enough.
Best regards,
Anne-Marie
Re: R: Re: R: Re: kde review kartesio
Hi, so I don't have to type all those every time I want to build Kartesio again. I'm not sure why you get that error, mainlybecause I don't know which is the instruction that gives that problem since I changed a lot the code in these hours. Try to download the latest git version and build it, so I will know exactly where the problem is. commenting out line 465 in calculations.cpp makes it build (the line after the return). Anne-Marie
Re: kde review kartesio
Hi, I am wondering what is the user base for this application as it seems quite specialized (I did not build it yet though). Can you tell us more about the potential target? Another question that comes to mind is: can't it be a feature of an existing KDE Edu apps? Best regards, Anne-Marie - Mail original - De: LucaTringali tringalinv...@libero.it À: kde-core-devel@kde.org Envoyé: Jeudi 9 Mai 2013 18:06:16 Objet: kde review kartesio Hello, I have been working on Kartesio, a program for calculating best fit curves with experimental points. I think it is ready to be moved in the KDE Edu main repo now, so I'm asking your approval. I followed the guidelines ( http://techbase.kde.org/Policies/Application_Lifecycle ) and Kartesio is actually in KDE review: https://projects.kde.org/projects/kdereview/kartesio For any question, ask me. Luca Tringali
Re: kde review kartesio
Hi, A few primary remarks: - libzorbaneural is needed but my distro does not have anything with neural in it (OpenSuse 12.3) what repo do I need to add in order to get it? The libzorbaneural website should be added to the cmake file so people can find this and packagers can add it to their distros. - I see a screenshot folder and some .pro files that probably are not needed - some doxygen comments for the variables in the .h files would be appreciated, if anyone else wants to fix bugs it'll help a lot. - Kartesio does not build for me, I get /home/kde-devel/kartesio/src/calculations.cpp:278:1: error: control reaches end of non-void function [-Werror=return-type] cc1plus: some warnings being treated as errors - I don't see a Messages.sh file to extract translatable strings. - I am not comfortable with the rm call line 181 in calculations.cpp = you can probably use more Qt classes here and in other parts of this file too. That's only a quick review as I couldn't run the app yet. Tomaz, as for the user base maybe we could start a module for advanced scientific tools? Best regards, Anne-Marie - Mail original - De: Tomaz Canabrava tcanabr...@kde.org À: Anne-Marie Mahfouf annemarie.mahf...@free.fr Cc: LucaTringali tringalinv...@libero.it, kde-core-devel@kde.org Envoyé: Vendredi 10 Mai 2013 12:28:54 Objet: Re: kde review kartesio Quite Unlikely ... It's a Solver, to fit curves into points, That's very used in any theorical research, engeniering, math, phisics, etc. 2013/5/10 Anne-Marie Mahfouf annemarie.mahf...@free.fr Hi, I am wondering what is the user base for this application as it seems quite specialized (I did not build it yet though). Can you tell us more about the potential target? Another question that comes to mind is: can't it be a feature of an existing KDE Edu apps? Best regards, Anne-Marie - Mail original - De: LucaTringali tringalinv...@libero.it À: kde-core-devel@kde.org Envoyé: Jeudi 9 Mai 2013 18:06:16 Objet: kde review kartesio Hello, I have been working on Kartesio, a program for calculating best fit curves with experimental points. I think it is ready to be moved in the KDE Edu main repo now, so I'm asking your approval. I followed the guidelines ( http://techbase.kde.org/Policies/Application_Lifecycle ) and Kartesio is actually in KDE review: https://projects.kde.org/projects/kdereview/kartesio For any question, ask me. Luca Tringali
Re: Review Request 110351: Move KFontDialog to KDE4Suport
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110351/ --- (Updated May 8, 2013, 11:44 a.m.) Review request for KDE Frameworks, David Faure and Kevin Ottens. Changes --- This diff fixes issues in kdeui/fonts/kfontrequester.cpp as indicated by Kévin Description --- Move KFontDialog to KDE4Support, move test as well, thing to check is diff for kdeui/fonts/kfontrequester.cpp to see if I got it right. Diffs (updated) - kdeui/fonts/kfontrequester.cpp 09aaa45 tier1/kwidgetsaddons/src/kfontchooser.h 8bdd5d4 Diff: http://git.reviewboard.kde.org/r/110351/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Review Request 110351: Move KFontDialog to KDE4Suport
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110351/ --- (Updated May 8, 2013, 11:46 a.m.) Review request for KDE Frameworks, David Faure and Kevin Ottens. Changes --- This diff makes the move of KFontDialog to KDE4Support and is unchanged from the first one, the first one was splitted in 2. Description --- Move KFontDialog to KDE4Support, move test as well, thing to check is diff for kdeui/fonts/kfontrequester.cpp to see if I got it right. Diffs (updated) - kdeui/CMakeLists.txt 38a7238 kdeui/fonts/kfontdialog.h 9098a83 kdeui/fonts/kfontdialog.cpp 8632183 kdeui/tests/CMakeLists.txt 037cec1 kdeui/tests/kfontdialogtest.cpp cbccadc staging/kde4support/src/CMakeLists.txt f5fbe60 staging/kde4support/src/kdeui/kfontdialog.h PRE-CREATION staging/kde4support/src/kdeui/kfontdialog.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 3d6a6dd staging/kde4support/tests/kfontdialogtest.cpp PRE-CREATION Diff: http://git.reviewboard.kde.org/r/110351/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110351: Move KFontDialog to KDE4Suport
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110351/ --- Review request for KDE Frameworks, David Faure and Kevin Ottens. Description --- Move KFontDialog to KDE4Support, move test as well, thing to check is diff for kdeui/fonts/kfontrequester.cpp to see if I got it right. Diffs - kdeui/CMakeLists.txt 38a7238 kdeui/fonts/kfontdialog.h 9098a83 kdeui/fonts/kfontdialog.cpp 8632183 kdeui/fonts/kfontrequester.cpp 09aaa45 kdeui/tests/CMakeLists.txt 037cec1 kdeui/tests/kfontdialogtest.cpp cbccadc staging/kde4support/src/CMakeLists.txt f5fbe60 staging/kde4support/src/kdeui/kfontdialog.h PRE-CREATION staging/kde4support/src/kdeui/kfontdialog.cpp PRE-CREATION staging/kde4support/tests/CMakeLists.txt 3d6a6dd staging/kde4support/tests/kfontdialogtest.cpp PRE-CREATION tier1/kwidgetsaddons/src/kfontchooser.h 8bdd5d4 Diff: http://git.reviewboard.kde.org/r/110351/diff/ Testing --- It builds. Thanks, Anne-Marie Mahfouf ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Review Request 110102: Change 2 strings from Display to Screen for better consistency.
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110102/ --- Review request for kde-workspace and Dario Freddi. Description --- The Battery applet indicates Screen Brightness and most strings refer to Screen except those 2 strings which referred to Display and that I changed to Screen Diffs - powerdevil/daemon/actions/bundled/powerdevildimdisplayaction.desktop 3050455 powerdevil/daemon/actions/bundled/powerdevilbrightnesscontrolaction.desktop 79f88ae Diff: http://git.reviewboard.kde.org/r/110102/diff/ Testing --- Testing done, OK Thanks, Anne-Marie Mahfouf
Re: GSoC proposal
Hi Ajay, We talked on IRC. Of course we will cooperate with you but you need to choose a subject, research it and write a proposal. Contributing to the KDE area of your project is a great bonus as well. I pointed you to Myriam's blog which she wrote so you wouldn't send such a vague mail! Best regards and do send your proposal to the plasma-devel list if it's about kde-workspace. You must follow Google guidance for proposal. Anne-Marie - Mail original - De: ajay kulkarni anku.man...@gmail.com À: kde-devel@kde.org Envoyé: Mardi 16 Avril 2013 16:36:15 Objet: GSoC proposal Hi, I'd like to do a GSoC project under KDE, so I' hoping that you'd co-operate with me :) AjayKumar N Kulkarni Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Beginner Help
Hi, You need to give us more details about which bug you are trying to fix. It should be on a KDE program you know quite well. You need to reproduce the bug and well understand it for a start. Then try to track the bug down in the code, for example by adding a few kDebug calls and recompiling the code and see the debug output. You will have to look at the code and try to understand it. Start with these few steps. Best regards, Anne-Marie - Mail original - De: Ashvini Varatharaj ash@hotmail.com À: Myriam Schweingruber myr...@kde.org, kde-devel@kde.org Envoyé: Vendredi 29 Mars 2013 09:16:46 Objet: RE: Beginner Help Hey I read the http://flossmanuals.net/kde-guide/ .Thanks it was of great help :). I decided first I will try Bug fixing so I went to the KDE bug tracking system https://bugs.kde.org/ and the junior jobs there show a list of all the bugs . I kind of understood the terms but i dont know how to fix it and again I am stuck :/ . On cliking the bug name it shows the details but then what should I do ? how do I go on ? .Please help required . Thank you , Kindly, Beginner. Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Guidance required
- Mail original - De: Tomaz Canabrava tcanabr...@kde.org À: kde-devel kde-devel@kde.org Cc: Anne-Marie Mahfouf annemarie.mahf...@free.fr Envoyé: Dimanche 17 Février 2013 14:30:34 Objet: Re: Guidance required first, download the code ( you can find the code in project.kde.org/kalzium , for example. then go to bugs.kde.org , search and fix a few bugs from it, and use reviewboard ( reviewboard.kde.org ) to send us the patches. Exactly, these are the steps to follow. You can also subscribe to the kde-edu mailing list and ask there questions about bugs or features for those programs: https://mail.kde.org/mailman/listinfo/kde-edu Best regards, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Guidance required
Hi Rushi, Here is a link you will find helpful http://community.kde.org/GSoC It would be good for you to get familiar in depth with KDE workspaces and applications and find out what area you like. You can also start fixing a few easy bugs to get a feeling on what it is like to work with our community. Getting a coding experience in KDE before GSoC is something that will greatly help you! This book http://flossmanuals.net/kde-guide/ can also be of interest. I hope this answers your question. Good luck and I hope to hear from you soon! Anne-Marie - Mail original - De: Rushi Shukla rushbo...@gmail.com À: kde-devel kde-devel@kde.org Envoyé: Jeudi 14 Février 2013 12:23:19 Objet: Guidance required Hello I am a student of Dhirubhai Ambani Institute of Information and Communication Technology (DAIICT) , Gandhinagar , India.I am really interested in going for GSOC 2013 . I would like to undertake one of KDE's projects involving desktop applications as my project for GSOC 2013. I am highly dedicated towards programming and research . Can anyone please guide me as to how do i contact a mentor and ask him/her to provide me documentation on any projects that KDE is offering . Any sort of help is highly appreciated . Awaiting your reply soon . Regards, Rushi Shukla Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Review Request: Make KRunner Enter work again in 4.10
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108197/ --- Review request for kde-workspace and Aaron J. Seigo. Description --- Aaron reverted some code in the 4.9 branch but not in the 4.10 branch where he seemed to not have the bug. Although we all have the bug and thus this patch reverts the code in the same way he did for 4.9. Should also be fixed in master because Enter not working makes KRunner useless. This addresses bug https://bugs.kde.org/show_bug.cgi?id=309787. http://bugs.kde.org/show_bug.cgi?id=https://bugs.kde.org/show_bug.cgi?id=309787 Diffs - krunner/interfaces/default/interface.cpp fac1066 Diff: http://git.reviewboard.kde.org/r/108197/diff/ Testing --- Works as expected Thanks, Anne-Marie Mahfouf
Re: Important: potential new contributors! was Fwd: we need more tasks
How do I become a mentor? I need a profile but I don't remember how to set one up. Cheers, Anne-Marie - Mail original - De: Myriam Schweingruber myr...@kde.org À: devel mailinglist KDE kde-devel@kde.org, KDE Quality Team kde-test...@kde.org Envoyé: Dimanche 2 Décembre 2012 13:27:47 Objet: Important: potential new contributors! was Fwd: we need more tasks Forwarding this to kde-devel, as we have an urgent need of new tasks for Code-In Dear KDE developers and contributors, we have been taken by storm by the Google Code-In students and have almost run out of suitable tasks. Please all, have a look at your project and get us some new tasks so we can feed the students. Important: these students are all potential new contributors as they work exclusively on KDE during the whole period, they had to choose a project and stick to it! So please, all, check your documentation, tutorials, Junior Jobs, etc. and bring us some new tasks! I will add some bug triaging tasks later today, but that will not be enough, please all, this is a unique opportunity to get new contributors on board and have some work done! Thanks in advance! Myriam PS. please come to #kde-soc and/or subscribe to the kde-soc-men...@kde.irg list for this occasion PPS. No translation tasks allowed this year, unfortunately. -- Forwarded message -- From: Myriam Schweingruber myr...@kde.org Date: Fri, Nov 30, 2012 at 1:04 PM Subject: Re: we need more tasks To: kde-soc-men...@kde.org On Fri, Nov 30, 2012 at 12:31 PM, Lydia Pintscher ly...@kde.org wrote: Heya folks :) We're running out of tasks on Melange. Please add more if you can and poke Teo, Alessandro or me to publish them. I do add new tasks every time a task is closed. For the other KDE tasks, you might want to ask students to triage bugs, that is always quite rewarding and takes quite some work off our shoulders. Also some Extra Mile bugs might qualify for the coding tasks, as well as some Junior Jobs. But I leave that up to the projects to decide. Did I mention Documentation? Are all your handbooks up-to-date? Does your project homepage have a Team presentation page? Git testing and beta testing is also a nice idea *HINT* we are in beta for KDE SC 4.10! */HINT* Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: ALERT: KDElibs (at least) 4.8.4 is actually 4.8.80+
On 06/09/2012 12:10 PM, Modestas Vainius wrote: Hello, On šeštadienis 09 Birželis 2012 13:01:20 Albert Astals Cid wrote: here at Debian we had a really bad experience with 4.8.4. While 4.8.3 was pretty good, 4.8.4 seemed like a huge step backwards in terms of stability (random crashes there and there). After quick investigation of kdelibs 4.8.4 I found the following: I don't know yet if any other modules from 4.8.4 has been mis-packaged in the same way There's no mispackaging. If you followed the list or read the archives before blaming people of wrong doing you'd know that kdelibs for 4.8.4 and 4.8.80 actually come from the same branch. Thank you for pushing a bunch of untested huge changes in the minor point release. Really appreciated. what are those untested changes please? the Quality Team will be happy to test anything you want to be tested so please state what we need to do. Anne-Marie
Re: kdelibs and Qt version dependency
On 06/06/2012 03:19 AM, Dawit A wrote:
It is a simple matter to put a #ifdef around the code that does not
compile with Qt 4.7. I wish this issue was raised when the code was up
for review for more than a month or the Qt documentation mentioned
something about those functions only being available in Qt 4.8.
Anyhow, I have attached a patch that should make it compile on Qt
4.7.x. If someone is willing to test it against Qt 4.7 and let me know
if it compiles and works fine for them, I can commit it. It will
however mean that bug# 275524 will not be fixed for those using Qt 4.7.
On Tue, Jun 5, 2012 at 3:16 PM, Albert Astals Cid aa...@kde.org
mailto:aa...@kde.org wrote:
On May 19, Dawit Alemayehu commited a change that uses
QSslConfiguration::testSslOption that is only available in Qt 4.8
This means that both kdelibs 4.8.4 and kdelibs 4.9 now depend in
Qt 4.8
instead Qt 4.7
I want to ask the kdelibs maintainers:
a) Do you think it makes sense to change our Qt required version from
Qt 4.7 in kdelibs 4.8.3
to
Qt 4.8 in kdelibs 4.8.4
?
b) Do you think kdelibs 4.9 should depend in Qt 4.8 or not?
Cheers,
Albert
I tried the patch, you forgot some stuff. I am working on the 4.8.80
kdelibs tarball if that matters.
I added
#if QT_VERSION = 0x040800
if (sslConfig.testSslOption(QSsl::SslOptionDisableCompression)
!shouldSslCompressBeDisabled) {
setMetaData(QLatin1String({internal~currenthost}LastUsedSslDisableCompressionFlag),
QString::number(true));
}
#endif
and
#if QT_VERSION = 0x040800
kDebug(7027) Trying SSL handshake with protocol: version
, SSL compression ON:
sslConfig.testSslOption(QSsl::SslOptionDisableCompression);
#endif
and it built.
Anne-Marie
Logo for KDE Quality Team
Hi, The KDE Quality and Testing Team is looking for a logo. If you know someone who would be able to draw one for us, please ask her/him to contact us: mailing list https://mail.kde.org/mailman/listinfo/kde-testing IRC Freenode #kde-quality Thanks in advance, Anne-Marie annma on IRC Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
KDE 4.9 feature plan
Hi all, It would be great if you could all take a few minutes to update the feature plan for 4.9 (preferably right now or you'll forget again!) http://techbase.kde.org/Schedules/KDE4/4.9_Feature_Plan as the Quality Team would need to identify new features, new applets, new apps,.. in order to give them some priority testing! Can you also forward this to any relevant subgroup you know, thanks a lot in advance. Best regards, Anne-Marie
Re: qt4 ver for trunk
On 05/05/2012 12:26 PM, Lindsay Mathieson wrote: On Sat, 5 May 2012 12:06:01 PM Martin Gräßlin wrote: On Saturday 05 May 2012 19:50:24 Lindsay Mathieson wrote: What version is currently needed to build trunk? You can find the minimum version in the CMakeLists.txt of kdelibs: set (QT_MIN_VERSION 4.7.0) Excellent, so the Qt 4.8.1 with my distro should be fine? Is there any need to build the qt-copy from kde then? thanks, Your distribution Qt 4.8.1 will be very fine! No need for qt-copy. Best regards, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Akademy hotels and hostels - book now
Hi all, Just a reminder: if you're planning to attend Akademy this year, please book you hotel or hostel room asap. Late June and July is high season in Tallinn and you might have trouble finding a hotel room if you want to book last minute. A list of recommended hostels and hotels can be found here: http://akademy.kde.org/accommodation Cheers, Claudia -- Claudia Rauch Business Manager KDE e.V. Linienstr. 141 10115 Berlin Germany
Akademy hotels and hostels - book now
Hi all, Just a reminder: if you're planning to attend Akademy this year, please book you hotel or hostel room asap. Late June and July is high season in Tallinn and you might have trouble finding a hotel room if you want to book last minute. A list of recommended hostels and hotels can be found here: http://akademy.kde.org/accommodation Cheers, Claudia -- Claudia Rauch Business Manager KDE e.V. Linienstr. 141 10115 Berlin Germany Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Introduction
On 04/25/2012 01:55 PM, Abhiram Ampabathina wrote: Hello KDE, I am Abhiram. I would like to participate in the development team of KDE. I would like to develop something that relates to education. I need some help on how to start things like getting involved and etc., Hoping to get a reply. Regards, Abhiram Hi Abhiram, In KDE we have a subproject related to educational software: KDE Edu See http://edu.kde.org In order to contribute to KDE Edu, you first need to install and look at the available programs http://edu.kde.org/applications/all/ and from there see what you would like to do and what area you would like to contribute to. You can then write to the KDE Edu mailing list to give your opinion on what you would like to work on. https://mail.kde.org/mailman/listinfo/kde-edu The best idea to get started is to contribute to some bug fixes in a program you like. Best regards, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Setting up a Quality Team within KDE
On 04/08/2012 07:11 AM, Percy Camilo Triveño Aucahuasi wrote: Hi Anne, hi all On Fri, Apr 6, 2012 at 12:03 PM, Anne-Marie Mahfouf This is addressed for 4.9 as putting in place a few selected areas of functional testing and hopefully we will assess some automated UI testing tools and start using them in the following releases. I hope we can gather enough beta testers and make this working. Indeed, Nice idea, I think this is the right focus to (auto)test the functionality/features of the app. I've searched some info about this topic and found this: http://ldtp.freedesktop.org/wiki/Home It has full support for KDE/Qt (4.x) apps and the scripts (for autotesting) can be written with Python. My 0.5 cents :) Cheers, Percy Yes this is maybe the best free tool to do the job. DO you or anybody have used it already? Thanks for your input, Anne-Marie On Fri, Apr 6, 2012 at 12:03 PM, Anne-Marie Mahfouf annemarie.mahf...@free.fr mailto:annemarie.mahf...@free.fr wrote: On 04/06/2012 02:23 PM, Aleix Pol wrote: On Thu, Apr 5, 2012 at 1:42 PM, Anne-Marie Mahfouf annemarie.mahf...@free.fr mailto:annemarie.mahf...@free.fr wrote: Hi, We would like to setup a Quality Testing Team within KDE in order to better test our next KDE SC and make the beta process more efficient. Attached is the first draft of the ideas I brainstormed. Source .odt of this document is available at http://quickgit.kde.org/index.php?p=scratch%2Fannma%2Fquality-testing-doc.git (We can make it a public Google doc if it is more convenient or an etherpad). The document roughly describes 2 areas of action: - reinforcement (labelled Reinforce) of existing structures (mainly targetted to developers and mainly relevant before the beta stage of the release). This could be used as guidelines for new developers. Of course it won't be newbies which will develop Unit Tests or check the code quality. But some guidelines can be useful for libs outside Frameworks. An area of relevant reinforcement that can be currently done is the Review process for new integration. - new infra-structures: this is labelled New in the doc: this is what I would see to happen for the 4.9 release. A new mailing list has been set up in order to discuss all this: please subscribe to it if you would like to be part of this https://mail.kde.org/mailman/listinfo/kde-testing An IRC channel also was created on Freenode: #kde-quality Please join the mailing list and the IRC channel so we can setup a plan to start putting all this in gear! Thanks in advance, Anne-Marie and Myriam Hi! I think this project is a very interesting idea and definitely something we need. Said that, I'd like to propose some small changes on how this should be done. In the document there are some actions to be taken that sound a bit too technical, for example it specifies reinforcing the unit testing. This is something that we should have been doing already and I don't see someone from the Quality Team going to a development team and improving that. Making unit tests is the developer task (and the document mentions it) and we do have solit Unit Tests in kdelibs and Frameworks and kdepimlibs. However there are other libs within KDE where maybe unit tests are not as present as they should (I did not research that though). Also, about unit tests, it's not only writing them, it's also running them. This is not done in a regular basis and needs to be automated in the future and the fails need to be fixed. No newbie will ever touch to any Unit Tests of course. And any action will be discussed with the gurus in this field (/me does not point to David). We have many tools for developers which are not fully used: latest great tool is Jenkins which I was aware of only recently. My label Reinforce is to take full advantage of those existing tools. (It would be cool if at Akademy there are some talks focusing on using these tools.) What I'd like to see is this new team testing KDE and its applications from a user perspective, specifying the different perspectives the KDE end user will face (different OS, different form factors, etc) and reporting problems (not necessarily bugs, as in crashes) and proposing new solutions. This is addressed for 4.9 as putting in place
Re: Setting up a Quality Team within KDE
On 04/06/2012 02:23 PM, Aleix Pol wrote: On Thu, Apr 5, 2012 at 1:42 PM, Anne-Marie Mahfouf annemarie.mahf...@free.fr wrote: Hi, We would like to setup a Quality Testing Team within KDE in order to better test our next KDE SC and make the beta process more efficient. Attached is the first draft of the ideas I brainstormed. Source .odt of this document is available at http://quickgit.kde.org/index.php?p=scratch%2Fannma%2Fquality-testing-doc.git (We can make it a public Google doc if it is more convenient or an etherpad). The document roughly describes 2 areas of action: - reinforcement (labelled Reinforce) of existing structures (mainly targetted to developers and mainly relevant before the beta stage of the release). This could be used as guidelines for new developers. Of course it won't be newbies which will develop Unit Tests or check the code quality. But some guidelines can be useful for libs outside Frameworks. An area of relevant reinforcement that can be currently done is the Review process for new integration. - new infra-structures: this is labelled New in the doc: this is what I would see to happen for the 4.9 release. A new mailing list has been set up in order to discuss all this: please subscribe to it if you would like to be part of this https://mail.kde.org/mailman/listinfo/kde-testing An IRC channel also was created on Freenode: #kde-quality Please join the mailing list and the IRC channel so we can setup a plan to start putting all this in gear! Thanks in advance, Anne-Marie and Myriam Hi! I think this project is a very interesting idea and definitely something we need. Said that, I'd like to propose some small changes on how this should be done. In the document there are some actions to be taken that sound a bit too technical, for example it specifies reinforcing the unit testing. This is something that we should have been doing already and I don't see someone from the Quality Team going to a development team and improving that. Making unit tests is the developer task (and the document mentions it) and we do have solit Unit Tests in kdelibs and Frameworks and kdepimlibs. However there are other libs within KDE where maybe unit tests are not as present as they should (I did not research that though). Also, about unit tests, it's not only writing them, it's also running them. This is not done in a regular basis and needs to be automated in the future and the fails need to be fixed. No newbie will ever touch to any Unit Tests of course. And any action will be discussed with the gurus in this field (/me does not point to David). We have many tools for developers which are not fully used: latest great tool is Jenkins which I was aware of only recently. My label Reinforce is to take full advantage of those existing tools. (It would be cool if at Akademy there are some talks focusing on using these tools.) What I'd like to see is this new team testing KDE and its applications from a user perspective, specifying the different perspectives the KDE end user will face (different OS, different form factors, etc) and reporting problems (not necessarily bugs, as in crashes) and proposing new solutions. This is addressed for 4.9 as putting in place a few selected areas of functional testing and hopefully we will assess some automated UI testing tools and start using them in the following releases. I hope we can gather enough beta testers and make this working. I'm really hopeful about such a team, I think it's a good opportunity for KDE to be able to reach contributions for a less common sector of our community and keep working together for a greater KDE experience. Cheers! Aleix Thanks for your input! Anne-Marie
Re: compile error with kde-runtime
Hi, I had to rm CMakeCache.txt in kdelibs build dir for it to be built with the latest SDO. Anne-Marie On 03/07/2012 11:14 AM, Vishesh Handa wrote: On Wed, Mar 7, 2012 at 3:35 PM, Anne-Marie Mahfouf annemarie.mahf...@free.fr mailto:annemarie.mahf...@free.fr wrote: On 03/07/2012 09:54 AM, Hugo Pereira Da Costa wrote: My experience: you need to rebuild kdelibs first (with latest sdo installed) to re-generate source code from the ontologies, that is then used in kde-runtime. Yup! (to experts, correct me if I'm wrong) Hugo I updated SDO from git master, I rebuilt and installed kdelibs and I still get the error. There is something else probably to build: I can't see where this Nepomuk::Vocabulary::NFO comes from. In any case, cmake should fail somehow if I miss something. NFO is generated by cmake scripts in kdelibs/nepomuk. If you look in the build directory you'll find the file nfo.h Eg - vlap:~/kde/build/kdelibs/nepomuk $ ack -a depiction nfo.h 643: * http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#depiction 648:NEPOMUK_EXPORT QUrl depiction(); Binary file CMakeFiles/nepomuk.dir/nfo.o matches nfo.cpp 103: nfo_depiction( QUrl::fromEncoded( http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#depiction;, QUrl::StrictMode ) ), 234:QUrl nfo_depiction; 671:QUrl Nepomuk::Vocabulary::NFO::depiction() 673:return s_nfo()-nfo_depiction; Could you check if it has this 'depiction' function? If it doesn't could you check if your SDO has it? vlap:~/kde/src/shared-desktop-ontologies/nfo $ ack -a depiction nfo.trig.in http://nfo.trig.in 944:nfo:depiction 948: rdfs:label depiction ; 958: nrl:inverseProperty nfo:depiction . Anne-Marie Still waiting to hear how to fix the error in compiling kde-runtime. Git updates have not helped. [ 33%] Building CXX object nepomuk/kioslaves/nepomuk/CMakeFiles/kio_nepomuk.dir/__/common/resourcestat.o /home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp: In member function ‘QByteArray Nepomuk::ResourcePageGenerator::generatePage() const’: /home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp:204:36: error: ‘depiction’ is not a member of ‘Nepomuk::Vocabulary::NFO’ /home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp:205:52: error: ‘depiction’ is not a member of ‘Nepomuk::Vocabulary::NFO’ make[2]: *** [nepomuk/kioslaves/nepomuk/CMakeFiles/kio_nepomuk.dir/resourcepagegenerator.o] Error 1 make[2]: *** Waiting for unfinished jobs Please advise. Thanks David On Sun, Mar 4, 2012 at 9:54 AM, Anne-Marie Mahfouf annemarie.mahf...@free.fr mailto:annemarie.mahf...@free.fr wrote: On 03/04/2012 09:41 AM, Vishesh Handa wrote: On Sat, Mar 3, 2012 at 10:23 PM, David Boosalis david.boosa...@gmail.com mailto:david.boosa...@gmail.com wrote: Thank you for the reply. By SDO I assume it is shared-desktop-ontologies. I very rarely build this, but from your email I did a git update on this and there was only one file updated. Perhaps I need to be on a different branch then master. I also updated and built kdelibs from master. I still get the same compile errors with kde-runtime Are you sure you have the correct git repo of SDO? Please check - http://techbase.kde.org/Getting_Started/Build/Requirements#Shared-Desktop-Ontologies I have the same error with SDO master up-to-date. Anne-Marie -David On Fri, Mar 2, 2012 at 11:42 PM, Vishesh Handa m...@vhanda.in mailto:m...@vhanda.in wrote: You need to update SDO, and then update kdelibs. On Sat, Mar 3, 2012 at 6:20 AM, David Boosalis david.boosa...@gmail.com mailto:david.boosa...@gmail.com wrote: Sorry if this is the wrong group to ask this question, please refer me to the right group if you know. The issue is kde-runtime from master. I've been getting the following compile error for about a week now. /home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp: In member function ‘QByteArray Nepomuk::ResourcePageGenerator::generatePage() const’: /home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp:204:36: error: ‘depiction’ is not a member of ‘Nepomuk::Vocabulary::NFO’ David
Re: Reactivate your KDE bugs.kde.org account before March 30th 2012
Hi, If I understand correctly, login with previous account credentials will reactivate the account and no further step is to be done? Thanks for the upgrade, Anne-Marie On 03/05/2012 11:36 PM, Tom Albers wrote: Hi, We have recently installed a new update of the bugzilla software and we would like to ask you to reactivate your accounts. This can be done in one simple step: login on the http://bugs.kde.org site. If you don't reactivate your account before March 30th we will block your account from logging in until the password reset feature is used to set a new password. Sorry for the trouble, but we hope you will enjoy the upgrade. Best, Tom Albers KDE Sysadmin Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: compile error with kde-runtime
On 03/04/2012 09:41 AM, Vishesh Handa wrote:
On Sat, Mar 3, 2012 at 10:23 PM, David Boosalis
david.boosa...@gmail.com mailto:david.boosa...@gmail.com wrote:
Thank you for the reply. By SDO I assume it is
shared-desktop-ontologies. I very rarely build this, but from
your email I did a git update on this and there was only one file
updated. Perhaps I need to be on a different branch then master.
I also updated and built kdelibs from master. I still get the
same compile errors with kde-runtime
Are you sure you have the correct git repo of SDO?
Please check -
http://techbase.kde.org/Getting_Started/Build/Requirements#Shared-Desktop-Ontologies
I have the same error with SDO master up-to-date.
Anne-Marie
-David
On Fri, Mar 2, 2012 at 11:42 PM, Vishesh Handa m...@vhanda.in
mailto:m...@vhanda.in wrote:
You need to update SDO, and then update kdelibs.
On Sat, Mar 3, 2012 at 6:20 AM, David Boosalis
david.boosa...@gmail.com mailto:david.boosa...@gmail.com
wrote:
Sorry if this is the wrong group to ask this question,
please refer me to the right group if you know.
The issue is kde-runtime from master. I've been getting
the following compile error for about a week now.
/home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp:
In member function ‘QByteArray
Nepomuk::ResourcePageGenerator::generatePage() const’:
/home/david/kde/src/KDE/kde-runtime/nepomuk/kioslaves/nepomuk/resourcepagegenerator.cpp:204:36:
error: ‘depiction’ is not a member of
‘Nepomuk::Vocabulary::NFO’
David
On Fri, Mar 2, 2012 at 9:58 AM, Lamarque Vieira Souza
lamar...@kde.org mailto:lamar...@kde.org wrote:
This is an automatically generated e-mail. To reply,
visit: http://git.reviewboard.kde.org/r/104140/
Review request for kdelibs.
By Lamarque Vieira Souza.
Description
Currently kdeclarative library does not install the
KDeclarativeConfig.cmake and KDeclarativeConfigVersion.cmake to
${LIB_INSTALL_DIR}/cmake/KDeclarative. In the current situation any KDE program that want
to use it set the kdeclarative name hardcoded into CMakeLists.txt, which is
not ideal. This patch fixes that problem.
Diffs
* experimental/libkdeclarative/CMakeLists.txt
(0db647c)
* experimental/libkdeclarative/KDeclarativeConfig.cmake.in
http://KDeclarativeConfig.cmake.in (PRE-CREATION)
*
experimental/libkdeclarative/KDeclarativeConfigVersion.cmake.in
http://KDeclarativeConfigVersion.cmake.in
(PRE-CREATION)
View Diff http://git.reviewboard.kde.org/r/104140/diff/
Re: Please avoid noisy merge commits in frameworks
On 02/19/2012 04:58 PM, Stephen Kelly wrote: Stephen Kelly wrote: Hi there, I was reviewing the changes in the frameworks branch from yesterday. Something I noticed was that there are a lot of merge commits that don't need to exist. Ugh. Yet more of this just appeared... Recent history in the frameworks branch looks far more complex than it is and is harder to follow. There are too many people unaware that they're doing it maybe... Yeah I notice I did it :( It happened yesterday because we were new people (which was very good) working on frameworks and not all of us are 100% used to git yet. I did git config branch.autosetuprebase always which should always rebase. I guess I should get used to using gitk. Anne-Marie
Re: Developing without creating a dedicated developer user account
On 02/04/2012 09:21 PM, Luiz Romário Santana Rios wrote: Hello. So, so far, I compiled KDE from the sources in a separated user account dedicated for KDE development, following that Techbase tutorial. But, as this has led to many inconvenients, I'd like to know how (or if) I can use my own user account for KDE development, especially for plasmoid, dataengine development and/or frameworks development. How can I configure KDevelop, environment stuff and so on. To run applications, I _think_ something like LD_LIBRARY_PATH=/local/kde/installation app should do the job, although I'm not sure if this is enough and I can't test anything *right now*. Thanks in advance. Hi, Which tutorial did you follow on techbase.kde.org please? (url) As far as I know, the recommended method is to use your normal account so I am a bit surprised. Also, what part of KDE do you want to work on? Apart from kdelibs and kde-runtime, kde-workspace and kde-baseapps, you do not need the full compilation of KDE. Thanks in advance for more precisions, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: build.kde.org partially down
Hi Torgny, What is build.kde.org exactly? In KDEEDU I only see Marble. What is Jenkins? What are people? Thanks in advance, Anne-Marie - Mail original - De: Torgny Nyblom nyb...@kde.org À: kde-devel@kde.org Envoyé: Mercredi 4 Janvier 2012 10:52:48 Objet: Re: build.kde.org partially down On Wednesday 04 January 2012 10.26.05 Torgny Nyblom wrote: Hi, the host that is hosting our jenkins instance (build.kde.org) has stopped listening to IPv4 connections. As a result build.kde.org is down for most?) people. Issue is fixed, turned out to be an issue in jenkins (it needed a double restart!) Sorry for the noise. /Regards Torgny Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Hello Kde
Hi Amandeep, Learning Qt is of course a good start. What you can also do is go to bugs.kde.org and look for JJ bugs to fix. Also ask the Amarok people for easy things to do. You will get started quicker if you do things besides of studying the book (which is a very good one). Best regards, Anne-Marie - Mail original - De: Amandeep Singh aman.ded...@gmail.com À: kde-devel kde-devel@kde.org Envoyé: Mercredi 28 Décembre 2011 10:48:50 Objet: Hello Kde Hi, I am Aman (irc : dedman) , a student of computer science from India. I love KDE Software and have been using it for over a year. I especially love using Amarok, Kate, Kopete, KMail and the Plasma Desktop as a whole. I wish to contribute to KDE but I have no prior experience with contributing to OpenSource. However i have been programming in C/C++ for some time. I understand that for contributing to KDE, I should learn Qt. I have started on basic Qt tutorials and I am planning on buying the book C++ GUI Programming with Qt 4 by Blanchette and Summerfield. Will it be a good starting point to Qt, and KDE in general ? Thanks. -- *- Dedman* Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Bug triage process needs help (links about bug triaging)
On Sunday, October 02, 2011 11:27:33 AM Anne-Marie Mahfouf wrote: On Wednesday, September 28, 2011 01:46:14 PM Bart Kelsey wrote: Hi folks, I'd like to draw attention to the fact that KDE's bug triage process is lacking. It's frustrating for users submitting bug reports when an easily reproducible bug sits in the queue, without even a comment, for six months. For the record, I'm referring to this bug report here: https://bugs.kde.org/show_bug.cgi?id=270105 I have, for the record, already posted a message to plasma-devel about it, and I'm mentioning it here because I believe it's indicative of a larger problem. From my understanding of C++ and Qt, this bug is most likely very easy to fix for someone who knows the code base. Even if it's not, though, it would require a trivial amount of time to confirm it, leave a brief comment, and mark the bug as new. My question, ultimately, is do you really want users to report bugs? If so, there ought to be a process in place to make sure the users who report the bugs know that the bugs have at least been looked at by a human being (and preferably triaged). I realize this isn't exactly a fun or interesting job, but for a large FOSS project like KDE, it's a necessary one. Regards, Bart Kelsey The bug refered there is not really a bug. It is a usability wish. In my opinion, such a wish should be accompanied by a strong use case. Do you often remove panels? when do you do so? why do you remove them accidentally? same for widgets. My use case is that I take time to set up my workspace when I install my distribution and then occasionally I need for example a new activity that I set up. The rest of the time I use my machine as it is. When I do those setup, I dedicate some amount of time which includes trial and error time. This is my use case. Yours can be different. As for general bugs: - the number of reported bugs is too large for developers to deal with it. We addressed this by trying to make the reporting smarter and by setting bugsquads days/weeks to triage bugs. Triaging means moving the bug report to a new state: - identify duplicates - reproduce the bug and mark it as CONFIRMED - write clearly the steps to reproduce it are 3 important states but there are others. Recommanded reading: Quick reading: http://techbase.kde.org/Contribute/Bugsquad/Guide Bug Triaging: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging A bug's Life Cycle: https://bugs.kde.org/page.cgi?id=fields.html Setting up a bug day: http://techbase.kde.org/Contribute/Bugsquad Users do report bugs. Developers do fix bugs. To achieve better results, we need the intermediary: users participating in bug triaging. The last bug days I participated to, we were only a handful of people (and maybe not a complete handful even!) and I was very discouraged to carry on. Maybe we lacked promotion of it, the one regarding kdepim also was difficult to triage because technical. I urge you to be positive and help with an hour or so of contribution during the next month. I am willing to set up some week-end bug days, I am sure members of the bugsquad also are. But we need help otherwise it's just too much work when yo uare only 2 people. Please stay tuned to Planet KDE in the next days and volunteer to participate to any bug crushing effort that will be planned. See http://blog.lydiapintscher.de/2011/10/03/teaching-the-next-adas-join-kde- for-ada-lovelace-day-tutorials/ The How to Help with Bugreports IRC tutorial is a great way of getting involved a step further reporting bugs and help KDE. I hope you'll be several to join. Best regards, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Bug triage process needs help (links about bug triaging)
On Wednesday, September 28, 2011 01:46:14 PM Bart Kelsey wrote: Hi folks, I'd like to draw attention to the fact that KDE's bug triage process is lacking. It's frustrating for users submitting bug reports when an easily reproducible bug sits in the queue, without even a comment, for six months. For the record, I'm referring to this bug report here: https://bugs.kde.org/show_bug.cgi?id=270105 I have, for the record, already posted a message to plasma-devel about it, and I'm mentioning it here because I believe it's indicative of a larger problem. From my understanding of C++ and Qt, this bug is most likely very easy to fix for someone who knows the code base. Even if it's not, though, it would require a trivial amount of time to confirm it, leave a brief comment, and mark the bug as new. My question, ultimately, is do you really want users to report bugs? If so, there ought to be a process in place to make sure the users who report the bugs know that the bugs have at least been looked at by a human being (and preferably triaged). I realize this isn't exactly a fun or interesting job, but for a large FOSS project like KDE, it's a necessary one. Regards, Bart Kelsey The bug refered there is not really a bug. It is a usability wish. In my opinion, such a wish should be accompanied by a strong use case. Do you often remove panels? when do you do so? why do you remove them accidentally? same for widgets. My use case is that I take time to set up my workspace when I install my distribution and then occasionally I need for example a new activity that I set up. The rest of the time I use my machine as it is. When I do those setup, I dedicate some amount of time which includes trial and error time. This is my use case. Yours can be different. As for general bugs: - the number of reported bugs is too large for developers to deal with it. We addressed this by trying to make the reporting smarter and by setting bugsquads days/weeks to triage bugs. Triaging means moving the bug report to a new state: - identify duplicates - reproduce the bug and mark it as CONFIRMED - write clearly the steps to reproduce it are 3 important states but there are others. Recommanded reading: Quick reading: http://techbase.kde.org/Contribute/Bugsquad/Guide Bug Triaging: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging A bug's Life Cycle: https://bugs.kde.org/page.cgi?id=fields.html Setting up a bug day: http://techbase.kde.org/Contribute/Bugsquad Users do report bugs. Developers do fix bugs. To achieve better results, we need the intermediary: users participating in bug triaging. The last bug days I participated to, we were only a handful of people (and maybe not a complete handful even!) and I was very discouraged to carry on. Maybe we lacked promotion of it, the one regarding kdepim also was difficult to triage because technical. I urge you to be positive and help with an hour or so of contribution during the next month. I am willing to set up some week-end bug days, I am sure members of the bugsquad also are. But we need help otherwise it's just too much work when yo uare only 2 people. Please stay tuned to Planet KDE in the next days and volunteer to participate to any bug crushing effort that will be planned. Thanks for reading, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Finding the Unloved
On Saturday, September 03, 2011 04:00:29 AM Valorie Zimmerman wrote: Hi folks, It's that time again. We in the CWG are trying to find those parts of KDE that do not have someone to take care of them, as well as those teams that are in need of help. Our goal is to find people who are interested in those unloved applications, teams, or areas in KDE. Please add to the list here: http://community.kde.org/KDE/Finding_The_Unloved . All the best, Valorie Zimmerman Member, Community Working Group http://about.me/valoriez Hi, Thanks for this! At KDE Edu we got new developers since last January: 1 for Step, 1 for KTouch, 1 for Kig and 1 for Kiten! So I guess all our released programs are loved! (which is amazing). We're currently working on a Memory program which we want to make touch friendly. Anybody is welcome to join our team! We need graphic designers, some SVG themes in particular. QML porting of some programs also is planned (Kanagram for example). Don't hesitate to join our mailing list https://mail.kde.org/mailman/listinfo/kde-edu and our IRC channel on Freenode: #kde-edu KDE Edu is a friendly team and some programs are quite small so it's an easy point of entry to KDE contribution. Best regards to all, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: error building kde/kanagram from master
Le Monday 6 June 2011 19:35:53, Zé a écrit : Error building kde/kanagram from master, the output: [ 22%] Building CXX object kanagram/src/CMakeFiles/kanagram.dir/kanagram.o /home/mmodem/rpm/BUILD/kdeedu/kanagram/src/kanagram.cpp:49:30: fatal error: sharedkvtmlfiles.h: No such file or directory compilation terminated. make[2]: *** [kanagram/src/CMakeFiles/kanagram.dir/kanagram.o] Error 1 make[1]: *** [kanagram/src/CMakeFiles/kanagram.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs When you run cmake in Kanagram build dir, it detects whether you have libkdeedu or not. If not it does not build. I checked to be sure. So as you're building I assume you have libkdeedu. Please look in /libkdeedu/keduvocdocument/ and check what files are there and what you installed from there. sharedkvtmlfiles.h is installed from there. And it's weird that you are on IRC and asking other stuff about kdeedu apps but then post here anyway... Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: impossible build kde-runtime
On Thursday 02 June 2011 15:33:39 Zé wrote: I have installed qt 4.8.0 and started building kde modules, but when i reached kde-runtime the build broke, the output: ../../../../lib/libdatamanagementtestlib.a(resourceidentifier.o):(.rodata. _ZTIN7Nepomuk18ResourceIdentifierE[typeinfo for Nepomuk::ResourceIdentifier]+0x10): undefined reference to `typeinfo for Nepomuk::Sync::ResourceIdentifier' collect2: ld returned 1 exit status make[2]: *** [nepomuk/services/storage/test/fakedms] Error 1 make[1]: *** [nepomuk/services/storage/test/CMakeFiles/fakedms.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/transactionmodel.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementmodel. o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementadapto r.o /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘resources’ /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘properties’ /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘app’ [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementcomman d.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/classandpropertytree .o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcemerger.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourceidentifier.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcewatchermanag er.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcewatcherconne ction.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/ontologymanageradapt or.o Linking CXX shared module ../../../lib/nepomukstorage.so [ 93%] Built target nepomukstorage make: *** [all] Error 2 Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe yes we're aware of it, the developers moslty use Qt 4.7 and of cours eit builds against 4.7. It'll be fixed soon, thanks, Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: impossible build kde-runtime
On Thursday 02 June 2011 15:33:39 Zé wrote: I have installed qt 4.8.0 and started building kde modules, but when i reached kde-runtime the build broke, the output: ../../../../lib/libdatamanagementtestlib.a(resourceidentifier.o):(.rodata. _ZTIN7Nepomuk18ResourceIdentifierE[typeinfo for Nepomuk::ResourceIdentifier]+0x10): undefined reference to `typeinfo for Nepomuk::Sync::ResourceIdentifier' collect2: ld returned 1 exit status make[2]: *** [nepomuk/services/storage/test/fakedms] Error 1 make[1]: *** [nepomuk/services/storage/test/CMakeFiles/fakedms.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/transactionmodel.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementmodel. o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementadapto r.o /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘resources’ /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘properties’ /home/mmodem/rpm/BUILD/kde-runtime/nepomuk/services/storage/datamanagement model.cpp:1212:6: warning: unused parameter ‘app’ [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/datamanagementcomman d.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/classandpropertytree .o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcemerger.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourceidentifier.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcewatchermanag er.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/resourcewatcherconne ction.o [ 93%] Building CXX object nepomuk/services/storage/CMakeFiles/nepomukstorage.dir/ontologymanageradapt or.o Linking CXX shared module ../../../lib/nepomukstorage.so [ 93%] Built target nepomukstorage make: *** [all] Error 2 Fixed now! Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: Top 15 Mailinglists with messages in moderation May 1st
On Sunday 01 May 2011 16:00:57 Tom Albers wrote: Hi, New month, new list. If lists are unused, let me know, I will delete them. If someone wants to help with moderation for any of these list, let me know as well. 19 kde-france-ca Where can I see archives of that list and its purpose? Anne-Marie
Re: Introducing libmediawiki
On Saturday, March 19, 2011 11:47:45 AM Alexandre Mendes wrote: Hello, We worked on a library, libmediawiki, to interface the MediaWiki API with Qt, which is a part of the project silk. Also we have produce two new widgets and a kipi plugin to export images to commons.wikimedia.org. They use our library . We think our work can interest some kde developpers and we want to know if you can introduce it in your release schedule. You can find our work at the same place as project-silk. https://projects.kde.org/projects/playground/base/silk/repository/revisions /master/show/mediawiki Best regards, The IUP ISI Team. Hi, Do you want to include the lib in kdelibs? If so, you need to explain what the lib does and list what projects can use this. Also you need to ensure all files have a proper licence header. What I suggest is: - make a list of projects that could use your lib - precise where you want this to be added to (kdelibs, extragear,..) and what it does - add your lib to kdereview so developers can test it Additional question: will you maintain this code after your university task is finished? Best regards, Anne-Marie PS: probably kdeedu can use it as well as Picture Frame applet, both projects I am involved in. But you need to clarify what your lib exactly can do!
Re: CMake error when compiling
On vendredi 21 janvier 2011 21:20:58 Daniel E. Moctezuma wrote: Hi there, I was trying to compile Kiten and I got the following error with CMake: CMake Error at CMakeLists.txt:9 (check_include_files): Unknown CMake command check_include_files. So instead of doing INCLUDE(CheckIncludeFiles) y did FIND_PACKAGE( KDE4 REQUIRED ), as this is a KDE4 application I thought that would be better and indeed I didn't had any other error. My question is: What is the difference between doing: FIND_PACKAGE( KDE4 REQUIRED ) INCLUDE( KDE4Defaults ) and FIND_PACKAGE( KDE4 REQUIRED ) ? Hi, To build Kiten from kdeedu svn module you need to issue cmake on top of kdeedu and then cd in kiten dir and build it with make and make install. You can amend your CMakeLists locally to allow to build only Kiten locally but in svn we work with modules (kdelibs, kdebase, kdeedu,...) and cmake is to be issued on top of these. This will change with git but while it's easy with Kiten which has no dependencies such as libkdeeedu it's not so easy for other applications which use kdeedu libs. Your patch on reviewboard is therefore not relevant. Best regards, Anne-Marie PS: A general remark, not aimed at you but which is at my concern: the build one app independently way as we'll have it in git is fine but we need not to forget to share resources and not reinvent the wheel for every program. Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: unabe to build kdeedu trunk revision 1214750
On Sunday 16 January 2011 08:18:04 Zé wrote: unabe to build kdeedu trunk revision 1214750 the output; [ 63%] Building CXX object kalgebra/analitza/CMakeFiles/analitza.dir/substituteexpression.o Linking CXX shared library ../../lib/libanalitza.so sipmarblepart2.cpp: In function ‘PyObject* meth_Marble_MarbleWidget_centerOn(PyObject*, PyObject*)’: sipmarblepart2.cpp:19640: error: no matching function for call to ‘Marble::MarbleWidget::centerOn(const QModelIndex, bool)’ /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:638: note: candidates are: void Marble::MarbleWidget::centerOn(qreal, qreal, bool) /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:650: note: void Marble::MarbleWidget::centerOn(const Marble::GeoDataCoordinates, bool) /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:659: note: void Marble::MarbleWidget::centerOn(const Marble::GeoDataLatLonBox, bool) sipmarblepart2.cpp: In function ‘PyObject* meth_Marble_MarbleWidget_addPlacemarkFile(PyObject*, PyObject*)’: sipmarblepart2.cpp:21289: warning: ‘void Marble::MarbleWidget::addPlacemarkFile(const QString)’ is deprecated (declared at /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:315) sipmarblepart2.cpp: In function ‘PyObject* meth_Marble_MarbleWidget_addPlacemarkData(PyObject*, PyObject*)’: sipmarblepart2.cpp:21321: warning: ‘void Marble::MarbleWidget::addPlacemarkData(const QString, const QString)’ is deprecated (declared at /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:323) sipmarblepart2.cpp: In function ‘PyObject* meth_Marble_MarbleWidget_removePlacemarkKey(PyObject*, PyObject*)’: sipmarblepart2.cpp:21351: warning: ‘void Marble::MarbleWidget::removePlacemarkKey(const QString)’ is deprecated (declared at /home/mmodem/rpm/BUILD/kdeedu/marble/src/lib/MarbleWidget.h:330) [ 63%] Built target analitza [ 63%] Generating settings.h, settings.cpp [ 63%] Generating ui_axisrange.h [ 63%] Generating ui_plottitle.h Scanning dependencies of target cantorlibs make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/ sipmarblepart2.o] Error 1 make[1]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe CCing Simon Edwards si...@simonzone.com who is the Python maintainer. Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: developer
Hi, It depends on what you want to develop: - a new program: use kde git - improve an existing program: send a few patches to the developers or use reviewboard.kde.org and you will be granted svn/git access after that Tell us a bit more on what area/program you want to contribute please. Best regards, Anne-Marie Le 9 janv. 2011 à 14:36, Matus Ujhelyi ujhely...@gmail.com a écrit : Hi, my name is Matus Ujhelyi. I would like to get some information about KDE-developer program. Is there any way to become a developer and how the process pass off? Who is the person i could talk with? Best wishes Matus Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: kcm_keyboard 4.5.4 fails to build
Hi Erik, You should subscribe to https://mail.kde.org/mailman/listinfo/kde-buildsystem and post all your errors here. This is because you use -DKDE4_ENABLE_FINAL=ON I don't know if we support it or not but the above list will know. Best regards, Anne-Marie On Friday 24 December 2010 16:06:54 Erik wrote: kcm_keyboard 4.5.4 fails to build Steps to reproduce: 1. tar jxvf /usr/portage/distfiles/kdebase-workspace-4.5.4.tar.bz2 2. cd kdebase-workspace-4.5.4 3. mkdir build 4. cd build 5. cmake -DKDE4_ENABLE_FINAL=ON .. 6. make kcm_keyboard Actual result: In file included from /usr/include/qt4/QtCore/QDir:1, from /home/work/programmering/kdebase-workspace-4.5.4/kcontrol/keyboard/xkb_help er.cpp:22, from /home/work/programmering/kdebase-workspace-4.5.4/build/kcontrol/keyboard/kc m_keyboard_final_cpp.cpp:8: /usr/include/qt4/QtCore/qdir.h:107: fel: expected identifier before numeric constant /usr/include/qt4/QtCore/qdir.h:107: fel: expected } before numeric constant /usr/include/qt4/QtCore/qdir.h:107: fel: expected unqualified-id before numeric constant Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Re: kcm_keyboard 4.5.4 fails to build
On Friday 24 December 2010 16:58:41 Erik wrote: 2010-12-24 16:14, Anne-Marie Mahfouf skrev: You should subscribe to https://mail.kde.org/mailman/listinfo/kde-buildsystem and post all your errors here. Actually kde-devel is the list that I was pointed to: https://bugs.kde.org/show_bug.cgi?id=260726#c1 (Although I personally think that a bug report is appropriate for a build failure in a stable release.) This is because you use -DKDE4_ENABLE_FINAL=ON I don't know if we support it or not but the above list will know. I have used --enable-final to build my KDE packages for many years. Even now, most packages work with that build style. So nothing needs to be fixed in the build system. Therefore I do not want to bother those people over there. The errors that I found now need to be fixed in the C++ source code. Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe OK then, sorry Anne-Marie Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
Review Request: In System Settings in French the icon's description is badly cut when there is a single quote
--- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6106/ --- Review request for kdelibs. Summary --- Patch to address https://bugs.kde.org/show_bug.cgi?id=257988: in French in System Settings the icon's description string is badly cut when there is a single quote. Unit tests added for the whole method (by Fredrikh) and for the specific single quote by me. Should go in 4.6 so please any kde-core devel review! Thanks Diffs - trunk/KDE/kdelibs/kdecore/tests/kstringhandlertest.h 1205827 trunk/KDE/kdelibs/kdecore/tests/kstringhandlertest.cpp 1205827 trunk/KDE/kdelibs/kdecore/text/kstringhandler.cpp 1205827 Diff: http://svn.reviewboard.kde.org/r/6106/diff Testing --- Tested in French, fixes the bug. Thanks, Anne-Marie
