From: Jonathan Nieder <jrnieder@gmail.com>
To: Joey Salazar <jgsal@protonmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"wireshark-dev@wireshark.org" <wireshark-dev@wireshark.org>
Subject: Re: [Outreachy] Internship blog 2020
Date: Thu, 3 Dec 2020 18:47:08 -0800 [thread overview]
Message-ID: <X8mjLHvNCYimATw7@google.com> (raw)
In-Reply-To: <I55UpoMB_QMpFuqJEp1cHW7oN8AJy-b5iveBe2kZLslum_LOctwR5IdXUJhzZETg7bZDtm4beN38Nz6kvpJKDf0luxBMFxfpoFCYWkwaae4=@protonmail.com>
Hi Joey,
Joey Salazar wrote:
> Very happy to be joining for this winter's internship! A short blog
> entry on the beginning of this journey here: https://jsal.home.blog/
>
> A new entry every 2 weeks, check it out!
>
> Thank you Outreachy, Git, and Wireshark for the opportunity, happy
> to be working together!
Welcome! I'm looking forward to working together (starting with an
initial wireshark patch to get the lay of the land, then fleshing out
the plan for the project, then executing on it in earnest).
A question for wireshark developers: are there preferences for what a
high quality dissector looks like? [1] talks about portability and
robustness but doesn't address other aspects of convention such as how
long functions should be (like [2] does). Is there a rule of thumb
like "when in doubt, do things the way <such-and-such dissector>
does?"
Excited,
Jonathan
[1] https://gitlab.com/wireshark/wireshark/-/raw/master/doc/README.developer
[2] https://www.kernel.org/doc/html/v5.9/process/coding-style.html
next prev parent reply other threads:[~2020-12-04 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 2:50 [Outreachy] Internship blog 2020 Joey Salazar
2020-12-04 2:47 ` Jonathan Nieder [this message]
2020-12-04 3:28 ` [Wireshark-dev] " ronnie sahlberg
2020-12-04 3:33 ` ronnie sahlberg
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=X8mjLHvNCYimATw7@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jgsal@protonmail.com \
--cc=wireshark-dev@wireshark.org \
/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).