[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Watching mentors and nifticlib



On Sun, 11 Nov 2007, Michael Hanke wrote:

I totally agree. I just wanted to point to the constant shortage of DDs
involved in Debian-med.

Well, I have the feeling that it becomes better and the idea was that
if we have tools that gives an easy overview what should be done we
could take some workload from the view of people.

And because you posted it to debian-devel I
thought it might be useful to mention this as a place to get involved...

Well - sometimes it is me who is doing really stupid things. ;-)
This posting

    http://lists.debian.org/debian-devel/2007/11/msg00336.html

was intended to be send to Debian-Med.

The mentors interface provides a way to mark packages as 'looking for
sponsors' and there is also sponsors.debian.net. It is however the
sponsorees task to advertise the packages appropriately.

I'm just thinking about a "SponsoredBy" field in our task files ...

;-) Yeah, in an ideal world we would all use the same tools. But back in
real life I use the tools that are the most compatible with _me_ and
that _I_ am the most productive with. Having a sponsor that shares my
views on the choice of weapons puts _me_ in the position to work
productively.

Well, it was not my intention to criticise this.  I just wanted to
point out that it becomes more complex than the usual emacs-vim-flamewar
because it finally does not matter for other people of your group which
editor you are using.  Ii do not want to join any flame war about tools
which finally makes no sense in a real world - I'm looking for means
to overcome the drawbacks for our particular group.  But at least
David acknowledged that there might be a way to work around this at
least for the web tool.

IMHO if ones relies on the ressources that debian-med provides (tools,
sponsors, feedback) then one should be as compatible with debian-med as
possible. In my case however, I already have a working environment that
lets me contribute to debian-med without depending on its ressources.

Sure, nobody will blame you about this.  Any contribution is welcome but
I'm just looking for means to make the cooperation as smooth as possible.

So as long as the work is done right there should be no problem. If however
someone stopped doing so, debian-med should hijack the packages an put them
in its SVN. Of course, always given the fact that it has enough manpower
to do so.

It makes no sense if people are cross-checking in and out between
different repositories.  This would be a real wast of time - even if we
would have more man power.

Personally I don't feel like you about 'the single repository', but only
from the technical perspective, because it might limit some people that
lack the required capabilities or simply have different preferences
(which doesn't mean that they cannot achieve optimal results in their very
own way). The general notion of a centralized gateway to _all_ debian-med
related code in Debian is definitely an advantage.

OK.  I'm just waiting for the next maintainer who prefers bzr. ;-)

Kind regards

            Andreas.

--
http://fam-tille.de



Reply to: