> I'm sure your project is very interesting, but it falls short of the
> scope for having the list crated on vger.
>
> Generally, we host lists for kernel projects and their tools for which
> they are already upstream or for which their upstream acceptance is
> imminent.
>
> I've never seen the BATMAN kernel bits even submitted for review on
> netdev(a)vger.kernel.org and getting your code upstream via submission
> there would be a prerequesite before we could be discussing a mailing
> list on vger.
>
> I'm not even sure the getting your kernel bits upstream is even
> something you want, or whether the networking maintainer (that's
> me :-) would consider your code and approach acceptable.
Hi David
Let me fill in some of the background.
We have been talking to GregKH about submitting the code to staging.
Greg has said he is happy to accept the patches for staging, since the
code is totally self contained, mostly passed checkpatch apart from
some long lines, sparse clean etc. And we have a TODO list of things
we think need fixing before it can leave staging.
However, at the moment we are using a closed list. Your reply to this
email is going to bounce from the list server. Before we submit to
staging and hopefully start getting feedback from kernel experts, we
would like to move to an open list. The current list server does not
have good enough Spam filtering for an open list. So we are looking
for a list server provider who we could use. vger seemed like an
obvious choice.
Is likely acceptance in staging sufficient for "...for which their
upstream acceptance is imminent."?
Thanks
Andrew