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
Jeff King <peff@peff.net>
Date
Jan 25, 2017, 18:42 UTC
Message-ID
<20170125184258.v5sy6hwwpdsxz2u6@sigill.intra.peff.net>
In-Reply-To
<CAP8UFD3Z9ZrLEZVkgL7ACkL5nOsoo2R6dUC=Bfy1AjF_9+4snQ@mail.gmail.com>
On Sun, Jan 22, 2017 at 08:13:53PM +0100, Christian Couder wrote:
Show 5 quoted lines
> > 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.

I don't clicking "merge" on more changes if people are willing to do the design work.

Show 9 quoted lines
> > 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.

I think I'm inclined to try it, as long as it's kept in a separate "paid training" section, and is open to everybody. If it becomes a burden, we can cut it out later. I think the important thing is that it be equally open to everybody or nobody, but not just "some". So we'll go with everybody for now, and switch to nobody later if need be.

-Peff
Previous: Christian Couder
Message 3 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.