git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: git <git@vger.kernel.org>
Subject: Git Developer Pages cleanup
Date: Sun, 10 Nov 2019 19:15:35 +0100	[thread overview]
Message-ID: <CAP8UFD3sVR+Z3ktYUhSCtfCr9fY0btX2UEve+o0y=iuooVTVEQ@mail.gmail.com> (raw)

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.

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.

* 9f46f72 Outreachy: rename Outreachy-2016-May to Outreachy-12

An old Outreachy related file now has a similar name as other
Outreachy related files.

* 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.

* 5f6b197 General-Microproject-Information: newbie related improvements

As the document can be useful to newcomers, tell a bit about that in
the document.

Thoughts?

Thanks,
Christian.

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 18:15 Christian Couder [this message]
2019-11-11  4:15 ` Git Developer Pages cleanup Jeff King

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='CAP8UFD3sVR+Z3ktYUhSCtfCr9fY0btX2UEve+o0y=iuooVTVEQ@mail.gmail.com' \
    --to=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).