[Digikam-devel] How to support the digikam team

[Sebastian Roeder]

Sorry for my late reply, I have been busy the week.

> On Monday 23 January 2006 00:43, Sebastian R?der wrote:
> > Now I think about how I can help the team a little, cause there is not so
> > much man power. I am just starting to learn C++ (later QT / Kdevelop to
> > come) so on the coding front I might not be of any help atm.
>
> Do you know the Junior Jobs?
> These reports, marked with JJ: at bko, are especially for beginners.

Yes, I had a short look at them. A good starting point for me once my C++
skills improve ;-) Btw didn't found a kipi/digikam related one in JJ.
>
> > My knowledge in web administration is very limited, too but in case the
> > HP needs some support we could discuss whether I am of any help.
>
> Since the migration to drupal, there is no need anymore.

OK

> > What comes into my mind is managing bugs at bko, exspecialy finding dups
> > and such. This might be a good start to help you out and if you want we
> > can talk about it so I might help with coordination tasks.
>
> But this would be very helpful. If you think, jobs are easy to solve, you
> can mark them as JJs (or ask us before). And solve them later, when you
> better know C++/kde/qt ;-)
> Or try to reproduce  reported bugs, as we did yesterday with the konqi
> problem.

Yes I think this is the best point to start (while behind the scenes I learn
C++/qt/kdevelop). I will search for dups and try to reproduce reported
errors. And there is the great task to move bugs form digikam to kipi etc.

Maybe the next step would be helping out in making the tarballs (but I am in
no way experienced here). I would like to provide some nightlys some day (say
once a week) that make sure they are not terribly broken and to prevent
people from huge extragear downloads. That would hopefully lead to more user
feetback on "unstable" stuff and prevent grave mistakes to slip into the
releases. But thats a long way to go ...

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

[Gilles Caulier]

> Maybe the next step would be helping out in making the tarballs (but I am
> in no way experienced here).

I love this idea...

Next week, from stable KDE svn branch, DigikamlmagePlugins need to be released
in 0.8.1 version. Are you interressed to do it ?

If yes, take a look in PACKAGING file from svn digikam directory, and let's me
hear if you need more informations to do it...

Gilles

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

[Sebastian Roeder]

> > Maybe the next step would be helping out in making the tarballs (but I am
> > in no way experienced here).
>
> I love this idea...
>
> Next week, from stable KDE svn branch, DigikamlmagePlugins need to be
> released in 0.8.1 version. Are you interressed to do it ?
>
> If yes, take a look in PACKAGING file from svn digikam directory, and let's
> me hear if you need more informations to do it...
> Gilles

 
OK, had a look at the PACKAGING file. I think I can process the steps
described there (thanks to Toma for the detailed "walkthrough").

When it helps the team, e.g. giving Toma more time to coding I will do the
packaging. Let's talk about the time frame. I have enough time this week to
do this I'd say. Only problem might be that my Inet connection will get some
maintainance periods this week and I hope the guys do not make to much
problems.

I would say I use the week days to make myself familar with SVN and target the
upload of the tarball for internal testing on friday, So maybe we can have a
RC1 on monday. Is this OK? Your comments please.

I need SVN (write) access til thursday or something I think - it would be nice
if someone could guide me a little in this subject.

For sure I will post a question on how to get digikam working from
inside /home (parallel install to stable gentoo ebuild in /usr). I always
failed at this point cause digikam couldn't recognize my KDE install. I have
to adjust my path somehow.

A yes, for the testing: should the testing of my image-plugins tarball be done
against digikam(core)-0.8.1 release or against 0.8.x Branch from SVN (fresh
checkout)?

Enough questions for the moment ;-)
Regards, Sebastian    
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Joern Ahrens]

On Monday 30 January 2006 12:54, Sebastian Röder wrote:

> > > Maybe the next step would be helping out in making the tarballs (but I
> > > am in no way experienced here).
> >
> > I love this idea...
> >
> > Next week, from stable KDE svn branch, DigikamlmagePlugins need to be
> > released in 0.8.1 version. Are you interressed to do it ?
> >
> > If yes, take a look in PACKAGING file from svn digikam directory, and
> > let's me hear if you need more informations to do it...
> > Gilles
>
> OK, had a look at the PACKAGING file. I think I can process the steps
> described there (thanks to Toma for the detailed "walkthrough").
>
> When it helps the team, e.g. giving Toma more time to coding I will do the
> packaging. Let's talk about the time frame. I have enough time this week to
> do this I'd say. Only problem might be that my Inet connection will get
> some maintainance periods this week and I hope the guys do not make to much
> problems.
>
> I would say I use the week days to make myself familar with SVN and target
> the upload of the tarball for internal testing on friday, So maybe we can
> have a RC1 on monday. Is this OK? Your comments please.

