git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Cc: Emily Shaffer <emilyshaffer@google.com>, git@vger.kernel.com
Subject: Re: Introduction - An Outreachy 2020 Applicant
Date: Mon, 12 Oct 2020 20:10:59 -0700	[thread overview]
Message-ID: <20201013031056.GC3814681@google.com> (raw)
In-Reply-To: <CACyXjPy=322gOBbcKpERvBnYnOsPr1OKeTbQktUGSx0+3SSpPA@mail.gmail.com>

Richard Sharpe wrote:
> Amanda Shafack wrote:

>> Good day.
>>
>> I'm Amanda Shafack, an Outreachy 2020 applicant who wishes to
>> contribute to the "Add Git protocol support to Wireshark" project.
>>
>> I have some experience coding in C and I hope to enhance
>> my skill set by contributing to this project.
>>
>> In addition, I'm fascinated by network protocols and it's really
>> exciting to get my hands around these concepts in a real-world
>> project.
>>
>> I'm currently going through the project description and contribution
>> guidelines.
>
> Welcome. There are many helpful people on the list.
>
> It would be useful if you can point us to a protocol description
> document but that can wait until help is needed. It may be that all
> the online resources are sufficient, but if not, do not hesitate to
> use this list to ask questions.

There's an overview of Git's HTTP protocol in the Pro Git book:

  https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols

The official protocol spec in git.git (https://git.kernel.org/pub/scm/git/git.git)
is split between a few files:

  Documentation/technical/protocol-common.txt:
    conventions for protocol docs

  Documentation/technical/pack-protocol.txt:
    overview of Git protocol

  Documentation/technical/protocol-capabilities.txt:
    optional capabilities

  Documentation/technical/protocol-v2:
    protocol v2, the new default (more about this is at
    https://opensource.googleblog.com/2018/05/introducing-git-protocol-version-2.html)

  Documentation/technical/http-protocol.txt:
    how this works with http

  Documentation/technical/pack-format.txt:
    packed representation of Git objects (used both on disk and over
    the wire)

Amanda, if you have any questions, please don't hesitate to ask
(#git-devel on IRC is the best place for that, and email works as
well).  I am there around 15:00-24:00 UTC most days.  In addition to
working on your initial starter contributions, we can start to put
together a plan for the project.

Richard, to set expectations: the internship period for accepted
interns starts in December: https://www.outreachy.org/apply/project-selection/.
Until then, potential interns are often not free full time, so we
focus on smaller contributions that help get their feet wet in the
codebase.

Excited,
Jonathan

       reply	other threads:[~2020-10-13  3:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGxm6oU+11zAjM6KBNRv4NUhx69CiaLekJ5ZhOhmQA8ofrAzbA@mail.gmail.com>
     [not found] ` <CACyXjPy=322gOBbcKpERvBnYnOsPr1OKeTbQktUGSx0+3SSpPA@mail.gmail.com>
2020-10-13  3:10   ` Jonathan Nieder [this message]
     [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
2020-10-08 19:11 Amanda Shafack
2020-10-09  0:25 ` Jonathan Nieder
2020-10-09  1:43   ` Jonathan Nieder
2020-10-09 18:57     ` Emily Shaffer
2020-10-09 19:29       ` Amanda Shafack
2020-10-09  7:47   ` Amanda Shafack

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=20201013031056.GC3814681@google.com \
    --to=jrnieder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.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.
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).