lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 30 Apr 2007 13:21:29 +0200
From:	Helge Hafting <helge.hafting@...el.hist.no>
To:	Uwe Bugla <uwe.bugla@....de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and	pseudo-authorities

Uwe Bugla wrote:
> In this ten Emails you will yourself see the intellectual and technical proof in how far Mr. Chehab is acting with nothing else but:
>
> a. Lies
> b. Unproven thesis
> c. Stigmatizations
>
> and so on.
>
> THIS MAN HAS NO IDEA, BUT HE HAS THE POWER!
>   
Please note that there are ways to replace a bad maintainer. 
We still try to keep it polite.

But note that you can't have someone "fired", no matter how bad they
do their job.  A bad maintainer is usually better than none - the bad
maintainer might improve. Or at least get some simple stuff done.

You therefore replace a bad maintainer by taking over the position. 
Contact whoever is above the maintainer (Linus or some other
higher-level maintainer). You explain the problem, and you must also
show that you have the time and knowledge to do a better job. 
You can, for example, maintain the same subsystem in parallel.  After a 
while,
all interested parties sees that your tree works better and that
communicating with you is easier.
If you aren't prepared to do this - then you have to live with the current
maintainer.  There is no staff ready to replace maintainers after
complaints, a volunteer doing a better job is always necessary.

Helge Hafting



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