git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Richard Sharpe <realrichardsharpe@gmail.com>
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Cc: Emily Shaffer <emilyshaffer@google.com>, git@vger.kernel.org
Subject: Re: [Wireshark-dev] Joint project with Git for outreachy
Date: Sat, 19 Sep 2020 09:17:50 -0700	[thread overview]
Message-ID: <CACyXjPzNCvFznmu9ARaUt_gsQ+fUMgYsHtBFDDziWRmsWJyq7A@mail.gmail.com> (raw)
In-Reply-To: <20200918222103.GA3352870@google.com>

On Sat, Sep 19, 2020 at 8:21 AM Jonathan Nieder <jrnieder@gmail.com> wrote:
>
> Hi wiresharkers,
>
> Outreachy <https://www.outreachy.org/> is a program similar to the
> Google Summer of Code, providing internships to work on open source
> projects.
>
> Emily (cc-ed) and I would be interested in mentoring an outreachy
> intern on adding support for the Git protocol to wireshark.  We think
> this would be helpful for documenting the spec better, for making
> debugging easier for future Git developers, and for helping people
> working on systems involving Git (e.g. CI systems) to understand the
> behavior of the systems they oversee.  We think that a co-mentor
> within wireshark would be helpful for making sure an intern is set up
> for success (helping them find pointers, making sure their approach is
> on the right track, etc).
>
> This would be a project under the Git umbrella
> <https://www.outreachy.org/communities/cfp/git/>.
>
> What do you think?  Does this sound interesting to you?

Replying again to all this time.

We welcome any one who wants to write a dissector or help out in any
area of Wireshark, as Ronnie said.

I am more than happy to offer advice and ideas and look at code to get
new Wireshark developers going.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)(传说杜康是酒的发明者)

      parent reply	other threads:[~2020-09-19 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 22:21 Joint project with Git for outreachy Jonathan Nieder
2020-09-19  9:12 ` ronnie sahlberg
2020-09-19 19:55   ` brian m. carlson
2020-09-19 22:36     ` Junio C Hamano
2020-09-20 16:17       ` Emily Shaffer
2020-09-21 11:33         ` ronnie sahlberg
2020-09-21 15:24         ` [Wireshark-dev] " Richard Sharpe
     [not found]           ` <CALcKHKoE2BCZEuW7rmsCdY4LSyvnCTBDLmgifND7TH+v5ma-6w@mail.gmail.com>
2020-09-21 22:07             ` Gerald Combs
2020-09-19 16:17 ` Richard Sharpe [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACyXjPzNCvFznmu9ARaUt_gsQ+fUMgYsHtBFDDziWRmsWJyq7A@mail.gmail.com \
    --to=realrichardsharpe@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).