I'm not blaming anyone or saying anyone is wrong.
But I almost named a project I was involved "beaver" something. (No, I am not a native speaker)
We also have a trademark on the name Kiln in the context of developer tools.
Edit: That last line sounds like a threat, which it absolutely isn't. Just, due to how these things work, picking another name probably makes sense.
Edit: I'm brainstorming names on the rubymotion google group. F-ing naming, it's so annoying. I'll try and get it renamed soon.
There's also no law against picking descriptive names.
Did you develop an egg smashing simulator? Where's the harm in calling it "Egg Smash Simulator Kit" instead of "Humpty" or some other confusing bloody puntastic name?
You're joking, right? Yes. You need to pick a name for your product that doesn't clash with a well established product in the same field.
I only clicked this article because I thought Joel had gone open-source. I suspect most everyone reading this thread thought the same thing.
Kiln is kind of a shitty name to begin with, so I'm sure you'll think of something better. I'd focus on how it's self-hosted, handheld, mobile, lightweight, and portable.
"Phone Self Exam" is one bad idea, with the obvious non-Ada Initiative approved branding concept...
Having heard of Joel or Fog Creek is one thing. Having heard of their Kiln project is another.
Wrong, my post originally said "The Fog Creek project" (as opposed to the OP's project). The only word I added was "Kiln", to make it clearer.
> How about some integrity?
How about stopping to think before making accusations about other people's integrity, rather than shooting from the hip? I see you're new to HN. Why don't you learn some etiquette by reading the HN guidelines, it'll help you to avoid the banhammer: http://ycombinator.com/newsguidelines.html
I'm not a "documentation expert" or anything, but IMHO I'd say there is too much information on your "landing page" and not a clear "call to action":
- How about some installation instructions?
- Basic usage? (addressing the main features, those which most users will probably use most of the time)
If I were you I'd put the details about plugins somewhere in the Wiki.
I don't have a lot of spare time to check out your thing, so the project becomes increasingly unattractive as I have to waste more and more time to figure out how to use it / how to get it up and running for a basic test.
Again, IMHO, I believe this applies to most hackers, and to open source documentation in general. Very often I see great hackers who can code 1000x better than I do, but fail to write 'attractive' documentation for their projects.
Different, though, because Kiln is meant to be more generic, and pluggable.