All of lore.kernel.org
 help / color / mirror / Atom feed
From: 3zl Trizonelabs <trizonelabs@googlemail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [Interop-dev] collaboration-group on batman-adv installation & application
Date: Sat, 28 Apr 2012 23:57:16 +0300	[thread overview]
Message-ID: <CAJuY50wBFRNaEwf-DvistUYd8N-TZ4+AGK=gNzGcTmjDVRqoJA@mail.gmail.com> (raw)
In-Reply-To: <CAHD-aqJ+Kc--pEJ5kxWsHJfit9HVMPjC6kX42iXSGTa3RzkeBw@mail.gmail.com>

good to have some input !

i do agree on the poit to have relevant informations on the batman
wiki, but i don't feel a wiki is the right tool for interactive
collaboration.
It might be suitable more for nearly finished dokumentation.

Teamwork must have some "noise" which ist filtered out once "cooking"
is done and dinner is ready. ;-)

Meanwhile i have setup a testpage to show the organisation in my
personal approach to manage the "information" mess
once starting with batman-adv for the first time.

Anybody might have a look at http://joker.eu5.org/   which represents
ROUGHLY what i have in mind.
It's done with Mindmanager and exported to html so for me it's very
easy to reoganize the subjects whilst orking on it.

Whatever tool we agree to use, its fine for me; giving a chance
someone has time and have a look at Teamlab or similiar
pse send me a personal msg to hand the access code for playing around.

Let's find a way to organize the communication and start to gather the
scattered informations on one place or the other

regards
3zl


2012/4/28 Guido Iribarren <guidoiribarren@buenosaireslibre.org>:
> On Sat, Apr 28, 2012 at 8:40 AM, Mitar <mitar@tnode.com> wrote:
>> Hi!
>>
>>> To keep things tidy, should we nest everything under
>>> http://interop.wlan-si.net/wiki/WikiSquatters/  ?
>>> ;)
>>
>> No need for that. Maybe just /wiki/Gudes/ or /wiki/Tutorials/?
>>
>> Anyway, I am not sure what is wrong with current Batman wiki?
>>
>> http://www.open-mesh.org/wiki/batman-adv
>
> Well, I first got the feeling that the batman-adv wiki was more
> implementation-agnostic, but now that i come to think about it, that
> wouldn't make much sense :P
>
> Then, let's fill in that gap in batman-adv wiki, and if things start
> dealing with other routing protocols than batman, we can put that
> stuff in interop wiki
>
> This is compatible with 3zl' proposal of using forum packages, since
> AFAIU that's just a bigger framework where a wiki fits in. :)
>
>> On one side I am very for combining our efforts, but we should make sure
>> that content is updated/actual/maintained and this is possible only if
>> communities are behind it. So yes, we could start doing a common wiki
>> for everything, too. :-)
>>
>>
>> Mitar

  reply	other threads:[~2012-04-28 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 16:39 [B.A.T.M.A.N.] collaboration-group on batman-adv installation & application 3zl Trizonelabs
2012-04-19 18:46 ` Christian Huldt
2012-04-28  7:09   ` Guido Iribarren
2012-04-28 10:19     ` 3zl Trizonelabs
2012-04-28 11:40     ` [B.A.T.M.A.N.] [Interop-dev] " Mitar
2012-04-28 12:53       ` 3zl Trizonelabs
2012-04-28 14:59       ` Guido Iribarren
2012-04-28 20:57         ` 3zl Trizonelabs [this message]
2012-05-07 19:05           ` Guido Iribarren

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='CAJuY50wBFRNaEwf-DvistUYd8N-TZ4+AGK=gNzGcTmjDVRqoJA@mail.gmail.com' \
    --to=trizonelabs@googlemail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.