From: Dave Taht <dave.taht@gmail.com>
To: Nick Feamster <feamster@cc.gatech.edu>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] repo locations + source code license?
Date: Tue, 31 May 2011 10:20:38 -0600 [thread overview]
Message-ID: <BANLkTi=7FqzUTNtf_0Rx-=+DNC+rRvoh3A@mail.gmail.com> (raw)
In-Reply-To: <5FC6E7BF-B18B-4D41-A80A-84030C79115E@cc.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
On Tue, May 31, 2011 at 8:56 AM, Nick Feamster <feamster@cc.gatech.edu>wrote:
> for the FCC writeup, the requirements are that the source code is publicly
> available.
>
Excellent.
>
> "Any new or improved app must be openly licensed (i.e., open source) and
> any non-personally identifiable data collected through the software tool
> must be made available, upon request, to the public for independent
> analysis."
>
Excellent.
>
> 1. What license are we going to use?
>
>
The Linux kernel is GPLv2.
> 2. Should we move to github.com today? I am happy to try to migrate the
> network dashboard code into there. What about: (1) the BISMark firmware
> build; (2) BISMark?
>
The packaging system for the firmware is in general GPLv2 and in general
copyright is held by the openwrt team.
Individual packages have a variety of licences, ranging from "free beer", to
BSD, to various forms of the GPL.
I note that openwrt itself is VERY LARGE (gigabytes), and it would be a
poor, and somewhat costly, idea to fork the existing capetown-wndr3700
repository and put on github.
Rather it would be best to document the (now very few) changes to the
openwrt core, push anything they will accept up to them, and store the
patches that openwrt would not accept as is, in a git repo per such.
> For the firmware and management software, I'm actually not sure if the
> repositories are currently public?
>
>
I'm uncomfortable with lumping all the various bits of openwrt into a single
catagory called 'firmware'.
What do you mean by management software?
> How should we handle this issue?
>
>
Carefully, and thoroughly.
> -Nick
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 3510 bytes --]
prev parent reply other threads:[~2011-05-31 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 14:56 Nick Feamster
2011-05-31 15:07 ` Walter de Donato
2011-05-31 15:13 ` Nick Feamster
2011-05-31 15:29 ` Walter de Donato
2011-05-31 15:31 ` Nick Feamster
2011-05-31 15:35 ` Walter de Donato
2011-05-31 15:37 ` Nick Feamster
2011-05-31 15:39 ` Walter de Donato
2011-05-31 15:40 ` Nick Feamster
2011-05-31 16:01 ` Nick Feamster
2011-05-31 17:01 ` Walter de Donato
2011-05-31 20:56 ` Dave Taht
2011-05-31 22:31 ` Nick Feamster
2011-05-31 16:20 ` Dave Taht [this message]
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='BANLkTi=7FqzUTNtf_0Rx-=+DNC+rRvoh3A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=feamster@cc.gatech.edu \
/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