I only hope that one more packager will mean acceleration of the process
and not the opposite - so we probably should coordinate and divide the
work...
I am more worried about the current status in Debian unstable due to the
gcc-5 transition. Dunno how (much) it will affect the upload to the archive.
So maybe we should create the initial package for Debian stable and then
upgrade it for unstable (probably the diff will be minimal)? I might be
wrong, but I think that all those problems with indirect dependencies
might postpone the upload, but they should not affect the content of the
package. Thats why I suggest to create the package for stable (which can
be done now) and then wait until the problems with indirect dependencies
settle down. Who knows, maybe it will happen in sync with us finalizing
the initial package...