2009 introspective

Hi...

I'm putting together a "where are we now, where are we going" snapshot of as
many of the "big pieces" in KDE 4 as possible, and I'd like some input from
you on DigiKam.

In particular, what I'm looking for are 2-4 bullet items for each of these two
questions:

* What have been the defining achievements in the last year?

* What are the main focus points and or goals for the project in 2009?


If you're feeling extra helpful, you might want to also provide some input on:

* What are the major pain points in your project right now?

* Outside of the core libs (kdecore, kdeui, kio, kfile) what are the most
critical pieces of KDE technologies that your project is relying on?


You can reply to me directly; I'll be collating and making public the results
when they are in ...

As an example of what I'm looking for, here's the answer set of Plasma:

In the last year:

        * Parity with KDE3 desktop/panels
        * Finished out the foundational pieces (extenders, activities, scripting..)
        * Moved libplasma to kdelibs

Focus points in 2009:

        * Ease of creating Plasma components (Plasmate)
        * Netbook interface
        * Media center components
        * Remote plasmoids
        * Social desktop features
        * Improved integration with Nepomuk and rest of workspace

Major point points:

        * x.org driver quality
        * QGraphicsView is still going through growing pains
        * newness of our own codebase resulting in larger #s of defects

Major technologies we rely (or will be relying) on:

        * x.org and kwin compositing features
        * QGraphicsView
        * Solid
        * Nepomuk



As for why I'm doing this survey, here's an excerpt from
http://aseigo.blogspot.com/2009/04/trailheads.html:

"The pre-4.0 development of KDE was helped along by everyone knowing what we
were striving towards: we had the Pillars, these new big chunks of technology
we were busy slotting into place so that we could build ever better
applications on top of; we had a renewed focus on clean, usable interfaces; we
were also aiming for beauty and greater platform independence.

The individual projects around the KDE universe all swirled around these
shared goals. Each headed in their own direction that reflected their own
interpretation of these goals as weighted by their development team in terms
of importance. Not remarkably, while there was variance in execution, there
was a remarkable harmony in the overall approach and results.

That didn't happen by accident: it happened because we were communicating with
each other about our goals and in-the-moment situations. I was part of only a
fraction of these conversations, but I remember the huge number of informal
meet ups both online and in person (part of my "coffee shop meetings around
the world" tour, or at least that's sometimes how it felt ;). It was inspiring
and helpful and marked a high water point in KDE community togetherness for
me.

We're into 2009 now and it's time to stoke those fires again."

Thanks for your time and energy in advance :)

--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software







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

[Gilles Caulier-4]

2009/5/4 Aaron J. Seigo <[hidden email]>:
> Hi...

Hi Aaron.

>
> I'm putting together a "where are we now, where are we going" snapshot of as
> many of the "big pieces" in KDE 4 as possible, and I'd like some input from
> you on DigiKam.
>
> In particular, what I'm looking for are 2-4 bullet items for each of these two
> questions:
>
> * What have been the defining achievements in the last year?

The KDE4/QT4 port of course + a lots of new features  (:=)))

If you want a list of new features, a resume can be found with 0.10.0 announce :

http://www.digikam.org/node/434

This includes development started since summer 2007 to March 2009 !

>
> * What are the main focus points and or goals for the project in 2009?

Next release will be 0.11.0, or perhaps 1.0 i don't know yet, this
depend of progress...

In this new release, a tool named Batch Queue Manager have been
implemented (trunk code):

http://www.digikam.org/node/427

This one is very important too and progress quickly :

http://www.digikam.org/node/439

In digiKam 0.10.0, not all code have been ported to Qt4 model/view. It
still few classes, as icon-view, folder-view, preview, and thumb-bar.
For 2 first ones, Marcel working on currently. It's a big job, because
it include a lots a features and regression tests. Also, this open to
includes new wish from users and close a lots of bugzilla entries.

A new first run assistant have been added recently to help new users
to setup digiKam :

http://www.digikam.org/node/442

Personnaly, i always work to improve digiKam under windows. I still 2
important bugs to solves, before to said that digiKam for Windows work
exactly as under Linux. I'm also played with last M$ compiler (pro
version) to be sure that all compile and run fine everywhere (i use a
dedicated computer at home only for that)

Andi as improved and factorized code of contextual menu everywhere.
Also Free rotation tool usability have been reviewed and improved a
lots.

We have a new developer named Matthias who start to make big patch for
digiKam, especially to improved Lens Autocorrection plugin and add new
batch tool to BQM.

