Monday, November 26, 2012

Akademy-Fr in Toulouse


Akademy-Fr happened in Toulouse last week-end part of a bigger FOSS event in Toulouse named Capitole du Libre. On Saturday (10am to 8pm) we had a booth to show KDE. 

A track with talks about KDE also went on in the room near the booth: Kévin Ottens presented KDE as a community, Lambert Clara promoted KDevelop as an IDE for everyone's project, Sébastien Renard explained how the French translation team checks translations in order to reach quality (using pology for example). David Faure then lead us to debug programs using valgrind, reading backtraces, having a thorough process when debugging and much more. Sébastien explained how to tackle IT complexity based on his own experiment. 
Meanwhile, the KDE booth was always staffed and passers-by enjoyed the demos (Marble on a desktop, on Plasma Active and on a N9 for example) and could learn more about KDE with great leaflets. 

I was particularly impressed to meet David Revoy who is an artiste living in Toulouse and he uses Krita for his professional graphical work. I also met an enthusiastic teacher who uses Kalzium and said that no other software can beat it. It's great to see people using and enjoying our software and choosing it over proprietary ones.
On Sunday we had several workshops: translation, Frameworks5 and UI Consulting. Groups of people were busy learning and contributing. 
Doctor UI aka Aurélien

Frameworks5 Team

Thanks to the sponsors and to Kévin, Jean-Nicolas, Benjamin for the organization. Thanks to the other Kévin and PixCyl for the great leaflet!

Tuesday, June 12, 2012

Numbers feedback from the Testing Team

After 8 days since the KDE 4.9 first Beta was released, 93 bug reports were open or confirmed against this version and 31 from those are already fixed. A few bugs were also fixed without any report issued.

