Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	codel@lists.bufferbloat.net, aqm@ietf.org
Subject: Fwd: [Ns-developers] NS-3 has been accepted for GSOC 2013
Date: Tue, 9 Apr 2013 01:17:39 -0700	[thread overview]
Message-ID: <CAA93jw7P1tR=ustWfEhp7OMgDUZU4O49=DCZJUmPydyzifsJvQ@mail.gmail.com> (raw)
In-Reply-To: <CAOj7qWbJKzbootw2G0L9Br=hMXCF1a5E9DPbsDboy5gC=Jupug@mail.gmail.com>

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

Andrew and I haven't had time to update the ns3 model to the current
versions of codel, fq_codel, and sfq_codel. I don't really expect that time
to materialize.

However I am certainly willing to mentor someone (other mentors would be
good, too!) on moving the codebase forward (and developing further
tests/papers) and pushing it into the mainline code, this summer, as part
of the GSOC program.

https://www.nsnam.org/wiki/index.php/GSOC2013Projects#INSTOOLS_for_ns-3

Any takers? See further below for more details.

The old (may, 2012) ns3 codebase is in git

https://github.com/dtaht/ns-3-dev

and the latest ns2 codebase which has sfq_codel in it is hosted on pollere

http://pollere.net/CoDel.html

Despite the name the sfq_codel codebase has morphed to be very similar to
the fq_codel codebase, but they do remain different in several approaches.

---------- Forwarded message ----------
From: Lalith Suresh <suresh.lalith@gmail.com>
Date: Mon, Apr 8, 2013 at 12:01 PM
Subject: [Ns-developers] NS-3 has been accepted for GSOC 2013
To: ns-developers <ns-developers@isi.edu>


Hi everyone,

I'm very pleased to inform you that ns-3 has been accepted for Google
Summer of Code 2013. Thanks to everyone who helped prepare our ideas
page [1]!

Students are encouraged to go through our Ideas list and begin
discussing their plans on the ns-developers mailing list to get
feedback from the developers. Also, start preparing your applications
as per our template [2]. The earlier you begin, the more refined your
application will be, so start now! You will soon be able to find ns-3
on Melange [3] after which you can begin filling in your application
there.

Please note: there is a simple test this year for all student
applicants. Please refer to [4] for details.


[1] https://www.nsnam.org/wiki/index.php/GSOC2013Projects
[2] https://www.nsnam.org/wiki/index.php/GSOC2013StudentApplicationTemplate
[3]  http://www.google-melange.com/gsoc/homepage/google/gsoc2013
[4] https://www.nsnam.org/wiki/index.php/GSOC2013PatchRequirement


--
Lalith Suresh
www.lalith.in



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 3293 bytes --]

       reply	other threads:[~2013-04-09  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOj7qWbJKzbootw2G0L9Br=hMXCF1a5E9DPbsDboy5gC=Jupug@mail.gmail.com>
2013-04-09  8:17 ` Dave Taht [this message]
2013-04-16  9:01   ` Igor Maravić

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='CAA93jw7P1tR=ustWfEhp7OMgDUZU4O49=DCZJUmPydyzifsJvQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    /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