git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC] what content should go in https://git-scm.com/doc/ext
@ 2017-01-21 13:55 Jeff King
  2017-01-22 19:13 ` Christian Couder
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2017-01-21 13:55 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] what content should go in https://git-scm.com/doc/ext
  2017-01-21 13:55 [RFC] what content should go in https://git-scm.com/doc/ext Jeff King
@ 2017-01-22 19:13 ` Christian Couder
  2017-01-25 18:42   ` Jeff King
  0 siblings, 1 reply; 3+ messages in thread
From: Christian Couder @ 2017-01-22 19:13 UTC (permalink / raw)
  To: Jeff King; +Cc: git

On Sat, Jan 21, 2017 at 2:55 PM, Jeff King <peff@peff.net> 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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] what content should go in https://git-scm.com/doc/ext
  2017-01-22 19:13 ` Christian Couder
@ 2017-01-25 18:42   ` Jeff King
  0 siblings, 0 replies; 3+ messages in thread
From: Jeff King @ 2017-01-25 18:42 UTC (permalink / raw)
  To: Christian Couder; +Cc: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-01-25 18:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-21 13:55 [RFC] what content should go in https://git-scm.com/doc/ext Jeff King
2017-01-22 19:13 ` Christian Couder
2017-01-25 18:42   ` Jeff King

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 NNTP newsgroup(s).