contributing some programming work

[Johannes Wienke-3]

Hi @all,

I just registered here to contribute with some programming work. Gilles
already told me that most of the work is coordinated in bugzilla but I
still got some questions about the normal workflow:

Is there any prioritization on which features to implement first?

What's the decision process if a feature conflicts with another one or
somehow doesn't fit the general application too well?

Regards,
Johannes


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Johannes,

In fact, there is no very high priority currently, excepted to
stabilize code for 1.0.0 of course...

The implementation for new features will be closed in digiKam after
1.0.0-beta5. We must cleanup bugzilla to publish a suitable version of
digiKam. this is not the best development stage (less exciting), but
it's necessary.

In kipi-plugins, it's different. both package follow different release
plans. I will certainly release 0.7.0 this week end. More than 20 bugs
have been fixed since 0.6.0. After that new features can be
implemented. Look in Bugzilla, for ex about picasaweb, Gallery, of
flickr tool.

There is also a thread about to implement a new wikimedia management
plugin. I'm in contact with this guy :

http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/

If you is interested...

In other words, take your choose in bugzilla (:=)))...

Gilles





2009/9/23 Johannes Wienke <[hidden email]>:

> Hi @all,
>
> I just registered here to contribute with some programming work. Gilles
> already told me that most of the work is coordinated in bugzilla but I still
> got some questions about the normal workflow:
>
> Is there any prioritization on which features to implement first?
>
> What's the decision process if a feature conflicts with another one or
> somehow doesn't fit the general application too well?
>
> Regards,
> Johannes
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Johannes

At 13/14/15 november, we plan to do a coding sprint in Germany, near
Düsseldorf. Take a look here :

http://websvn.kde.org/*checkout*/trunk/extragear/graphics/kipi-plugins/project/CodingSprint2009.ods

Do you want to contribute to this event. We can share like this
experience and tips about coding. It's a fun moment between
developpers...

Gilles

2009/9/23 Gilles Caulier <[hidden email]>:

> Johannes,
>
> In fact, there is no very high priority currently, excepted to
> stabilize code for 1.0.0 of course...
>
> The implementation for new features will be closed in digiKam after
> 1.0.0-beta5. We must cleanup bugzilla to publish a suitable version of
> digiKam. this is not the best development stage (less exciting), but
> it's necessary.
>
> In kipi-plugins, it's different. both package follow different release
> plans. I will certainly release 0.7.0 this week end. More than 20 bugs
> have been fixed since 0.6.0. After that new features can be
> implemented. Look in Bugzilla, for ex about picasaweb, Gallery, of
> flickr tool.
>
> There is also a thread about to implement a new wikimedia management
> plugin. I'm in contact with this guy :
>
> http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/
>
> If you is interested...
>
> In other words, take your choose in bugzilla (:=)))...
>
> Gilles
>
>
>
>
>
> 2009/9/23 Johannes Wienke <[hidden email]>:
>> Hi @all,
>>
>> I just registered here to contribute with some programming work. Gilles
>> already told me that most of the work is coordinated in bugzilla but I still
>> got some questions about the normal workflow:
>>
>> Is there any prioritization on which features to implement first?
>>
>> What's the decision process if a feature conflicts with another one or
>> somehow doesn't fit the general application too well?
>>
>> Regards,
>> Johannes
>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>>
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel