Re: libqsearch under Debian Med group maintenance? (corrected)
Hi Andreas,
I will try to upload a fix for the bug and try to transfer to
debian-med team maintenance. I have a newborn son (2 weeks old) and a
computer crash (also 2 weeks old) for which I am expecting to receive
replacement parts by mail tonight. I expect to repair / replace the
broken system in the next few days and then on the weekend I will try
to do these two things. I must admit that although I have frequently
cooperated with many Debian team members on specific bugs / patches /
questions in my packaging, I have never yet formally transferred any
of my packages to team maintainence. I am looking forward to figuring
out this process better in October with libqsearch and other packages.
Any more info you might provide in this regard would be useful to me.
Thanks for the kind information already sent; it is much appreciated.
Best regards,
Rudi
On Wed, Sep 30, 2009 at 6:01 AM, Andreas Tille <andreas@an3as.eu> wrote:
> Hi Rudi,
>
> when I recently watched our bugs page [1] I stumbled upon the fact that
> libqsearch is not yet under team maintenance of Debian Med Packaging
> Team but included into our tasks pages. It also might fit under the
> hood of Debian Science team - but I'm currently running a QA effort on
> Debian Med tasks - so finally it is your decision to which team you tend
> more (in case you agree with group maintenance).
> Given the fact that I have the impression that the quality of our
> major packages increased since we are doing so I wonder whether you want
> to follow our group policy[2] or Debian Science group policy[3]
> and move to group maintenance.
>
> BTW, any chance that you upload the fix for #533784?
>
> Kind regards
>
> Andreas.
>
> [1] http://debian-med.debian.net/bugs/bio-dev.html
> [2] http://debian-med.alioth.debian.org/docs/policy.html
> [3] http://debian-science.alioth.debian.org/debian-science-policy.html
>
> --
> http://fam-tille.de
>
--
Git, Hg (Mercurial), and Subversion (svn) hosting over SSH
http://sshcontrol.com/
Reply to: