Re: [B.A.T.M.A.N.] Opportunity to contribute in B.A.T.M.A.N

[Simon Wunderlich <sw@simonwunderlich.de>]

[-- Attachment #1: Type: Text/Plain, Size: 3067 bytes --]

Hello Dhruvesh,

> Hello,
> 
> 	We are a group of students that are currently pursuing our undergraduate
> degrees in Computer Science form Pune Institute of Computer Technology
> (PICT), Maharashtra, India. We will be graduating in June 2015 and are
> currently in our final year. For our final year B.E project we have
> selected the domain as Computer Networks and would be very interested in
> working in the field of routing protocols for multihop ad-hoc mesh
> networks, which is where we stumbled upon the B.A.T.M.A.N protocol. Over
> the past few weeks we have been extensively studying the various features
> and working principles which has allowed this protocol to prosper. It will
> be a great learning opportunity for us to work with B.A.T.M.A.N and in
> turn work with you. As per given on the open-mesh.org website for
> contributions, we would appreciate if you could steer us towards the
> direction of choosing the right topic and working towards culminating a
> project in the same, which would be helpful for the community. Following
> are a few details which includes information about us, which would help
> you in making an informed decision:

Thank you very much for your interesting proposal. We have discussed a little 
bit about topics you might find interesting and which are currently vacant:

 * Distributed ARP table support for IPv6 - this has been started but they guy 
who has been working on it doesn't have the time anymore. You could pick up 
the patches [1]
 * Interconnecting batman-adv clouds. We have a rough draft proposal [2] 
already, but nothing more
 * Evaluation and review of BATMAN V - we currently work on the next 
generation of BATMAN routing, and testing/reviewing that would certainly help.

I'm not sure how much experience you have in kernel development. Depending on 
the task you choose, it would be a good thing to start reading about how the 
kernel and kernel modules work. In any case, for submitting code you must 
comply to the Linux kernel coding style[3], and should run your patches 
through checkpatch, but you probably have already read that in our 
contribute[4] page. And please don't hesitate to send patches early, you can 
always send unfinished stuff as RFC patches. As you can see on the mailing 
list, we usually have a few review cycles for patches, and even though you 
have a few months planned development, time runs out easily and it would be 
sad to see half-finished stuff stopped being worked on. :) You should plan to 
release the first feature-complete patchset at half-time at latest to have 
enough time for review/corrections.

If you have ideas on your own what you want to work on, please don't hesitate 
to propose them!

Cheers,
     Simon

[1] http://thread.gmane.org/gmane.org.freifunk.batman/10014/focus=10574
[2] http://www.open-mesh.org/projects/open-mesh/wiki/Connecting-Batman-adv-
clouds
[3] https://www.kernel.org/doc/Documentation/CodingStyle
[4] http://www.open-mesh.org/projects/open-mesh/wiki/Contribute

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]