GSOC2013PatchRequirement - Revision history

Buherman: Undo revision 7613 by Buherman (talk)

2013-06-01T23:08:30Z

Undo revision 7613 by Buherman (talk)

← Older revision		Revision as of 23:08, 1 June 2013
Line 48:		Line 48:

	* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance). See also some guidelines [http://www.nsnam.org/developers/contributing-code/submit/ here] about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Lalith Suresh) for advice.		* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance). See also some guidelines [http://www.nsnam.org/developers/contributing-code/submit/ here] about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Lalith Suresh) for advice.

	~~[[Category:GSoC]]~~

Buherman at 23:07, 1 June 2013

2013-06-01T23:07:38Z

← Older revision		Revision as of 23:07, 1 June 2013
Line 48:		Line 48:

	* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance). See also some guidelines [http://www.nsnam.org/developers/contributing-code/submit/ here] about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Lalith Suresh) for advice.		* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance). See also some guidelines [http://www.nsnam.org/developers/contributing-code/submit/ here] about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Lalith Suresh) for advice.

			[[Category:GSoC]]

Lalith: /* Setting up the environment */

2013-03-28T15:29:03Z

Setting up the environment

← Older revision		Revision as of 15:29, 28 March 2013
Line 26:		Line 26:
	$: cd ns-3-dev		$: cd ns-3-dev
	$: git clone https://gist.github.com/5186251.git gsoc-patch/		$: git clone https://gist.github.com/5186251.git gsoc-patch/
	$: patch -p1 < gsoc-patch/n3-gsoc-patch-test		$: patch -p1 < gsoc-patch/ns3-gsoc-patch-test

	* Verify if you can build ns-3 and run the test script		* Verify if you can build ns-3 and run the test script

Tomh: /* What to submit */

2013-03-24T14:32:10Z

What to submit

← Older revision		Revision as of 14:32, 24 March 2013
Line 47:		Line 47:
	=== What to submit ===		=== What to submit ===

	* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance).		* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance). See also some guidelines [http://www.nsnam.org/developers/contributing-code/submit/ here] about formatting patches for review. If you need help with this step, contact the ns-3 Org Admin (Lalith Suresh) for advice.

Lalith at 12:48, 18 March 2013

2013-03-18T12:48:12Z

← Older revision		Revision as of 12:48, 18 March 2013
Line 1:		Line 1:
	As part of their Google Summer of Code 2013 applications to ns-3, we require that students produce a patch for ns-3. This will allow us to ~~guage~~ your ability to dive into source code, understand it, make a modification, and proceed to build and verify if ~~their~~ modification works.		As part of their Google Summer of Code 2013 applications to ns-3, we require that students produce a patch 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:		A patch in this regard can be at least one of the following:
Line 6:		Line 6:
	* If you already have contributed a patch for ns-3, point us to the relevant commits in our code repository.		* If you already have contributed a patch for ns-3, point us to the relevant commits in our code repository.
	* If not the above, complete the minimum requirement test given below.		* If not the above, complete the minimum requirement test given below.


	Note, a patch here does not have to be merged for you to qualify. It only serves to show us how comfortable you are with diving into and hacking on a large code base. The more prowess you demonstrate through the patch, the higher your chances of being accepted.		Note, a patch here does not have to be merged for you to qualify. It only serves to show us how comfortable you are with diving into and hacking on a large code base. The more prowess you demonstrate through the patch, the higher your chances of being accepted.

Lalith at 12:47, 18 March 2013

2013-03-18T12:47:13Z

← Older revision		Revision as of 12:47, 18 March 2013
Line 49:		Line 49:
	=== What to submit ===		=== What to submit ===

	* A patch ~~to ns-3-dev~~ that achieves the ~~above~~ objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance).		* A patch atop the above provided files that achieves the said objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance).

Lalith at 12:46, 18 March 2013

2013-03-18T12:46:37Z

