[lukeholder]

Why does he need to make a good impression? look at the code and make your determination - build it and make a pull request with your improved video. This is the spirit of Github: he may be an awesome coder but weak in video production - fork and collaborate.

[eridius]

You seem to be of the mindset that "Open Source" means "other people will be eager to contribute". That's not necessarily the case. If you want people to contribute, you need to give them a reason to do so. People like contributing to high-quality projects. If the first impression of your project indicates a lack of quality, this will deter people from looking any further.

[docgnome]

s/Github/FOSS/

Fixed that for you.

[docgnome]

Hrm. I was trying to make a point about confusing Github with FOSS which greatly predates it. These days it seem to be becoming a more common mistake to make. I guess I didn't do that very well.

[eropple]

Sure, that might happen. Or someone could spend their time writing code for their own projects instead of building a video for someone else's, because hey, he couldn't be assed to make his project interesting enough to spend time playing with. My first reaction, too, was "that's a pretty half-assed job," and closed the window. That makes it very unlikely that I go back and use it if I find a case where it might be valuable (because I won't remember it, except for the low-quality video and the lack of a demo - doesn't GitHub have a "pages" feature, anyway, where he could embed a real video on YouTube or something?). And if I'm not using it, there's zero chance of me going "hey, this could be great if X," writing X, and contributing it back.

It might be anathema to the "code is everything!" mindset, but part of getting people interested in your projects is presentation. You might think that's not the spirit of Github, but it's the way lots of (most?) people roll.