From: demos <demos@posteo.de>
To: openwrt-hackers@openwrt.org, linux-wireless@vger.kernel.org
Subject: Connecting
Date: Tue, 14 Apr 2015 23:03:11 +0200 [thread overview]
Message-ID: <552D808F.1080900@posteo.de> (raw)
In-Reply-To: <552D79AE.3070509@gnunet.org>
[-- Attachment #1.1: Type: text/plain, Size: 1563 bytes --]
Connecting GNUnet with Openwrt
Is this the right place to forward this email?
Kind regards
Demos
-------- Weitergeleitete Nachricht --------
Betreff: Re: [GNUnet-developers] EDN
Datum: Tue, 14 Apr 2015 22:33:50 +0200
Von: Christian Grothoff <grothoff@gnunet.org>
An: demos <demos@posteo.de>, gnunet-developers@gnu.org
On 04/14/15 21:55, demos wrote:
> Concerning the support of openwrt:
> What do you think about the idea of crosschecking certain parts of code
> for bugs (those parts that directly interact with one another?) together
> with the Openwrt-developers. (I haven't asked them yet. Maybe it's
> better if you ask them directly?)
Well, our code largely just calls the TUN/TAP APIs of the Kernel right
now, so I don't know where we'd there touch with OpenWRT-logic.
> In my opinion this would be a win-win situation for both,
> because you both have experienced C developers.
> They get their code reviewed, you get your code reviewed.
I'm not sure this is terribly realistic: it takes quite some time to be
familiar with the codebase (and you can't review code without
understanding what it is supposed to do). That knowledge doesn't
translate to a different project easily, you have the initial steep
learning curve each time. So it doesn't quite sound like a win-win.
However, if the OpenWRT folks are interested in helping Bart (& Florian)
get GNUnet onto the WRT platform, that would be great and might be an
actual win-win (we gain a platform, they a capability).
Happy hacking!
Christian
[-- Attachment #1.2: 0xBF83D308.asc --]
[-- Type: application/pgp-keys, Size: 4814 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2015-04-14 21:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <552D79AE.3070509@gnunet.org>]
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=552D808F.1080900@posteo.de \
--to=demos@posteo.de \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-hackers@openwrt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).