28 Jul
2013
28 Jul
'13
8:53 a.m.
On 07/27/2013 09:50 PM, Mitar wrote:
:( :( it would be a great opportunity to meet, hope you can find a way
to make it there!
Hi!
Yes, that's exactly the idea.
Everything we already have, that looks reusable, we are throwing it in;
Everything that can be pushed upstream, to vanilla openwrt, for an even
broader audience, we're pushing it.
So, it'd like a 'mesh-oriented' openwrt repo. We'll maybe build a
generic, unbranded firmware at some point, but the idea from the start
was to "refactor" our current firmwares over that shared base, doing
exactly what you're saying of taking these packages, adding a few, and
making a "distro"
to put a really bad analogy:
openwrt is the base of everything ("debian")
libre-mesh is a superset of openwrt packages ("ubuntu")
qMp would base on libre-mesh, ("mint")
AlterMesh will also use that base ("lubuntu")
eigennet as well ("xubuntu")
and anyone can come in, contribute to libre-mesh reusable packages that
do not quite fit in openwrt upstream (because if not, we'd encourage
pushing them upstream), and instead of having those improvements
scattered around each community repo, we share the most we can.
Each community will take some parts and make another flavour :)
Well, this kind of discussions is what I was
trying to avoid... but it
is my fault for starting it.
No no. It is important to discuss this things. You cannot just believe
that people would just take some firmware without trying to understand
it and reasons for why something is like it is and not some way around?
So don't see this as a flame but more as a way to teach/show.
It is exactly what we are doing. Please see our
repositories you will
find lime-packages which is an OpenWRT feed.
Great!
This maybe means that talking about "firmware" is not the right word.
But more about a set of packages? Because then it is easier to imagine
that another community network takes few of those packages and add few
theirs and maybe even then put them all together in one feed for later
community network to build upon.
Can you maybe just show us few examples of such scripts? Just so that it
is easier to imagine what kind of things one have to think about when
developing a firmware?
We're avoiding vapourware talk, so that's why we haven't made a proper
"presentation" till we have some real juicy code to show;
...but i understand p4u's reaction to reading your wiki; your whole
firmware design is exactly what we are aiming for! so, a friendly invite
right on time to avoid doubling efforts was more important :)
So I am not sure that it is smart to add another layer
(another routing
protocol) of complexity to the networking stack, where we could just
learn and build upon existing tools. As you said, if I paraphrase, not
yet another routing protocol. Cannot we have just one and all contribute
to that one? So if Batman works in most cases, let's fix those cases
where it does not.
We had several long, insightful discussions with the bat-team in Aalborg
last battlemesh, it's a pity you couldn't attend :(
i'm really looking forward to meet you Mitar! maybe we can at least have
a mumble one of these days?
Cheers, Mitar.
Hope to see you in October.
Sadly, I will not have time to attend the summit this time. :-(