On Tuesday 09 September 2014 10:57:44 Stefan Derkits wrote: > Hey all, > > I'm a Teaching assistant for the course Advanced Software > Engineering at the Vienna University of Technology.
> It is a course for master students in Software Engineering. In this > course the students have to run a project in a group of 4 - 6 > people. As they can choose freely what project they want to do (if > the scope is big enough) I was thinking of showing them some > projects they could do in KDE, because most of the self choosen > projects are actually pretty boring ;) > > The scope of the project is the following: > -) one to three distinct bigger features should be added to an > application (like in GSoC or SoK) > -) ideally these features would include every layer of the > application (so not only backend or GUI) > -) enough for 4 - 6 Students to work a total of 140 hours per > student (including project managment) between October and January > -) some students may have experience with C++/Qt, some not. But we > anyways offer a C++ & Qt crashcourse for another Bachelor level > course. -) they already have good programming knowledge (mostly > Java) and attended a basic Software Engineering course where they > did a preselected project > > What do I need from you? > > You have a project that could need some help? You can make or > already have a small description of your feature? The project fits > into the scope described above? Either you or someone else in your > project can mentor (like the GSoC or SoK mentors) the students? > > Then write me with the following data: > > -) Small Description of the project (all of them will be presented > to students in the preliminary discussion) > -) Mentor for this project > > If you have any questions, feel free to contact me (HorusHorrendus > @ IRC, personally @ Akademy in the hacking room) > > Stefan Hello Stefan, First, thank you very much for offering young and eager man power for helping KDE projects ;) The amount of help needed is certainly never falling below a point where it would become boring. Would it make sense we setup a dedicated wiki page for project suggestions like we did for GSoC and SoK? You could also browse the pages for previous projects that were not finished (or not even started). Otherwise, as a starting point, I would suggest to browse the brainstorm section on our KDE forum. A lot of features are summarized there, rated and voted by users and discussed together with developers. Additionally, our bug tracker has literally thousands open issues, many of them requiring larger structural changes that need planning and crafting beyond the typical "one line fix", and might also involve additions in underlying Qt libraries. Some of the higher voted ones are here: https://bugs.kde.org/buglist.cgi?votes=81&chfieldfrom=3650d&votes_type=greaterthaneq&chfield=%5BBug%20creation%5D&order=map_products.name%2Cbugs.bug_id&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&limit=0 (Feel free to lower the first number to see more entries :) A good software engineer does not only know how to plan and write new code, but also reads existing code written by others to analyze it and to plan improvements and there. If you have questions, please ask on this list or in the IRC channel #kde-devel on freenode servers. -- Christoph Feck http://kdepepo.wordpress.com/ KDE Quality Team
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
