Hacker News new | past | comments | ask | show | jobs | submit login

You can start on github just by being clear what sort of repo you have in the readme. There's all kinds of projects on there, from "I accidentally the fork button" to production grade stuff, and it's often hard to guess which the author thinks they have.



This is a really important hint. Put a note in that describes what people can expect from you and what not. Maybe there even should be some "standard" for this info, and a place to put it (either in the repo, or in the description), so you could easily find it.

Also, don't forget to update those notes if things change.


Yeah, I really think this is all that's needed.

For instance, it's enormously helpful, in the aggregate, that people have repos that are simply "example of an application that uses Foo with a Bar adapter."


I think this is a good idea.

I will add as a side note, if you can't maintain something anymore, put a big heading on the README.md saying so. If it's popular, point people to a maintained fork.

(Nothing I write is extremely popular but I'm going to go through and "deprecate" a few things of mine tonight)


Github could use the 1-alpha, 5-production system.

At least you'd get a hint at the intention behind the release.


I really wish there was tagging and categorization - I have so many little repos, and now recruiters look at my GitHub as part of my resume. Is hitting the Fork button going to have impacts on my future employment?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: