public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] new alfred packet type *3* for solar tracer charging units
Date: Mon, 06 Oct 2014 16:39:15 +0200	[thread overview]
Message-ID: <1461254.rz0spk34lf@prime> (raw)
In-Reply-To: <54327CCB.20406@rund.freifunk.net>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

On Monday 06 October 2014 13:28:11 Ufo wrote:
> Am 27.08.14 15:14, schrieb Ufo:
> > best way for distributing the detailed data (about local sun impact..)
> > was alfred. we used nr. 160 but now simon choosed nr. 3 for that.
> 
> all the different values from solar units are now defined on our test
> systems. and meanwhile EP Solar China gave us some additional hints..
> 
> https://twitter.com/rundfreifunk/status/519083918436630528
> https://gitorious.org/tracertools/tracertools/source/4a6eb477a850e102f37b6f6
> 690b0797ec664f36d:tracerstat.c#L26
> 
> so the next step should be to include these into alfred?
We basically have two options here:

 * integrat the tracetools into the alfred repository, similar to vis and 
gpsd. Please note that the quality should also be similar and you or your 
colleagues should be able to maintain that code
 * keep the package external (e.g. on gitorious), then since we have an 
external software package now we should start using a number assignment table 
in wiki to show which software uses which packet type. We could then link from 
there your software

Any preferences? :)

Cheers,
     Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-10-06 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 13:14 [B.A.T.M.A.N.] new alfred packet type *3* for solar tracer charging units Ufo
2014-10-06 11:28 ` Ufo
2014-10-06 14:39   ` Simon Wunderlich [this message]
2014-10-06 21:04     ` Daniel Golle
2014-10-10 18:54       ` Simon Wunderlich

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=1461254.rz0spk34lf@prime \
    --to=sw@simonwunderlich.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox