Hi Tyson, Thanks for your detailed reply.
But, still I am having a doubt. If, being a developer, someone makes an unintentional mistake & commits the same to SVN, then it will get released in the next Wireshark build. Isn't it? Is there any quality control process / monitoring system for that? Also, does ViewVc interface make it possible to find all the commits made by a developer? If not, then is it possible some other way? On 26 May 2012 01:53, Tyson Key <[email protected]> wrote: > Hi Dipanjan, > > There isn't really a formal registration process, but registering at > http://bugs.wireshark.org/ is a good place to start. As for "tasks" - > there isn't a formal list of mandatory activities (but there is a wishlist > on the wiki, which might be vaguely interesting); and things are fairly > ad-hoc - you just think "I'd like to implement feature X", do it, and post > a diff on the bug tracker. > > If you think that you're going to do something that conflicts with what > others are doing, then it's a good idea to ask on this list, first. > > I hope that helps - and welcome aboard! > > Tyson. > > 2012/5/25 Dipanjan Das <[email protected]> > >> >> Hi Developers, >> >> I want to get myself involved in the development of Wireshark. Can >> anybody please let me know about the following: >> >> 1. Is there anywhere I need to get myself registered as a developer? >> 2. How are the tasks splitted across? >> 3. How is the synchronization among developers done? >> >> TIA. >> >> -- >> >> Thanks & Regards, >> Dipanjan >> >> >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <[email protected]> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:[email protected] >> ?subject=unsubscribe >> > > > > -- > Fight Internet Censorship! > http://www.eff.org > http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | > 00447934365844 >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
