# [RFC] what content should go in https://git-scm.com/doc/ext 3 messages from 2017-01-21 to 2017-01-25. Participants: Jeff King, Christian Couder. Thread: https://gitlist.dev/t/44931 ## Jeff King, 2017-01-21 13:55 Subject: [RFC] what content should go in https://git-scm.com/doc/ext Message-ID: <20170121135545.gi6crct66msylhpr@sigill.intra.peff.net> URL: https://gitlist.dev/e/20170121135545.gi6crct66msylhpr%40sigill.intra.peff.net ``` 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). 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? 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? -Peff ``` ## Christian Couder, 2017-01-22 19:13 Subject: Re: [RFC] what content should go in https://git-scm.com/doc/ext Message-ID: URL: https://gitlist.dev/e/CAP8UFD3Z9ZrLEZVkgL7ACkL5nOsoo2R6dUC%3DBfy1AjF_9%2B4snQ%40mail.gmail.com In-Reply-To: <20170121135545.gi6crct66msylhpr@sigill.intra.peff.net> ``` On Sat, Jan 21, 2017 at 2:55 PM, Jeff King wrote: > 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. > 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. ``` ## Jeff King, 2017-01-25 18:42 Subject: Re: [RFC] what content should go in https://git-scm.com/doc/ext Message-ID: <20170125184258.v5sy6hwwpdsxz2u6@sigill.intra.peff.net> URL: https://gitlist.dev/e/20170125184258.v5sy6hwwpdsxz2u6%40sigill.intra.peff.net In-Reply-To: ``` On Sun, Jan 22, 2017 at 08:13:53PM +0100, Christian Couder wrote: > > 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. > > 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 ```