Wireshark mailing list archives

Re: Starting point for a developer


From: Guy Harris <guy () alum mit edu>
Date: Sat, 26 May 2012 23:18:23 -0700


On May 26, 2012, at 9:59 PM, Dipanjan Das wrote:

I am yet keen to know who are the core Wireshark developers

As Evan Huus said in his response the previous time you asked these questions:

        http://www.wireshark.org/lists/wireshark-dev/201205/msg00195.html

http://wiki.wireshark.org/Developers is the page that lists the core developers.

& if there is any way to find out the commits made by any one of the community developers.

If you want to see *all* the commits, subscribe to the wireshark-commits list, and look at the archives of the list:

        http://www.wireshark.org/lists/

but it's a list that gets a message *every time a developer checks something in*, so it's a bit of a high-volume list 
and you might not want to subscribe to it, and there have been a lot of commits in the past, so you might not want to 
browse through the archives.

If you want to know what commits are made by a particular developer, then you can try to search for them on Ohloh:

        https://www.ohloh.net/

and, if they have an entry, it might have a link for Wireshark commits - for example, the entry for Gerald Combs has 
such a link:

        https://www.ohloh.net/p/wireshark/contributors/16342350561851

However, as they say, "Due to perf issues, we only show the last 300 days of commit activity", so you won't be able to 
find every commit they've ever made.

And, frankly, for any developer who's made a significant number of commits, you will very quickly become extremely 
bored if you look at a list of their commits,
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: