git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: 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: Fri, 08 Apr 2022 11:12:37 -0700	[thread overview]
Message-ID: <xmqq35ino356.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD2fN=c2JvvzH94Nu8yqt2MOOtXrn29eFxuie9aZ5YVjQw@mail.gmail.com> (Christian Couder's message of "Fri, 8 Apr 2022 10:10:08 +0200")

Christian Couder <christian.couder@gmail.com> writes:

> On Fri, Apr 8, 2022 at 12:39 AM Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>>
>> On Fri, 1 Apr 2022, Taylor Blau wrote:
>
>> > To that end, we have a few options about what to do with the website in
>> > the future:
>> >
>> >   - Convert the Rails application into a static site that could be
>> >     hosted elsewhere for free. The non-static portions of the site would
>> >     have to become static in one way or another, and we'd have to come
>> >     up with an alternative search mechanism to replace the existing one.
>>
>> This is my preference (and I would love to contribute the time, but am
>> quite short on that resource to help much).
>
> I wonder if this could be an Outreachy (maybe next Winter) or a GSoC
> (2023) project.

Good suggestion.

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.

Thanks.



  reply	other threads:[~2022-04-08 18:12 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 [this message]
2022-04-11 15:18       ` Taylor Blau
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=xmqq35ino356.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --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).