mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <>
Subject: RFC - Git Developer Blog
Date: Mon, 5 Aug 2019 18:49:35 -0700	[thread overview]
Message-ID: <> (raw)

Hi all,

In backchannels recently there has been some discussion about the idea
of a Git-project-blessed blog written by Git contributors, generally
covering usability tips or overviews of the internals of Git which the
general public tend to find confusing.

Ideally, we could use a channel like this to make Git better understood
in the rest of the world, in a less formal setting than the man pages or
gittutorial. I think it would be valuable to have resources which have
been reviewed and endorsed by the Git contributor community, in addition
to individual company blogs. (It might even make sense for contributors
who would normally post this kind of thing to their company blog to
cross-post the content in both places.)

Are folks interested in writing and reviewing this kind of content? Any
ideas for where we may be able to host (maybe git-scm)? It could make
sense to review contributions like this on the mailing list, so that we
get the attention of those who wrote the features that are being covered
in the blog posts - are we okay with the additional traffic?

Some example topics, from the top of my head:

 - Using `git worktree` Effectively
 - Overview of the Git Object Store
 - Finding Regressions with `git bisect`
 - Life of a Git Remote Request

The idea is that we could cover high level topics stringing together
multiple components or giving power user advice, which we can't really
do with the manpages.


 - Emily

             reply	other threads:[~2019-08-06  1:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  1:49 Emily Shaffer [this message]
2019-08-06  3:33 ` RFC - Git Developer Blog Junio C Hamano
2019-08-06  4:59   ` Christian Couder
2019-08-06 13:27     ` Jeff King
2019-08-06 21:07       ` Emily Shaffer
2019-08-07 17:00       ` Taylor Blau
2019-08-06  4:52 ` Andrew Ardill
2019-08-06 12:19   ` Derrick Stolee
2019-08-06 21:00     ` Emily Shaffer
2019-08-07 17:12       ` Taylor Blau
2019-08-07 17:07     ` Taylor Blau
2019-08-07 17:15       ` Junio C Hamano
2019-08-07 17:44         ` Taylor Blau
2019-08-06 13:20 ` Jeff King
2019-08-06 20:49   ` Emily Shaffer
2019-09-13 13:29     ` James Ramsay
2019-09-13 14:05       ` pedro rijo
2019-09-17 19:22         ` James Ramsay
2019-09-17 19:32           ` Emily Shaffer
2019-09-17 19:39             ` pedro rijo
2019-10-23 22:36       ` James Ramsay
2019-10-23 23:48         ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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

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