From: Nick Feamster <feamster@cc.gatech.edu>
To: Walter de Donato <walter.dedonato@unina.it>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] repo locations + source code license?
Date: Tue, 31 May 2011 17:37:08 +0200 [thread overview]
Message-ID: <614A5E13-6E88-4F01-9182-4D45147678C0@cc.gatech.edu> (raw)
In-Reply-To: <BANLkTimM-W9K-1G7semjUjc+3+dyMW1W1g@mail.gmail.com>
Do you have access to the "bismark-devel" user on github?
On May 31, 2011, at 5:35 PM, Walter de Donato wrote:
> Sold! :-)
>
>
> 2011/5/31 Nick Feamster <feamster@cc.gatech.edu>
> Yes. "bismark-firmware" (singular) seems good.
>
> On May 31, 2011, at 5:29 PM, Walter de Donato wrote:
>
> > Why don't bismark-firmwares?
> >
> > Walter
> >
> > 2011/5/31 Nick Feamster <feamster@cc.gatech.edu>
> > Yes, I think perhaps bismark builds could be kept in a separate repo.
> >
> > Not sure what we could call that one. bismark-router?
> >
> > -Nick
> >
> > On May 31, 2011, at 5:07 PM, Walter de Donato wrote:
> >
> > > I usually feel comfortable using GPL licenses.
> > > I don't know if in this case choosing the Affero GPL would be more appropriate.
> > > What do you think?
> > >
> > > I can try to migrate Bismark to github if Dave didn't start yet doing it.
> > > Probably Bismark builds should be kept apart from it. Ideas?
> > >
> > > Walter
> > >
> > > 2011/5/31 Nick Feamster <feamster@cc.gatech.edu>
> > > for the FCC writeup, the requirements are that the source code is publicly available.
> > >
> > > "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."
> > >
> > > 1. What license are we going to use?
> > >
> > > 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?
> > >
> > > For the firmware and management software, I'm actually not sure if the repositories are currently public?
> > >
> > > How should we handle this issue?
> > >
> > > -Nick
> > > _______________________________________________
> > > Bismark-devel mailing list
> > > Bismark-devel@lists.bufferbloat.net
> > > https://lists.bufferbloat.net/listinfo/bismark-devel
> > >
> > >
> > >
> > >
> > > --
> > > Walter de Donato, PhD Student
> > > Dipartimento di Informatica e Sistemistica
> > > Università degli Studi di Napoli "Federico II"
> > > Via Claudio 21 -- 80125 Napoli (Italy)
> > > Phone: +39 081 76 83821 - Fax: +39 081 76 83816
> > > Email: walter.dedonato@unina.it
> > > WWW: http://wpage.unina.it/walter.dedonato
> > >
> >
> >
> >
>
>
>
>
next prev parent reply other threads:[~2011-05-31 15:20 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 [this message]
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
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=614A5E13-6E88-4F01-9182-4D45147678C0@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=walter.dedonato@unina.it \
/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