public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] VGER mailing list request
@ 2009-10-04  3:15 Jacob Marble
  2009-10-04  7:38 ` Andrew Lunn
  2009-10-04 17:23 ` Andrew Lunn
  0 siblings, 2 replies; 5+ messages in thread
From: Jacob Marble @ 2009-10-04  3:15 UTC (permalink / raw)
  To: BATMAN mailing list

This is my correspondence with David, aka postmaster@vger.  At this
point, I need someone else (Marek, etc.) to contact David if we are to
move forward with VGER.

Jacob

<quote>
> Hello, I'm looking for a new mailing list host for the B.A.T.M.A.N.
> project (http://open-mesh.net/).  Batman is two mesh networking tools,
> one a kernel module and the other a user-space approach.  We would
> like to host at VGER; what is the procedure to create a new list?

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@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.

Sorry.
</quote>

^ permalink raw reply	[flat|nested] 5+ messages in thread
* [B.A.T.M.A.N.] VGER mailing list request
@ 2009-10-04 17:41 Andrew Lunn
       [not found] ` <20091004.171221.67525397.davem@davemloft.net>
  0 siblings, 1 reply; 5+ messages in thread
From: Andrew Lunn @ 2009-10-04 17:41 UTC (permalink / raw)
  To: postmaster; +Cc: b.a.t.m.a.n

> 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@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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2009-10-05  6:34 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-04  3:15 [B.A.T.M.A.N.] VGER mailing list request Jacob Marble
2009-10-04  7:38 ` Andrew Lunn
2009-10-04 17:23 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2009-10-04 17:41 Andrew Lunn
     [not found] ` <20091004.171221.67525397.davem@davemloft.net>
2009-10-05  6:34   ` Andrew Lunn

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox