Difference between revisions of "GSOC2018PatchRequirement"

Revision as of 17:35, 27 February 2018

As part of their Google Summer of Code 2018 applications to ns-3, we require that students produce at least a small amount of code for ns-3. This will allow us to gauge your ability to dive into source code, understand it, make a modification, and proceed to build and verify if your modification works.

A patch in this regard can be at least one of the following:

• If you already have contributed a patch for ns-3 in the past, point us to the relevant commits in our code repository or the bug tracker issue, and your patch requirement is satisfied. If you have code posted somewhere else (GitHub, for example, or a class project page) that you feel is a good indicator of your ability to write ns-3 code, please point us to the URL.
• If not the above, either complete the minimum requirement test given below, or pick a bug in our Bugzilla that does not already have a patch pending, and try to fix it.

Minimum requirement patch

Setting up the environment

Perform the following steps (you may want to review our Installation page):

• Download the ns-3.27 release, or clone it from Mercurial:

 $: hg clone http://code.nsnam.org/ns-3.27

or

 $: wget http://www.nsnam.org/release/ns-allinone-3.27.tar.bz2

• Verify if you can build ns-3 and run the test suite:

 $: ./waf configure --disable-python --enable-examples
 $: ./waf build
 $: ./test.py

Objective

(To be posted shortly).

What to submit

• A patch to ns-3.27 that accomplishes the objectives. In your GSoC application, point us to a publicly available URL where you've hosted the patch (such as a "gist" on github.com for instance). See also some guidelines here about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Tom Henderson) for advice.

Note: Keep your solution private by pasting the link in your application to Google, not posting it on the mailing list.