pkg kde talk - Aug 2006 - Maintainer sought for the dbus qt(3) bindings

Hi,

  Some time ago dbus was finaly modularized. Yesterday i''ve uploaded
dbus 0.91,
  the glib bindings and the python bindings to experimental (in NEW currently.) 

  To be able to make the transition in unstable, somebody needs to
  maintain/package the qt3 bindings. And as i basically know nothing about
  qt/kde i would prefer it that somebody isn''t me :)

  Can the debian KDE take care of this ?

  Sjoerd
PS: Please CC me as i''m not on the list
-- 
Take an astronaut to launch.

On Tuesday 08 August 2006 15:42, Sjoerd Simons wrote:
>   Some time ago dbus was finaly modularized. Yesterday i''ve
uploaded
> dbus 0.91, the glib bindings and the python bindings to experimental
> (in NEW currently.)
>
>   To be able to make the transition in unstable, somebody needs to
>   maintain/package the qt3 bindings. And as i basically know nothing
> about qt/kde i would prefer it that somebody isn''t me :)
You may know nothing about Qt/KDE, but you probably don''t need to know 
all that much to maintain a split-off version of your old codebase. 
Conversely, the KDE team may know a lot about KDE, but, while I can''t 
speak for everyone on the team, I certainly know nothing about dbus, 
and that''s a real problem when starting to maintain something new.

Thus I think it would make more sense for you to maintain the Qt3 
bindings, with a promise of plenty of testing and help-whenever-needed 
from us. If the new Qt3 bindings are basically just the old ones split 
out, then it shouldn''t be hard or require much work. And once KDE 4.0 
is out, then the old bindings will go away anyway.

How will the Qt4 bindings be handled, BTW?

Cheers,
Christopher Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 249 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20060808/96280128/attachment.pgp

On Tue, Aug 08, 2006 at 07:02:29PM -0400, Christopher Martin
wrote:
> On Tuesday 08 August 2006 15:42, Sjoerd Simons wrote:
> >   Some time ago dbus was finaly modularized. Yesterday i''ve
uploaded
> > dbus 0.91, the glib bindings and the python bindings to experimental
> > (in NEW currently.)
> >
> >   To be able to make the transition in unstable, somebody needs to
> >   maintain/package the qt3 bindings. And as i basically know nothing
> > about qt/kde i would prefer it that somebody isn''t me :)
> 
> You may know nothing about Qt/KDE, but you probably don''t need to
know
> all that much to maintain a split-off version of your old codebase. 
> Conversely, the KDE team may know a lot about KDE, but, while I
can''t
> speak for everyone on the team, I certainly know nothing about dbus, 
> and that''s a real problem when starting to maintain something new.
That''s understandable. I hoped there was at least someone in the KDE
team who
knows a little more then nothing about dbus ;)
> Thus I think it would make more sense for you to maintain the Qt3 
> bindings, with a promise of plenty of testing and help-whenever-needed 
> from us. If the new Qt3 bindings are basically just the old ones split 
> out, then it shouldn''t be hard or require much work. And once KDE
4.0
> is out, then the old bindings will go away anyway.
Packaging work is one thing. Maintaining is something else. While i
don''t
expect a lot of problems with the split-out bindings (i never got bugs about
the qt bindings bugs when it was still one big package), i never feel very
comfortable whith things i can''t really test :)..
> How will the Qt4 bindings be handled, BTW?
They are part of QT4.2. As (luckily) nothing in debian depends on them, the
current packages are going to be removed as soon the move to modular in
unstable is made.

  Sjoerd
-- 
Anyone who imagines that all fruits ripen at the same time
as the strawberries, knows nothing about grapes.
		-- Philippus Paracelsus