MaintainersApr2026

Tomh — Fri, 01 May 2026 16:26:58 GMT

add minutes for April 24 meeting

← Older revision		Revision as of 16:26, 1 May 2026
Line 52:		Line 52:

	2) Inclusion of DTN models in the mainline		2) Inclusion of DTN models in the mainline

			== Minutes for April 24 ==

			Attendees: Anders Martinsson, Tom Henderson, Eduardo Almeida, Alberto Gallegos Ramonet

			Minutes from Tom Henderson, edited by Alberto and Eduardo

			Agenda:
			1. Use of CMake Presets
			2. Inclusion of DTN models in the mainline
			3. How to promote smaller MRs for easier reviews

			Anders introduced himself as the submitter of a recent patch series to update DCE environment. He said that other developers were involved at his company and they were using it to test a secure reliable transport protocol. Tom said that he was planning to get to DCE patches once mp-units work died down.

			Alberto and Eduardo discussed the history of the CMake Presets to Tom who does not use VScode and wasn't fully aware of the issues. Eduardo mentioned that we currently use .ns3rc for this kind of configuration control but it would be nicer to use CMake Presets since it is the standardized way.
			An initial attempt to use CMake Presets was introduced last month in !2763 by the CTTC team as a way to use configurations that allow the use of Sionna spectrum models. However, as described in !2822, the introduction of CMake Presets forced users using the VsCode IDE to chose one preset (VsCode default behavior when using CMake Presets) without the possibility of choosing different build variants or compilers outside the established presets. Gabriel reverted the situation by renaming the CMake Presents configuration file to use a different extension but more work is needed on a better solution if the use of presets are to be introduced.

			We discussed DTN and the pros and cons of adding this to the mainline or to the app store. Alberto is in favor of adding new models to the main line assuming that they are for the common benefit ( e.g., based on specifications, standards, current RFCs, etc) and have a maintainer. In the same line of thought, he thinks that models in the main line that do not have a maintainer or have unresponsive maintainers should be moved to the app store. Accepting new contributions has the possible side benefit of attracting more long term maintainers. If the maintainers of those models become uninterested in maintaining or unresponsive, it is possible to move them to the app store.

			Eduardo pointed out that the app-store have evolved and serve multiple purposes, among them: A place where worthy unmaintained projects are stored and where private groups keep visibility of projects actively maintained outside of the main line.

			However, the general sentiment is that when possible, we ought keep ns-3 mainline lean, and it is not clear where DTN lands as a result of these tensions.

			Tom mentioned that a second benefit of having MRs submitted to the mainline is that they obtain code reviews; the ns-3-contributed-modules review site has never taken off and is ignored by maintainers. Still, it seems that the attendees were possibly in favor of reducing the modules in ns-3-dev, adding more to the app store, and making it easier for users to discover and clone modules of interest (kind of like 'bake' is doing for DCE, but possibly through extending the ns3 script or CMake).

			Tom mentioned his difficulty with reviewing large MRs. Eduardo said he wasn't in favor of a hard CI requirement on MR size and Tom said he wasn't serious about this and agreed that softer reminders (please regenerate your MR in smaller chunks) would be better. Tom said that he also wants to see the overall plan of where things are going, rather than having the new module revealed to him piece-by-piece with small MRs, so having a fully built-out branch that is publicly available for review to accompany the MRs is also needed. Eduardo volunteered to review our contributing documentation to see if there is an opportunity to emphasize "one MR per topic and make as small as possible."

	== Recent maintainers meetings ==		== Recent maintainers meetings ==

Summer Projects

Tomh — Fri, 01 May 2026 15:16:52 GMT

Google Summer of Code 2026

← Older revision		Revision as of 15:16, 1 May 2026
Line 7:		Line 7:
	The organizational admins are Tommaso Pecorella, and Mohit P. Tahiliani.		The organizational admins are Tommaso Pecorella, and Mohit P. Tahiliani.

			We are happy to announce that the following five projects have been accepted:

			* '''Nipuna Dulara''', [https://summerofcode.withgoogle.com/programs/2026/projects/nQxxo1N3 Energy Consumption Modeling and Power Aware Extensions for 5G LENA]
			* '''Anuka Hettiarachchi''', [https://summerofcode.withgoogle.com/programs/2026/projects/G2dYeVu6 Integrating 5G NR module with ns-3-ai]
			* '''Kedar Kisan''', [https://summerofcode.withgoogle.com/programs/2026/projects/PCXPdFoD Flent Application API Integration and Validation in ns-3]
			* '''Usham Roy''', [https://summerofcode.withgoogle.com/programs/2026/projects/wHBM2psz 6LoWPAN Mesh Under Routing Enhancements with Trickle Suppression in ns3]
			* '''Manmita Das''', [https://summerofcode.withgoogle.com/programs/2026/projects/Wl61Gzov Switched Ethernet]

			Background material:
	* [[GSOC2026Projects \| Project Ideas Page]]		* [[GSOC2026Projects \| Project Ideas Page]]
	* [[GSOC2026ContributorGuide \| ns-3's GSoC Contributor Guide]]		* [[GSOC2026ContributorGuide \| ns-3's GSoC Contributor Guide]]

Nsnam - Recent changes [en]

MaintainersApr2026

Summer Projects