We have 2 new very active newcomers full of energy and doing a great job. New applets are almost all tested (see http://community.kde.org/Getinvolved/Testing/Beta/Plasma) we now need to concentrate less on Plasma and more on applications.

Don't hesitate to join if your distribution provides the Beta (Beta 2 will be out really soon). Channel #kde-quality on IRC (Freenode) is a convenient way to get introduced and work with others. Developers also are welcome to join this channel!

If you report bugs, do not forget to set your KDE version in the "Version:" field. This should reflect the KDE version of the first reporter then the highest KDE version on which the bug was reproduced to ensure the report is always up-to-date.

Thursday, June 07, 2012

Testing KDE 4.9: status

Yesterday I indicated how one can participate to KDE 4.9 Beta 1 testing phase. There is indeed a Live CD available at http://susestudio.com/a/tAWYe6/kde-plasma-daily 

We are prioritizing the testing of new applets, new applications and new features and we have functional tests ready to be used. Please read my previous post to learn more about this. Janek was the first person doing a functional test of the Now Playing applet and sending a report to the Quality mailing list. He opened 2 bug reports following his tests. Thanks a lot Janek!

Testers test and report bugs. Reporting good bugs is compulsory if we want devels to fix them. We need to make the developers focus on the most important bugs. Stating the KDE version in the "Version:" field in a bug report is compulsory. If you identify a regression, you can add the word "regression" in the "keywords" field. This will help targeting specific bug reports as a priority to be fixed.
I am pleased to report that some bugs have already been fixed and we triaged lots of bug reports, especially in Plasma. I'd like to thank all the users who take time to report bugs and who took time to answer our questions about older reports. We were pleased to see that lots of bug reporters care enough to help us having precise bug reports which will lead to better and quicker fixes.

The Quality Team will conduct a bugzilla training this week-end on IRC in #kde-bugs (freenode) (June 9th and 10th). We will also be available to help people wanting to be part in testing in #kde-quality. Do not hesitate to join if you can spare a bit of time for KDE. I also invite all developers to join this training in order to use bugzilla more efficiently!

Wednesday, June 06, 2012

Testing KDE 4.9 Beta1 (version 4.8.80)

As you may know, we recently set up a Quality and Testing team within KDE. We prepared some wiki pages (http://community.kde.org/Getinvolved/Testing/Beta) and now that the Beta 1 is out, several people already joined this Testing phase.

How can you get involved?
Install the Beta 1 from your distribution, most known distributions provide packages for it.
After that, you can choose two ways of testing:
- either use the release as you would normally and look for regressions, bugs, crashes,... Please report them to bugs.kde.org (try to search if the bug was already reported, for a quicker result you can ask on IRC, freenode, in #kde-bugs), do not forget to set up the version in your bug report as well as the precise stps to reproduce the bug. If it is a regression, explain how it was before.
- or choose a specific component to test in a more thorough way. We focus in priority on new additions to this release, on changed components and on new features. You can therefore test applets (http://community.kde.org/Getinvolved/Testing/Beta/Plasma) or test full programs (http://community.kde.org/Getinvolved/Testing/Beta/4.9Applications) or new features (http://community.kde.org/index.php?title=Getinvolved/Testing/Beta/AreasToTest). Copy the proposed tests in a text file and add a note like "works" or "OK" after testing each proposed feature. Then send your text to the Quality Team (kde-testing@kde.org) with your name or nickname. You can also extend those tests if you find other things to test, that will be useful in the future and also when we will move to more automated tests. I believe testing an applet does not require much time while testing a full application is more time demanding.
There is something to work on for everyone!
Testing does not require any specific knowledge: install the Beta and have a bugzilla account are the only requirements.
Please do not hesitate to join this effort and raise the quality of this release. Developers will then get batches of bugs to fix, priority will be given to regression and blockers. Several bugs already have been fixed!

IRC channels on freenode are #kde-quality and #kde-bugs
Mailing list is https://mail.kde.org/mailman/listinfo/kde-testing

Friday, April 06, 2012

Setting up a Quality Assurance and Testing Team in KDE

We have great tools in KDE to check our code but they are not all used the best they could. We also can go further in testing our software and deliver higher quality releases. This is why we decided to setup a Quality Assurance and Testing Team which will coordinate the efforts for testing better the next release, KDE SC 4.9 and the ones after it.
Here is a link to a document I wrote to expose some ideas in order to have a starting point to debate from: http://www.flootr.com/download.php?file=3374d1db022e34aa39083c22f06abc2e
(the source in .odt is available from my KDE git scratchpad).
The document outlines improvement in using existing tools or following existing policies (marked as "Reinforce") and new testing methods (marked as "New"). For the post 4.9 releases more new targets will be set.
So, what to do to participate? You can subscribe to the mailing list and also join the IRC channel  #kde-quality on Freenode and comment on the document or share your experience with testing software or present yourself and tell us you are interested in participating.
We are trying to assess and update the existing wiki resources and update them, this is done on the Community wiki: http://community.kde.org/Getinvolved/Testing. A page for brainstorming also exists if you have practical ideas on how to make this effort work: http://community.kde.org/Getinvolved/Testing/Brainstorming
We will use the beta phase to start testing, in coordination with distributions for providing packages, with the Bug Squad and with developers. Beta testers will be called for before the first beta and meantime we need to have all the documentation ready for them and specific goals set.
Hope you will join!

Saturday, February 18, 2012

Frameworks Day

So today was Frameworks 5 day. I was a bit disappointed not seeing more developers joining, to be honest. I thought I would come here only to help newcomers building the branch but in the end I started contributing too. Probably because the core developers are very patient and helpful. I think we did some good work but we need to sustain this effort in order to make progress in the next 2 months.
I see you can't wait contributing too (after all, if I can, surely you can too!) . Some common problems in porting to more Qt libs are listed here and you can volunteer for a task here. I chose an easy task which is to move some tests and to make sure they build (and pass!). Before committing, a core developer must approve your work.

Despite having the flu, I learnt a lot and would like to encourage you to do the same.
Thanks to ervin for organizing, to dfaure for being patient and fixing my build bug (and many more of course) and to all other people who are very nice to work with.

Friday, February 17, 2012

Reminder: tomorrow is Frameworks 5 Volunteer Day

From 10am to 6pm CET on Saturday February 18 on IRC Freenode #kde-devel channel, you are invited to join core developers to contribute to the new KDE Frameworks. Tasks will be prepared, ranging from quite easy to more difficult.
Pre-requisites: Qt 4.8, a build of kdelibs frameworks branch (note the you will need cmake 2.8.7 for it or the cmake git version and a clone of extra-cmake-modules). It is prefered that you do not install Frameworks at the same prefix as your other KDE prefix.
You can also read the Frameworks Community wiki page in order to learn more about Frameworks internals.

Hope you'll join!