← Older revision		Revision as of 12:46, 18 March 2013
Line 45:		Line 45:

	* '''Have TestApplication print "Hello World!" when started and "Goodbye World!" when stopped'''. For this, you will need to implement two private methods provided by the "Application" base class (see the header file testapp.h). Also try looking at the code of other applications inside src/application/model/ for hints on what to do.		* '''Have TestApplication print "Hello World!" when started and "Goodbye World!" when stopped'''. For this, you will need to implement two private methods provided by the "Application" base class (see the header file testapp.h). Also try looking at the code of other applications inside src/application/model/ for hints on what to do.
	* '''Within the testapp-sim.cc simulation script, add "TestApplication" to the single node that is initiated, and have it started and stopped at the first and second second of the simulation respectively'''. As a hint, look for public methods available within the "Node" class. You can also look at other example scripts within the examples/ or src/*/examples/ folders for ideas.		* '''Within the testapp-sim.cc simulation script, add "TestApplication" to the single node that is initiated, and have it started and stopped at the first and second second of the simulation respectively'''. As a hint, look for public methods available within the "Node" and "Application" class. You can also look at other example scripts within the examples/ or src/*/examples/ folders for ideas.

			=== What to submit ===

			* A patch to ns-3-dev that achieves the above objective. In your application, point us to a publicly available URL where you've hosted the patch (like a "gist" on github.com for instance).

Lalith: /* Setting up the environment */

2013-03-18T11:16:32Z

Setting up the environment

← Older revision		Revision as of 11:16, 18 March 2013
Line 27:		Line 27:

	$: cd ns-3-dev		$: cd ns-3-dev
	$: git clone https://gist.github.com~~/lalithsuresh~~/5186251 gsoc-patch/		$: git clone https://gist.github.com/5186251.git gsoc-patch/
	$: patch -p1 < gsoc-patch/n3-gsoc-patch-test		$: patch -p1 < gsoc-patch/n3-gsoc-patch-test

Line 35:		Line 35:
	$: ./waf build		$: ./waf build
	$: ./waf --run testapp-sim		$: ./waf --run testapp-sim


	=== Objective ===		=== Objective ===

Lalith: /* Minimum requirement patch */

2013-03-18T10:28:29Z

Minimum requirement patch

← Older revision		Revision as of 10:28, 18 March 2013
Line 16:		Line 16:


	~~TBA~~		=== Setting up the environment ===

			Perform the following steps:

			* Clone ns-3-dev:

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

			* Apply the ns-3 GSOC patch for the test

			$: cd ns-3-dev
			$: git clone https://gist.github.com/lalithsuresh/5186251 gsoc-patch/
			$: patch -p1 < gsoc-patch/n3-gsoc-patch-test

			* Verify if you can build ns-3 and run the test script

			$: ./waf configure --disable-python --enable-examples
			$: ./waf build
			$: ./waf --run testapp-sim


			=== Objective ===

			The patch you applied above adds the following:
			* An ns-3 application with the classname TestApplication. The corresponding files are src/applications/model/testapp.{cc ,.h}.
			* A simulation script scratch/testapp-sim.cc

			Your objective is to fill up the missing sections in the TestApplication class and testapp-sim.cc in order to be able to:

			* '''Have TestApplication print "Hello World!" when started and "Goodbye World!" when stopped'''. For this, you will need to implement two private methods provided by the "Application" base class (see the header file testapp.h). Also try looking at the code of other applications inside src/application/model/ for hints on what to do.
			* '''Within the testapp-sim.cc simulation script, add "TestApplication" to the single node that is initiated, and have it started and stopped at the first and second second of the simulation respectively'''. As a hint, look for public methods available within the "Node" class. You can also look at other example scripts within the examples/ or src/*/examples/ folders for ideas.

Lalith at 15:28, 1 March 2013

2013-03-01T15:28:26Z

← Older revision		Revision as of 15:28, 1 March 2013
Line 1:		Line 1:
	As part of their Google Summer of Code 2013 applications to ns-3, we require that students produce a patch for ns-3. This will allow us to guage ~~their~~ ability to dive into source code, understand it, make a modification, and proceed to build and verify if their modification works.		As part of their Google Summer of Code 2013 applications to ns-3, we require that students produce a patch for ns-3. This will allow us to guage your ability to dive into source code, understand it, make a modification, and proceed to build and verify if their modification works.

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