Take the time you need. It doesn't matter if we will release some days later.

> I need SVN (write) access til thursday or something I think - it would be
> nice if someone could guide me a little in this subject.
You neither need write access for packaging nor testing. The tarballs aren't
stored in svn.

> For sure I will post a question on how to get digikam working from
> inside /home (parallel install to stable gentoo ebuild in /usr). I always
> failed at this point cause digikam couldn't recognize my KDE install. I
> have to adjust my path somehow.
add_root=/opt/kde-svn
export KDEDIRS=$add_root:
export PATH=$add_root/bin:$PATH
export LD_LIBRARY_PATH=$add_root/lib


... Jörn

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

[Gilles Caulier]

Le Lundi 30 Janvier 2006 13:20, Joern Ahrens a écrit :
> > I need SVN (write) access til thursday or something I think - it would be
> > nice if someone could guide me a little in this subject.
>
> You neither need write access for packaging nor testing. The tarballs
> aren't stored in svn.

Excepted to update release number, changelog and others stuff during
Packaging...

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

[Gilles Caulier]

Le Lundi 30 Janvier 2006 13:20, Joern Ahrens a écrit :
> > I would say I use the week days to make myself familar with SVN and
> > target the upload of the tarball for internal testing on friday, So maybe
> > we can have a RC1 on monday. Is this OK? Your comments please.
>
> Take the time you need. It doesn't matter if we will release some days
> later.

No need to make an RC1. There are only bugfix/memory leak on
DigikamImagePlugins.

Gerhard Kulzer will commit a fix during this week in all plugins .rc files to
drive properly keyboard shortcuts on IE/showfoto. Packaging actions must be
done after that, but you can trying to make a tarball in your computer before
for testing

About svn, personnally, i'm using esvn. It's work fine...

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

[Sebastian Roeder]

> > I would say I use the week days to make myself familar with SVN and
> > target the upload of the tarball for internal testing on friday, So maybe
> > we can have a RC1 on monday. Is this OK? Your comments please.
>
> Take the time you need. It doesn't matter if we will release some days
> later.

OK. But I think the time frame is quite right.

> > I need SVN (write) access til thursday or something I think - it would be
> > nice if someone could guide me a little in this subject.
>
> You neither need write access for packaging nor testing. The tarballs
> aren't stored in svn.

Yes that's right - but the PACKAGING file is also about taging and branching,
and that would need SVN write access. But if this part is managed by another
person from the team, no problem.

> > For sure I will post a question on how to get digikam working from
> > inside /home (parallel install to stable gentoo ebuild in /usr). I always
> > failed at this point cause digikam couldn't recognize my KDE install. I
> > have to adjust my path somehow.
>
> add_root=/opt/kde-svn
> export KDEDIRS=$add_root:
> export PATH=$add_root/bin:$PATH
> export LD_LIBRARY_PATH=$add_root/lib

Nice, will try that. Thanks Joern

> > You neither need write access for packaging nor testing. The tarballs
> > aren't stored in svn.
>
> Excepted to update release number, changelog and others stuff during
> Packaging...

For the tarball I do this on my local checkout and if another person manages
SVN I can send him the updated changelog. When I get SVN access I can do it
myself - as you like it.

> No need to make an RC1. There are only bugfix/memory leak on
> DigikamImagePlugins.

OK, will call it 0.8.1 and that's it.

> Gerhard Kulzer will commit a fix during this week in all plugins .rc files
> to drive properly keyboard shortcuts on IE/showfoto. Packaging actions must
> be done after that, but you can trying to make a tarball in your computer
> before for testing

Yes I do my tests before and have a look when Gerhard's fix comes in.

> About svn, personnally, i'm using esvn. It's work fine...

Ok, might try that. Or stick to the command line, not sure yet.

BTW I can be found on your IRC with the nickname sebroeder.
As far as the emotional debate goes about kipi future on kde-imaging list (I
can quite understand that you guys can not hear the word "cooperation") I
would say it's a good idea when the digikam devels write down a summary of
there viewpoint/arguments and its results for kipi so that this discussion
doens't go on forever in this mood. Just one text that makes things clear.
Just an idea, though. Tried that myself at the beginning of the debate and I
think it helps.

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