git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Taylor Blau <ttaylorr@github.com>, git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] git-scm.com Heroku credits update
Date: Mon, 11 Apr 2022 11:18:22 -0400	[thread overview]
Message-ID: <YlRGvmPCoWn8DFTs@nand.local> (raw)
In-Reply-To: <xmqq35ino356.fsf@gitster.g>

On Fri, Apr 08, 2022 at 11:12:37AM -0700, Junio C Hamano wrote:
> > I wonder if this could be an Outreachy (maybe next Winter) or a GSoC
> > (2023) project.
>
> Good suggestion.

I agree!

> It would take talent quite different from what our past GSoC
> programs saw, from both mentors and "contributors" (we used to call
> them "students").  If we have mentors who can give good experience
> to mentees, I would welcome to see such a task for a change.

I would be happy to help mentor a new contributor as somebody vaguely
familiar with the architecture of the existing site, though I have next
to no experience / good judgement on current web best practices ;).

Thanks,
Taylor

  reply	other threads:[~2022-04-11 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 16:22 [ANNOUNCE] git-scm.com Heroku credits update Taylor Blau
2022-04-04 23:09 ` Taylor Blau
     [not found]   ` <CAKUhyqE2L9MiNvauA6kaPstvNp6ift5ehfmeFxKvb2DjPvOnsA@mail.gmail.com>
2022-04-04 23:27     ` Dan Moore
2022-04-05  3:14   ` Kaartic Sivaraam
2022-04-06  9:52   ` Phillip Wood
2022-04-11 15:21   ` Taylor Blau
2022-04-18 23:43     ` Taylor Blau
2022-04-07 21:54 ` Johannes Schindelin
2022-04-08  8:10   ` Christian Couder
2022-04-08 18:12     ` Junio C Hamano
2022-04-11 15:18       ` Taylor Blau [this message]
2022-04-11 15:16   ` Taylor Blau

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=YlRGvmPCoWn8DFTs@nand.local \
    --to=me@ttaylorr.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ttaylorr@github.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).