netdev - Re: [PATCH] MAINTAINERS: Remove Sven Eckelmann from BATMAN ADVANCED

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:	Wed, 22 Jun 2011 01:16:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sven@...fation.org
Cc:	netdev@...r.kernel.org, b.a.t.m.a.n@...ts.open-mesh.org
Subject: Re: [PATCH] MAINTAINERS: Remove Sven Eckelmann from BATMAN ADVANCED

From: Sven Eckelmann <sven@...fation.org>
Date: Wed, 22 Jun 2011 09:41:45 +0200

> On Tuesday 21 June 2011 14:35:15 David Miller wrote:
>> All of this effort was placed to get this thing merged into the
>> main tree, and then moved out of staging.
> 
> "Shooting the messenger" - I think that is the matching phrase. Just try to 
> grep my name in the net/batman-adv/ and you will see it nowhere.

It is everywhere as far as I am concerned, because you're the only person
actually keeping upstream maintained and in sync.

> The problem is that I am probably the most unimportant person in the
> whole project.

>From my perspective, this is not true.  You are the most important
person.  And this is because the people writing the code obviously
don't care enough about upstream to do any merges themselves.  Yet
you do.

> But at least I was good enough to send some patches around which
> were accepted or made by other people. I was also not the person
> behind the whole Linux-merge thing, but only some kind of
> marionette.

When we agree to allow someone to merge something into the tree,
especially a significant piece of code like batman-adv, there are some
impressions we want to have beforehand.

And one such impression we want is that there is going to be someone
continuing to be active maintaing the code upstream, even after the
code is merged.

Otherwise we get "merge and run" scenerios.  As networking maintainer,
I've been burnt by this several times.

If you're the only person who had the energy and motivation to do the
merges of this code, then you're only person we know that can keep up
with the expectations we had when we agreed to merge the code.

If you step down, that trust has been broken, and we're left with a
rotting pile of poo in the tree because it's unlikely anyone else is
going to step up and keep things maintained upstream as you did.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html