# [Outreachy] Introduction 3 messages from 2020-10-16 to 2020-10-17. Participants: Joey S, Jonathan Nieder. Thread: https://gitlist.dev/t/54444 ## Joey S, 2020-10-16 22:09 Subject: [Outreachy] Introduction Message-ID: URL: https://gitlist.dev/e/HiG3ctHji8hdGWXWEwWgeoa6eDDHkUbhfa0x0xYr9EHWD7FqXqZsQt3fHMZ4Vle0jo2QPCW8rjRviw_aGKqxUIFtvX2igp1aUnx9p6YCL0Y%3D%40protonmail.com ``` [Message previously sent as rich text to both git@vger.kernel.org and wireshark-dev@wireshark.org, re-sending to the git ml as plain text from a different account, apologies for the inconvenience] Hi everyone, I'm Joey Salazar, an Outreachy 2020 applicant certified in CCNA and Linux+, with some experience in C for both private and open source repositories (BIND at gitlab.isc.org/Joey), community code reviews, and automated tests in bash. I'd like to contribute to the "Add Git protocol support to Wireshark" project and improve my skills, yet remain open to a different project if that'd be preferable. I have installed and built git, followed git.github.io/General-Microproject-Information and checked the sample email thread [1], as well as the tutorial git-scm.com/docs/MyFirstContribution and created the psuh command files here [2]. After following the git.github.io/Outreachy-21-Microprojects page I'd like to work on the 'Use test_path_is_* functions in test scripts', and given that Charvi Mendiratta might be working on tests t7101,t7102 and t7201 as per this ml thread [3], I'd like to check with the group if working on tests t7006 and t7300 would be ok. In parallel, I'm following gitlab.com/wireshark/wireshark/-/wikis/Development as suggested through the #git-devel IRC channel and will follow that up with the overview of Git's HTTP protocol in the Pro Git book [4]. All guidance much appreciated, I'm very looking forward to working together! Joey [1] public-inbox.org/git/1386590745-4412-1-git-send-email-t.gummerer@gmail.com/T/#u [2] github.com/j-sal/git/tree/psuh [3] public-inbox.org/git/CAP8UFD1m2zXUm1PXmJKW2MxA9XZVUOkBFA62jLP7jx6_DCYZGw@mail.gmail.com [4] git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols ``` ## Jonathan Nieder, 2020-10-16 23:08 Subject: Re: [Outreachy] Introduction Message-ID: <20201016230801.GA945741@google.com> URL: https://gitlist.dev/e/20201016230801.GA945741%40google.com In-Reply-To: ``` Hi Joey, Joey S wrote: > Hi everyone, > > I'm Joey Salazar, an Outreachy 2020 applicant certified in CCNA and > Linux+, with some experience in C for both private and open source > repositories (BIND at gitlab.isc.org/Joey), community code reviews, > and automated tests in bash. I'd like to contribute to the "Add Git > protocol support to Wireshark" project and improve my skills, yet > remain open to a different project if that'd be preferable. Welcome! > I have installed and built git, followed > git.github.io/General-Microproject-Information and checked the > sample email thread [1], as well as the tutorial > git-scm.com/docs/MyFirstContribution and created the psuh command > files here [2]. > > After following the git.github.io/Outreachy-21-Microprojects page > I'd like to work on the 'Use test_path_is_* functions in test > scripts', and given that Charvi Mendiratta might be working on tests > t7101,t7102 and t7201 as per this ml thread [3], I'd like to check > with the group if working on tests t7006 and t7300 would be ok. I'd recommend just doing a single file. t7006 is a good one. > In parallel, I'm following > gitlab.com/wireshark/wireshark/-/wikis/Development as suggested > through the #git-devel IRC channel Yes, building wireshark and making your first modification to it would be a good next step. One possible first modification would be to teach epan/dissectors/packet-git.c about sideband. See "Packfile Data" in git's Documentation/technical/pack-protocol.txt for how sideband works. Alternatively you can run wireshark and see if anything you see bothers you and make a first contribution that improves on that. :) Happy developing. Thanks, Jonathan > [1] public-inbox.org/git/1386590745-4412-1-git-send-email-t.gummerer@gmail.com/T/#u > [2] github.com/j-sal/git/tree/psuh > [3] public-inbox.org/git/CAP8UFD1m2zXUm1PXmJKW2MxA9XZVUOkBFA62jLP7jx6_DCYZGw@mail.gmail.com > [4] git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols [5] https://www.wireshark.org/lists/wireshark-dev/202010/msg00042.html ``` ## Joey S, 2020-10-17 00:42 Subject: Re: [Outreachy] Introduction Message-ID: <10jLX0WcuXO5QAeFmLoSxxyDAwb9zvqiYPM8ZId5Rab4os7_yXTksG5Fc7Z_pM97vudO0W4AtE4PuunS4TeS6z45heDTJpzAfEuLoLycgwM=@protonmail.com> URL: https://gitlist.dev/e/10jLX0WcuXO5QAeFmLoSxxyDAwb9zvqiYPM8ZId5Rab4os7_yXTksG5Fc7Z_pM97vudO0W4AtE4PuunS4TeS6z45heDTJpzAfEuLoLycgwM%3D%40protonmail.com In-Reply-To: <20201016230801.GA945741@google.com> ``` Thank you Jonathan, will happily get to it. Hoping you all have a nice weekend, Joey ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, October 16, 2020 5:08 PM, Jonathan Nieder wrote: > Hi Joey, > > Joey S wrote: > > > Hi everyone, > > I'm Joey Salazar, an Outreachy 2020 applicant certified in CCNA and > > Linux+, with some experience in C for both private and open source > > repositories (BIND at gitlab.isc.org/Joey), community code reviews, > > and automated tests in bash. I'd like to contribute to the "Add Git > > protocol support to Wireshark" project and improve my skills, yet > > remain open to a different project if that'd be preferable. > > Welcome! > > > I have installed and built git, followed > > git.github.io/General-Microproject-Information and checked the > > sample email thread [1], as well as the tutorial > > git-scm.com/docs/MyFirstContribution and created the psuh command > > files here [2]. > > After following the git.github.io/Outreachy-21-Microprojects page > > I'd like to work on the 'Use test_path_is_* functions in test > > scripts', and given that Charvi Mendiratta might be working on tests > > t7101,t7102 and t7201 as per this ml thread [3], I'd like to check > > with the group if working on tests t7006 and t7300 would be ok. > > I'd recommend just doing a single file. t7006 is a good one. > > > In parallel, I'm following > > gitlab.com/wireshark/wireshark/-/wikis/Development as suggested > > through the #git-devel IRC channel > > Yes, building wireshark and making your first modification to it would > be a good next step. > > One possible first modification would be to teach > epan/dissectors/packet-git.c about sideband. See "Packfile Data" in > git's Documentation/technical/pack-protocol.txt for how sideband > works. > > Alternatively you can run wireshark and see if anything you see > bothers you and make a first contribution that improves on that. :) > > Happy developing. > > Thanks, > Jonathan > > > [1] public-inbox.org/git/1386590745-4412-1-git-send-email-t.gummerer@gmail.com/T/#u > > [2] github.com/j-sal/git/tree/psuh > > [3] public-inbox.org/git/CAP8UFD1m2zXUm1PXmJKW2MxA9XZVUOkBFA62jLP7jx6_DCYZGw@mail.gmail.com > > [4] git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols > > [5] https://www.wireshark.org/lists/wireshark-dev/202010/msg00042.html ```