Hi. My organization is currently developing a Wireshark dissector for a still rapidly evolving IEEE standard. Since quite a few changes to the standard are planned to happen within the coming months, we are not sure if we want to push this into the trunk of the main Wireshark repo. Instead, we want to take the latest stable load and make a fork and host it in GitHub for people across the globe to contribute. Once the standard is approved, we will make sure the dissector fits into the Wireshark coding development practices before pushing the changes to the general Wireshark community. Are there any guidelines to this? Thank you! asked 05 Jun '14, 15:42  frankh-c4mi |
One Answer:
You don't have to fork a whole new Wireshark repository. It's sufficient to create a new GitHub Repo for your dissector code, unless you have to modify the Wireshark code to make your dissector work. If you do it this way you'll have to add some information about how to add your dissector to the Wireshark build process. If you still think you need a fork Or search only: GitHub fork tutorial Regards answered 05 Jun '14, 21:48  Kurt Knochner ♦ edited 05 Jun '14, 21:51 |
Why not just use Gerrit and mark it as [WIP] work-in-progress in that way you can rebase and keep it up to date with Wireshark sources.