Quote:
Originally Posted by chaley
I am mildly surprised that more people don't volunteer to do documentation. It requires no python/programming skills, can be done incrementally, is a good way to learn, would be actively supported by people, and is a fine way to contribute to the project.
|
Probably because we're afraid that what we wrote would be wrong, and cause a lot more problems.
Even though I've used the program for a while, it was even hard to ask a question, because I didn't have the right words for the right process I was trying to ask about. So I had to explain what I was looking at more than once, because I didn't know what everyone else called that feature.
I try to point a lot of people toward Calibre, but do have a problem with a lot of questions about devices I don't have, and processes I've never tried myself. (For example, I'm happy with the font size on the Sony, so haven't tried all the features in the bulk convert options yet.)
So when asked, I try to find the answer here, or point people here. But as it gets more features it gets more complicated. And the answers get harder to find.
I think it would help more if the people who contribute to the program do the documentation on their own bits and then have it collected on the web site. The person who wrote it should be able to explain it.
Such as that feature from the Sony. A small note at the site might help, or something at the web site. You really have to do a lot of digging to find out the barest clue to some of this stuff.
And I've junked up whole libraries in the past by playing around on my own. I'm really leery of doing that again. So experimentation is pretty much out unless I do find that clue. Somewhere.