Skip to content

Comment on Ask HN: Best practices for open sourcing your project?

Comments

In line with the "release early, release often" mantra, you can just go ahead and do it.

Secrets are usually split into separate "configuration" repositories that remain private, and that's the only gotcha.

Any other time you invest in beautifying your code, writing documentation, stripping ads and making them configurable, might be in vein: most open source projects do not attract any contributors, yet having these "easy pickings" is also stimulating for someone to contribute.

Your users are better served having an ability to tinker with the code than waiting for the code to become nicer. At least, the free software persona in me says so :)

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.