Re: A newbie to contributiobn

[Graham Bloice <graham.bloice () trihedral com>]

Hi,



Welcome to the community,



The dev mailing list is usually the best place for these sort of
discussions, so I’ll cc the dev list so others can see as well.



Personally I’m not sure how we “assign” Bugzilla items, unless someone is
grabbing the item to work on it themselves but adding your email to the CC
list for the bug ensures you’ll know if someone else “touches” the item



The Developers Guide section on contributions (3.9) discusses how to
contribute your code changes.



For a straightforward bugfix, just attaching the patch to the Bugzilla item
and setting “review_for_checkin” to “?” would be sufficient.



For a more complex bugfix, or something such as a change in UI, then it
might be best to start a discussion on the dev mailing list to canvas
opinions.



Hope this helps.



*From:* Shankar Raman [mailto:shankaraman.r () gmail com]
*Sent:* 11 November 2013 11:49
*To:* graham.bloice () trihedral com
*Subject:* Fwd: A newbie to contributiobn



Hello,

     Sir. I am willing to contribute some bug fixes or the enhancements
mentioned in the Bugtracker <https://bugs.wireshark.org/bugzilla/>. I went
through the bug list and I have chosen a Bug with ID : 9285, which is about
changing the fonts of the selected and marked packets rather than having a
color highlighted. I just added my email address in the CC list in the same
place where I found the issue and I don't know whether it is sufficient, to
ensure that the bug is assigned to me or not.

     I went to IRC channel and sought for help, but nobody replied and thus
I came to know about the mailing list. So I thought of asking help from
someone. Can you help me on what to do next?



Thank you very much. Waiting for your response eagerly to move forward.



-- 
Regards,

Shankarraman.



blog: www.shankaraman.wordpress.com

___________________________________________________________________________
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