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

Re: Policy for Debian Qt/KDE Maintainers Group



On Mon, Oct 20, 2003 at 01:39:48AM +1000, Ben Burton wrote:
> 
> > Can you (esp. the people mentioned as "base members") read it and tell us
> > whether they want to lodge objections and if so what needs to be changed
> > in their opinion? And can those who do not have any objections please let
> > us know that too?
> 
> Further to my previous email:  My second question is how the proposed
> development model (upload if you're the primary maintainer or have their
> blessing) differs from the current model (upload if you're the debian
> maintainer or NMU if you have their blessing)?
> 
Infact, points 2.4, 2.5, 2.6 and 2.7 were included not only for but especially 
for you -- you complained about "feeling unhappy with justifying all changes
you do to others". However, point 2.8 explicitly advances team work and all
members of the team are encouraged to make use of it. The point here is to
_allow_ others to commit changes but to _disallow_ them if one feels unhappy
with it.

> I guess I'm specifically wondering what advantages the new system would
> have over the current system (which is more or less communal CVS
> commits, maintainer uploads).
> 

The advantages of the new system IMHO are:

1. Advance team work and communication amongs the maintainers of the current
KDE related packages

2. Be more effective with bug handling (Since all bugs will go to the mailing
list). Shared knowledge is good knowledge.

3. Spread the amount of work KDE packages produce and thus keep KDE in a state
that is generally better than the way it was until now.

> I think the biggest inconvenience I forsee is with the BTS - I'd have to
> start keeping track of multiple maintainer email addresses, and it will
> be more difficult to track the bugs in the packages that I'm looking
> after amongst the significant noise of kdelibs, kdebase, qt, etc.
> 
There is no real inconvenience. Since I guess you know the names of the
packages you maintain, you can still easily find the bugs which belong 
to your packages by searching for the package name instead of the name 
of the maintainer.

> Ben. :)


-- 
  .''`.   Martin Loschwitz           Debian GNU/Linux developer
 : :'  :  madkiss@madkiss.org        madkiss@debian.org
 `. `'`   http://www.madkiss.org/    people.debian.org/~madkiss/
   `-     Use Debian GNU/Linux 3.0!  See http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: