mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <>
To: Andrew Ardill <>,
	Emily Shaffer <>
Cc: git <>, Taylor Blau <>
Subject: Re: RFC - Git Developer Blog
Date: Tue, 6 Aug 2019 08:19:15 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8/6/2019 12:52 AM, Andrew Ardill wrote:
> On Tue, 6 Aug 2019 at 11:51, Emily Shaffer <> wrote:
>> Are folks interested in writing and reviewing this kind of content?

I am interested in writing and reviewing! Here are some topics I am
interested in writing:

* Updates to the commit-graph feature
* What is a multi-pack-index and what is it for?
* Git at Scale: What makes a repo big, and how to avoid it?
* Advanced Git config settings

Here are some topics I'd be interested in seeing in the wild
(and was considering writing them myself if I didn't see them elsewhere):

* Partial clone: what, why, and how?
* Life cycle of a patch series
* Crafting perfect patches with interactive add and rebase

It would also be helpful to have a post for every major release
highlighting new features and giving users examples of how to use them.
Taylor has been writing these on the GitHub blog [1], but maybe he
would be interested in writing them for this new venue?


> The idea sounds great, and I would be happy to review content - even
> if it's only for readability and spelling!
> In terms of collaborating, I've found the processes over at Git Rev
> News[0] straightforward and sensible, if you're looking for ideas.

I agree that the review process there is helpful, and users contributing
edits via PRs to a feature branch works quite well. I would also suggest
writing a "request for review" on the mailing list before merging any
pull requests.

One goal I think would be important is that this blog is that the posts
come with some amount of blessing from "the Git Dev Community". That is,
they should be service-agnostic and focused on helping _all_ Git users.

That said, I also suggest that the authors can list their professional
affiliation as some minimum amount of credit to their employers. Something
as simple as "Author: Derrick Stolee, Microsoft" would go a long way to
justifying the work it takes to write these on the community blog and not
a company-owned blog.

  reply	other threads:[~2019-08-06 12:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  1:49 RFC - Git Developer Blog Emily Shaffer
2019-08-06  3:33 ` 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 [this message]
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).