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

Re: [RFC] what content should go in https://git-scm.com/doc/ext

From
Christian Couder <christian.couder@gmail.com>
Date
Jan 22, 2017, 19:13 UTC
Message-ID
<CAP8UFD3Z9ZrLEZVkgL7ACkL5nOsoo2R6dUC=Bfy1AjF_9+4snQ@mail.gmail.com>
In-Reply-To
<20170121135545.gi6crct66msylhpr@sigill.intra.peff.net>
On Sat, Jan 21, 2017 at 2:55 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> I'm wondering if anybody has opinions on:
>
>   https://github.com/git/git-scm.com/pull/924
>
> (and I suspect most people in this community do not read pull requests
> there, hence this post).
Yeah, thanks for posting it here.
> Basically, we maintain a list of links to outside documentation, as well
> as to books. Somebody has requested a link to their paid tutorial
> course. How should we handle it?
I think it depends if you are ready and willing to handle more changes.
Show 6 quoted lines
> If the resource is valuable, then it may make sense to link to it, even
> if it costs money. We already do this with book links, and my policy has
> been to link any relevant book that is requested (I don't read them for
> quality, so I have no opinions).
>
> Should we do the same for tutorial content like this?

It could make sense to link to tutorial content, and then it could also make sense to link to trainings (online and maybe offline too), but my fear is that you could then have many people who want to advertise their tutorials and trainings, and that it might be difficult to draw a line while keeping the playing field even.

But maybe it's worth trying anyway.
Previous: Jeff KingNext: Jeff King
Message 2 of 3 in “[RFC] what content should go in https://git-scm.com/doc/ext”
  1. Jeff KingJan 21, 2017
  2. Christian CouderJan 22, 2017
  3. Jeff KingJan 25, 2017

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.