git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joey S <jgsal@protonmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: [Outreachy] Introduction
Date: Fri, 16 Oct 2020 22:09:58 +0000	[thread overview]
Message-ID: <HiG3ctHji8hdGWXWEwWgeoa6eDDHkUbhfa0x0xYr9EHWD7FqXqZsQt3fHMZ4Vle0jo2QPCW8rjRviw_aGKqxUIFtvX2igp1aUnx9p6YCL0Y=@protonmail.com> (raw)

[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



             reply	other threads:[~2020-10-16 22:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 22:09 Joey S [this message]
2020-10-16 23:08 ` [Outreachy] Introduction Jonathan Nieder
2020-10-17  0:42   ` Joey S
  -- strict thread matches above, loose matches on Subject: below --
2020-10-16  8:28 Zodwa Phakathi
2020-10-16  8:46 ` Christian Couder
     [not found]   ` <CAGdqGXrLN2W_CgqfmfkCSu_hmZ9Ze8A1N9n08bgPRPApSMraSQ@mail.gmail.com>
2020-10-16 10:02     ` Christian Couder
2020-10-10 11:48 Charvi Mendiratta
2020-10-11  8:09 ` Christian Couder
     [not found]   ` <CAPSFM5cXN57z56Cvq-NX1H4raS7d8=qXEFDQqpypJfoYzbxcyA@mail.gmail.com>
2020-10-15 18:56     ` Charvi Mendiratta
2020-10-15 19:16       ` Junio C Hamano
2020-10-17  8:09         ` Charvi Mendiratta
2020-10-07 20:10 Sangeeta NB
2020-10-08  9:07 ` Phillip Wood
2020-10-09  7:41   ` Sangeeta NB
2020-10-09 18:29     ` Phillip Wood
2020-10-11 11:30       ` Sangeeta NB
2020-10-12 10:18         ` Phillip Wood
2020-10-12 11:22         ` Kaartic Sivaraam
2020-10-12 15:57         ` Junio C Hamano
2020-10-14 15:52           ` Sangeeta NB
2020-10-15  9:23             ` Phillip Wood
2020-10-15 10:18               ` Sangeeta NB
2020-10-15 13:39                 ` Phillip Wood
2020-10-15 13:57                   ` Sangeeta NB
2020-10-15 14:45                     ` Phillip Wood
2020-10-16  5:27                       ` Sangeeta NB
2020-10-16 13:26                         ` Phillip Wood

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='HiG3ctHji8hdGWXWEwWgeoa6eDDHkUbhfa0x0xYr9EHWD7FqXqZsQt3fHMZ4Vle0jo2QPCW8rjRviw_aGKqxUIFtvX2igp1aUnx9p6YCL0Y=@protonmail.com' \
    --to=jgsal@protonmail.com \
    --cc=git@vger.kernel.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).