Asking for help maintaining several gtk/gnome C++ bindings

[manphiz]

Otavio Salvador wrote:
 > manphiz <manphiz at gmail.com> writes:
 >
 >> As for myself, I'm not a DD, and haven't packaged anything in Debian
 >> yet. I've finished reading New-Maintainer's Guide, and am reading 
Debian
 >> Developer Reference and Debian Policy. I've gained some basic knowledge
 >> of debhelper commands, and keep learning as well. I've tried packaging
 >> some home-made packages which seem working.
 >
 > The best way is you to start proposing patches for the bugs and then
 > start proposing the diffs need to update the packages for lastest
 > versions. This would people start to look at your work and help giving
 > tips about better ways of doing things.
 >
 > After this, you can end added on pkg-gnome project and start to commit
 > the changes yourself and just ask people to sponsor the uploads.
 >
 > IMHO, this is the best way to start. I offer help to review your
 > proposed patches before them being send and giving hints about how to
 > make things too.
 >
Thanks for the advice. Currently I've already proposed a patch (a 
.diff.gz) against the newest version of glibmm2.4 in my 3rd post of bug 
#442828. It's the base of all C++ bindings, so I'd like to work on this 
first. As glibmm development keeps maintaining the ABI compatibility, 
there's not many things to do. Although the binary packages haven't 
splitted the doc into a -doc package yet, I was told such a change is 
not supposed to happen in a NMU, so I kept the structure intact (I'm 
planning to let this change take place when I get the authority to 
maintain glibmm2.4). With a little glitch of my forget to change the new 
watchupstream address, the patch should be usable combined with upstream 
2.14.1 release package. Please check, and provide a NMU if possible. Thanks.