[kunwon1]

It seems to be getting more and more common to leave your git repository completely undocumented. If you're releasing a software project on github, I want to read about it on github.

A basic README that outlines what it does, how it does it, and basic syntax - this is really easy. Table stakes, I might say. I can checkout your repo and I have everything I need to work

[zeeg]

Don’t disagree, but technically the docs are in the same repo. Not easily consumed though.

We removed bits from the readme as it kept becoming duplicated and eventually wrong. I think that’s the usual reason folks like to avoid it. DRY and all.

[1letterunixname]

It's a terrible habit. Documentation is a nonfunctional requirement. It should describe what is not obvious to someone new and the value of it. Without the conveyance of utility and purpose, all of a project's potential value goes to waste with foot-gunning accuracy.

[ren_engineer]

a lot of "open source" companies leave their repos bare so you are forced to go onto their website where they can better track and retarget you

[bentlegen]

I assume you're not talking about this company because there is no such script on spotlightjs.com (easily verifiable), and the docs are also actually in the repository:

Example: https://github.com/getsentry/spotlight/blob/main/packages/we...

[joshmanders]

Retarget you for what? "Hey you should come back and read the docs on our open source project you were interested in last week"