3 ms·
I can't count the number of times I've read an announcement of some OSS project, gone to the project home page, read it all and still had absolutely no idea wha
by simonh 8y ago
I can't count the number of times I've read an announcement of some OSS project, gone to the project home page, read it all and still had absolutely no idea what it was, what it did or why it might be important.
It is impressive how much Linus had working at that point though. Getting bash and gcc working and a multithreaded FS is no mean feat, and is enough for other people to actually make useful contributions without excessive pain.
- jonny_eh 8y agoIt probably means you're not the target audience.
- tomrod 8y agoWhile this may be true, it can still be helpful to have an FAQ, context, or other way that interested parties can understand applicability. I fully appreciate shorthand/jargon are ways to communicate complex ideas swiftly. Yet, taking time to provide some form of entry point for the uninitiated shows a disciplined approach that often translates to other areas of the project.
- lloydde 8y agoMost often it is that the author is so involved they forget to given enough context. They are so passionate about a topic, but don’t realize that others do not drink the same Kool-Aid every day. More than half of the emails I get from technology companies fail to start with a reminder of what their product or service does. I see this much, much less frequently with consumer products — better marketing.
- aasasd 8y agoI usually have to go to Wikipedia to learn what a project is about, since their format puts the info in the first couple paragraphs. If a project is not (yet) there, it's either Github, because markdown readmes somehow force the crux of the matter out of people… or it's goodbye.
- caf 8y agoIt is impressive how much Linus had working at that point though. Particularly when you consider that he had to do it all on bare metal.