From: Jonathan Nieder <jrnieder@gmail.com>
To: Amanda Shafack <shafack.likhene@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Introduction - An Outreachy 2020 Applicant
Date: Thu, 8 Oct 2020 17:25:41 -0700 [thread overview]
Message-ID: <20201009002541.GB2415320@google.com> (raw)
In-Reply-To: <CAGxm6oXSaKoTR3btKRV4bMYUsc3-oKeWSfzrWKkCXgrRorAEAQ@mail.gmail.com>
+wireshark-dev@wireshark.org
Hi Amanda,
Amanda Shafack wrote:
> I am Amanda Shafack, an Outreachy 2020 applicant who wishes to
> contribute to the "Add Git protocol support to Wireshark" project.
>
> In addition, I have some experience coding in C and I hope to enhance
> my skill set by contributing to this project.
>
> I am currently going through the project description and contribution
> guidelines.
Welcome!
Since this project would involve Git (for Git protocol) and Wireshark
(where the dissector goes), we're comfortable working with you on
contributions to both Git and Wireshark during the application[1]
period.
https://gitlab.com/wireshark/wireshark/-/wikis/Development/ has some
pointers on getting started with Wireshark development. I'm cc-ing
the wireshark developers list in case they have suggestions for an
approachable "first patch" idea to get used to that project's
contribution flow.
It's also a good idea to build and run wireshark and see if anything
strikes your eye as something you'd be interested in seeing work
differently.
For Git we have some suggestions for microprojects at
https://git.github.io/Outreachy-21-Microprojects/
Thanks for writing, and I look forward to working with you. These are
two open source projects that I love and I hope you enjoy working with
them, too. :)
Sincerely,
Jonathan
[1] https://www.outreachy.org/apply/
next prev parent reply other threads:[~2020-10-09 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 19:11 Introduction - An Outreachy 2020 Applicant Amanda Shafack
2020-10-09 0:25 ` Jonathan Nieder [this message]
2020-10-09 1:43 ` Jonathan Nieder
2020-10-09 17:46 ` [Wireshark-dev] " Richard Sharpe
2020-10-09 19:00 ` Emily Shaffer
2020-10-09 18:57 ` Emily Shaffer
2020-10-09 19:29 ` Amanda Shafack
2020-10-09 7:47 ` Amanda Shafack
[not found] <CAGxm6oU+11zAjM6KBNRv4NUhx69CiaLekJ5ZhOhmQA8ofrAzbA@mail.gmail.com>
[not found] ` <CACyXjPy=322gOBbcKpERvBnYnOsPr1OKeTbQktUGSx0+3SSpPA@mail.gmail.com>
2020-10-13 3:10 ` Jonathan Nieder
[not found] <mailman.1.1602590401.25101.wireshark-dev@wireshark.org>
2020-10-15 8:52 ` Wireshark-dev Digest, Vol 173, Issue 14 Amanda Shafack
2020-10-16 3:05 ` Introduction - An Outreachy 2020 Applicant Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201009002541.GB2415320@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=shafack.likhene@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).