From: elektra <onelektra@gmx.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] List policy for none subscribers
Date: Wed, 26 Aug 2009 11:19:21 +0200 [thread overview]
Message-ID: <200908261119.22173.onelektra@gmx.net> (raw)
In-Reply-To: <200908261001.31814.sven.eckelmann@gmx.de>
Hi!
> > As a side issue, i'm not sure batman-adv is the right name for
> > mainline. In the context of the batman project, it makes sense, but
> > from the perspective of mainline, this is the first version of batman,
> > and maybe we cannot justify the advanced.
One problem of the B.A.T.M.A.N. project is the confusion we created by having
too many versions. Renaming batman-advanced to batman would be the worst we
could probably do with this regard.
> To the wiki stuff. The policy was long time correct if I remember it
> correct (send my first stuff without being subscribed). Maybe it was
> accidentally changed when the administrator upgraded the mailing list/mail
> stuff.
In principle a open-posting list would be nice, but I don't see this
implemented anywhere with reason. My guess would be that no one is willing to
go through literally thousands of SPAM mails every day to find the one
legitimate e-mail coming in once a week that is waiting for approval by the
list admins. Whenever I tried posting as a non-subscriber to a mailing list
my email never went through.
> What make me a little curious is what that change would mean for the
> development model. Ok, they would have to work with a git clone and have to
> send merge requests/patches to upstream - but what about internal packet
> versions. The current version is 7 and have it to support older version in
> the (very probably) situation that the packet format is changed again?
This is a good and important question. Even more so because Marek and I were
having a initial discussion via VOIP about ideas and changes to the algorithm
for the next generation mark 5 of the protocol algorithm. Our aim is (again)
reduced computational and data overhead, faster convergence speed, a
simplification of the protocol and added support for IPv6. This step will
again call for a higher packet version number, naturally. I guess the kernel
developers won't be amused to include something in the main line which is
still under heavy development?
We should discuss the changes to mark 5 with all the people which are deeper
involved. It would be awesome to meet you all physically somewhere for
a "B.A.T.M.A.N. developer meeting/conference" to set the agenda and gather
ideas... I could organize a venue if you want to come to Berlin...
> And as my position as random guy I want to thank you for contacting Greg
> G-K
I want to say big THANKS to all people - testers, developers - that are
contributing to the project. Marek, Andrew, Sven, Axel, Yang, Antoine,
Simon... - it is a great joy for me to see your contributions!
Cheers,
Elektra
next prev parent reply other threads:[~2009-08-26 9:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 6:41 [B.A.T.M.A.N.] List policy for none subscribers Andrew Lunn
2009-08-26 7:54 ` Marek Lindner
2009-08-26 8:27 ` Andrew Lunn
2009-08-26 8:01 ` Sven Eckelmann
2009-08-26 8:51 ` Marek Lindner
2009-08-26 10:47 ` [B.A.T.M.A.N.] Breaking long lines Andrew Lunn
2009-08-26 10:52 ` [B.A.T.M.A.N.] New name for batman-adv? Andrew Lunn
2009-08-27 9:58 ` Marek Lindner
2009-08-27 19:44 ` Andrew Lunn
2009-08-28 1:57 ` Outback Dingo
2009-08-28 3:08 ` Andrew de Andrade
2009-08-28 6:42 ` Antoine van Gelder
2009-10-09 18:57 ` Linus Lüssing
2009-08-26 11:01 ` [B.A.T.M.A.N.] Configuration interface Andrew Lunn
2009-08-27 13:57 ` [B.A.T.M.A.N.] List policy for none subscribers Bernd Petrovitsch
2009-08-26 9:19 ` elektra [this message]
2009-08-26 10:41 ` Andrew Lunn
2009-08-26 18:08 ` Andrew Lunn
2009-08-27 10:05 ` Marek Lindner
2009-08-27 11:10 ` elektra
2009-08-27 14:17 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908261119.22173.onelektra@gmx.net \
--to=onelektra@gmx.net \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox