git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git Developer Pages cleanup
Date: Sun, 10 Nov 2019 23:15:51 -0500	[thread overview]
Message-ID: <20191111041551.GD6379@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD3sVR+Z3ktYUhSCtfCr9fY0btX2UEve+o0y=iuooVTVEQ@mail.gmail.com>

On Sun, Nov 10, 2019 at 07:15:35PM +0100, Christian Couder wrote:

> Hi everyone,
> 
> For sometime I have been thinking about cleaning up the Git Developer
> Pages web site (https://git.github.io/), and making some of the
> documentation there more generic and possibly more useful for all kind
> of newcomers.

Thanks for taking care of this. I agree these pages have been in need of
some cleanup for ages.

> So I pushed the following commits:
> 
> * 17b7b3e SoC: remove 2017 SoC material from the navbar
> * 4e01d0a SoC: remove 2018 SoC material from the navbar
> * 7c13096 Outreachy: fix titles
> 
> Old GSoC and Outreachy material can now only be accessed through the
> Historical Summer of Code Materials
> (https://git.github.io/SoC-Historical/) link.

I almost wonder if they could be dropped entirely, as they'd still be
accessible via the Git repository. But maybe somebody finds it useful to
be able to see them from the built web page.

> * 717ec3c Add General-Microproject-Information.md
> 
> Extract information from https://git.github.io/SoC-2019-Microprojects/
> to make it independent of GSoC or Outreachy. I think it's really
> better to have a separate document and just link to it, instead of
> copy pasting it each time.

Yeah, this is much better.

-Peff

      reply	other threads:[~2019-11-11  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 18:15 Git Developer Pages cleanup Christian Couder
2019-11-11  4:15 ` Jeff King [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=20191111041551.GD6379@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.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.
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).