[Digikam-devel] Re: Needing ideas for Rosedu's Open Source Development Course

[Gabriel Voicu]

Hi Gilles,

Thank you very much for this long answer! I will speak today with the
organisers and see what they have to say.

Also, be sure that I was not thinking in starting a junior job project
inside digikam's core, because it's under heavy development for the 2.0
version. The ideal project would be modifying a GUI for a plugin(album or
KIPI, doesn't matter).
Do you have in mind a plugin that should need GUI refactoring? If yes,
please let me know, because I couldn't find any example on Bugzilla.

Best Regards,
Gabriel Voicu

On Tue, Jan 4, 2011 at 9:54 AM, Gilles Caulier <caulier.gilles at gmail.com>wrote:

> Hi Gabriel,
>
> In general, for junior jobs, i recommend to take a look into components
> outside digiKam core. Why ?  because it can have side-effect with the whole
> program to touch in this area.
>
> It must be better to take a look in plugins.
>
> You have 2 way :
>
> 1/ plug-ins for image editor.
> 2/ plug-ins for album gui (kipi-plugins).
>
> Now how to select job ? Use bugzilla and look Wishes files by preference
> order. Bugs can be more complex to fix and can take a while.
>
> In all case, use bugzilla for each entry found and post messages and
> patches by this way. This is the best QA work-flow.
>
> I don't recommend to use kde review tool. It's not link to bugzilla, and
> it's complex to follow in time.
>
> Do not use devel mailing list directly. Use bugzilla instead. All post from
> bugzilla are posted in this mailing list.
>
> For new idea, i recommend also to use bugzilla, and create new entries with
> attached patches.
>
> Like you can see, the main tool is bugzilla.
>
> Another idea is to review all entries with patch attached. All these
> entries have "[patch]" annotation in the title. It's easy to find these
> entries with bugzilla search engine.
>
> Now the ultimate question which code to patch ?
>
> - If patch is not too intrusive, 1.x from trunk can be patch, and later
> code backported to GoSC 2010 branch.
> - If patch is intrusive, it's will be better to use GoSC2010 branch.
>
> Don't forget that trunk is stable used in production, and we trying to
> stabilize this code now. We plan 1.8 and probably 1.9 release including
> minors changes.
>
> I hope these tips will help you in this task...
>
> Best
>
> Gilles Caulier
>
> 2011/1/4 Gabriel Voicu <ping.gabi at gmail.com>
>
> Hi,
>>
>> Thank you very much, Martin, for the ideas! They indeed sound good for
>> this kind of project.
>>
>> Gabriel
>>
>>
>> On Tue, Jan 4, 2011 at 1:21 AM, Martin Klapetek <
>> martin.klapetek at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I remember seeing couple UI mockups here on ML, but noone really got
>>> through (what happened to that new statusbar thinggy?). So maybe after
>>> some consultation with Gilles or Marcel, you could work on these. Also
>>> adding some decent animations could refresh the UI. You could also
>>> help porting the rest of Qt3 stuff to Qt4/kdelibs (btw. the thumbbar
>>> centering of the selected image doesn't work, I tried to fix that, but
>>> with no luck. Also the Qt4 views have better methods for handling
>>> this).
>>>
>>> That's all I can think of right now :)
>>>
>>> Marty
>>>
>>> On Monday, January 3, 2011, Gabriel Voicu <ping.gabi at gmail.com> wrote:
>>> > Hi everyone,
>>> > ROSEDU (Romanian Open Source Education) people are organising an Open
>>> Source Development Course, where they teach a group of selected students
>>> (aprox. 30 students) about tools used in open source development. Also,
>>> during the course, the students will be grouped in teams of 3-4 to work on a
>>> contribution to an existing open-source software. Each group of students is
>>> coordanated by a menthor.
>>> >
>>> > Because I participated in the last year GSoC, the organisers invited me
>>> to be a menthor for a team and propose a project related to Digikam/KIPI
>>> Plugins. Now, I would like to know if you have some junior jobs for Digikam
>>> or KIPI Plugins that will not involve more than 5-6 hours/week for 7-8
>>> weeks. The projects should contains easy things to do, like modifying a UI
>>> or make some small changes in different parts of Digikam. I mention that the
>>> course will be from the start of March until the the start/middle of May.
>>> >
>>> > If you have any ideas, please tell me as soon as possible, because I
>>> should speak with the organisers until Wednesday 5th January. Also, it's no
>>> problem if you tell me after 5th January. :-)
>>> >
>>> > Best wishes,
>>> > Gabriel
>>> >
>>> _______________________________________________
>>> Digikam-devel mailing list
>>> Digikam-devel at kde.org
>>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>>
>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> Digikam-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>>
>
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20110105/fabdf389/attachment.html>