 | 1 | initial version |
Before you even think about contributing. See if you can take the source code and compile it for your own use. Then see if you actually understand some of the code that you compiled. And then do the same thing on the latest code that is published on git.
In my view. If you have to ask how to contribute? Then you are not a likely candidate. Most contributed because they saw a challenge/problem and they tried to solve it and wrote a bit of code to add to their own wireshark install. Then once they were comfortable with it they contribted their work.
And this applies to pretty much every open source project. You start by using what is there and then once you are compfortable you start to tweak things a bit and start to participate by listening on developer channels.
Doing relentless testing of features is another way of contributing.
Back in the days when 64 bit machines were rare I ran Sparc and Alpha systems and just recompiled source packages for them and recorded all the warnings and errors about incorrect integer usage and shared them with the authors. I was not comfortable enough to fix them but understood enough to see where they occured.
So there are many way to contribute. But somehow it must match your skills and resources.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
