From: Christian Couder <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>
Cc: Emily Shaffer <firstname.lastname@example.org>,
git <email@example.com>, Jakub Narebski <firstname.lastname@example.org>,
Markus Jansen <email@example.com>,
Gabriel Alcaras <firstname.lastname@example.org>
Subject: Re: RFC - Git Developer Blog
Date: Tue, 6 Aug 2019 06:59:21 +0200 [thread overview]
Message-ID: <CAP8UFD1XNGWf8=_LvrEsFswZdw5pydk2VyVWxWvwALfhVbBOsg@mail.gmail.com> (raw)
On Tue, Aug 6, 2019 at 5:35 AM Junio C Hamano <email@example.com> wrote:
> Emily Shaffer <firstname.lastname@example.org> writes:
> > 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.
> > ...
> > 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.
> > Thoughts?
> I recall that I used to do the "Fun with ..." series back when I was
> more into use-case-exploration mode; writing those articles was fun,
> but it took a lot of time and quite an effort, so I stopped after
> writing enough.
Linux-Kongress (LK) was a conference organized by the German Unix User
Group from 1994 to 2010. They asked authors of accepted submissions
for the technical sessions to provide a paper for publication in the
conference proceedings. As I wanted to give a presentation at LK 2009,
I wrote a paper about git bisect and asked kind souls (like Junio) to
review it on the mailing list. A bit later it was included in the Git
documentation and is still there:
The git bisect man page links to it, but I must say that it tends to
be a bit obsolete as it has not really been updated.
There are also "guides" that are part of the actual documentation and
can be listed using `git help -g`.
> Making it a group effort may help by allowing writers and reviewers
> to encourage each other.
When Git Rev News was started I thought that there could be such a
group effort to encourage each other to publish articles in it, but I
must say that outside the group of editors (currently Jakub, Markus,
Gabriel and me) it hasn't happened much.
Each month though there are a small number of people helping on
smaller things like short news, typos, releases, etc. And people who
are interviewed are doing a great job when they accept to be
Maybe it's also not clear that we could accept other kind of articles
than just articles focused on what happens on the mailing list. I
think we have generally tried to highlight articles by Git developers
that were published on their blogs or their company's blog though.
In any case if you or others would like to join the editor group to
focus on other kind of articles, or just to help a bit, you are most
I would also be ok to change the form of Git Rev News if there is an
official blog. For example the "Discussions" section could become
something like "Featured articles" with links to articles on the blog.
next prev parent reply other threads:[~2019-08-06 4:59 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 [this message]
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
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: 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 \
* 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).