git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC - Git Developer Blog

From
Christian Couder <christian.couder@gmail.com>
Date
Aug 6, 2019, 04:59 UTC
Message-ID
<CAP8UFD1XNGWf8=_LvrEsFswZdw5pydk2VyVWxWvwALfhVbBOsg@mail.gmail.com>
In-Reply-To
<xmqqlfw7klwk.fsf@gitster-ct.c.googlers.com>
On Tue, Aug 6, 2019 at 5:35 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
>
> Emily Shaffer <emilyshaffer@google.com> 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?
>
> Interesting.
>
> 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:

https://git-scm.com/docs/git-bisect-lk2009.html

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

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 welcome!

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.

Previous: Junio C HamanoNext: Jeff King
Message 3 of 22 in “RFC - Git Developer Blog”
  1. Emily ShafferAug 6, 2019
  2. Junio C HamanoAug 6, 2019
  3. Christian CouderAug 6, 2019
  4. Jeff KingAug 6, 2019
  5. Emily ShafferAug 6, 2019
  6. Taylor BlauAug 7, 2019
  7. Andrew ArdillAug 6, 2019
  8. Derrick StoleeAug 6, 2019
  9. Emily ShafferAug 6, 2019
  10. Taylor BlauAug 7, 2019
  11. Taylor BlauAug 7, 2019
  12. Junio C HamanoAug 7, 2019
  13. Taylor BlauAug 7, 2019
  14. Jeff KingAug 6, 2019
  15. Emily ShafferAug 6, 2019
  16. James RamsaySep 13, 2019
  17. pedro rijoSep 13, 2019
  18. James RamsaySep 17, 2019
  19. Emily ShafferSep 17, 2019
  20. pedro rijoSep 17, 2019
  21. James RamsayOct 23, 2019
  22. Jeff KingOct 23, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.