>
>
> If you're feeling extra helpful, you might want to also provide some input on:
>
> * What are the major pain points in your project right now?

- Complete QT4 model port definitely. This is the priority.

>
> * Outside of the core libs (kdecore, kdeui, kio, kfile) what are the most
> critical pieces of KDE technologies that your project is relying on?
>

Ah.... 2 ones : Marble and Phonon.

We wait 2 important features :

- Marble : to be able to display region selection over a map : we can
already make a selection and saved it to digiKam DB to perform a
search, but later marble is not yet able to display this region over
the map... it's an important usability details

- KDELibs/Phonon, is not yet able to render preview of videos. It a
huge regression compared to KDE3. A lots of users wait for that.We
know some hack and unofficial solution to wrap around but it's really
time to have a real solution in kdelibs.

Note : We plan to do another Coding Sprint this year, as in 2008 :

http://www.digikam.org/drupal/374

Same place : Genoa.
Date : September/ October 2009. Not yet sure.
Peoples : same than 2008 + new one (Andi, Mathias, Luka, etc...)

The usual question (:=))) : KDE-ev can sponsorship this event ?

Best

Gilles

PS: to others developers : please don't hesitate to respond in this
thread if i forget something... Thanks in advance
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

lunedì 04 maggio 2009 alle 21:56, Aaron J. Seigo ha scritto:

> Hi...
>
> I'm putting together a "where are we now, where are we going" snapshot of as
> many of the "big pieces" in KDE 4 as possible, and I'd like some input from
> you on DigiKam.
>
> In particular, what I'm looking for are 2-4 bullet items for each of these two
> questions:
>
> * What have been the defining achievements in the last year?

As far as i can say good digikam and kipi-plugins release for kde4.
>
> * What are the main focus points and or goals for the project in 2009?

Adding new functionalities, get back some missed plugins (better re-write them
from scratch), and thanks to Gilles a real multiplatform presence for digikam
and kipi-plugins.

> If you're feeling extra helpful, you might want to also provide some input on:
> * What are the major pain points in your project right now?
k3b is not finished yet and i've missed a good irc client into kde4. kopete was mine
in kde3 i could use it for jabber, msn, yahoo and irc one client more servers :D

> * Netbook interface
I can confirm an already great work here :D
 
> Thanks for your time and energy in advance :)

Maybe we can talk about a new code sprint event in the near future :)

Angelo

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

[Gilles Caulier-4]

2009/5/5 Gilles Caulier <[hidden email]>:

> 2009/5/4 Aaron J. Seigo <[hidden email]>:
>> Hi...
>
> Hi Aaron.
>
>>
>> I'm putting together a "where are we now, where are we going" snapshot of as
>> many of the "big pieces" in KDE 4 as possible, and I'd like some input from
>> you on DigiKam.
>>
>> In particular, what I'm looking for are 2-4 bullet items for each of these two
>> questions:
>>
>> * What have been the defining achievements in the last year?
>
> The KDE4/QT4 port of course + a lots of new features  (:=)))
>
> If you want a list of new features, a resume can be found with 0.10.0 announce :
>
> http://www.digikam.org/node/434
>
> This includes development started since summer 2007 to March 2009 !
>
>>
>> * What are the main focus points and or goals for the project in 2009?
>
> Next release will be 0.11.0, or perhaps 1.0 i don't know yet, this
> depend of progress...
>
> In this new release, a tool named Batch Queue Manager have been
> implemented (trunk code):
>
> http://www.digikam.org/node/427
>
> This one is very important too and progress quickly :
>
> http://www.digikam.org/node/439
>
> In digiKam 0.10.0, not all code have been ported to Qt4 model/view. It
> still few classes, as icon-view, folder-view, preview, and thumb-bar.
> For 2 first ones, Marcel working on currently. It's a big job, because
> it include a lots a features and regression tests. Also, this open to
> includes new wish from users and close a lots of bugzilla entries.
>
> A new first run assistant have been added recently to help new users
> to setup digiKam :
>
> http://www.digikam.org/node/442
>
> Personnaly, i always work to improve digiKam under windows. I still 2
> important bugs to solves, before to said that digiKam for Windows work
> exactly as under Linux. I'm also played with last M$ compiler (pro
> version) to be sure that all compile and run fine everywhere (i use a
> dedicated computer at home only for that)
>
> Andi as improved and factorized code of contextual menu everywhere.
> Also Free rotation tool usability have been reviewed and improved a
> lots.

A new blog entry is done for details about this subject. Look here :

http://www.digikam.org/node/445

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