One area that could use a little cleanup is examples of the differing syntax's
for using client certificates. It is possible to figure it out from existing
docs, but if you aren't already used to using the cert9.db NSS certutil syntax
switching over from the openSSL backend is a bit of a headache.
I s'pose that means I should submit the examples I care about phrased into the
existing docs in a way that makes sense to me so people switching from RHEL 5
to RHEL 6 (for example) can see how to fix their broken scripts that depend on
cURL a bit more easily. I'll try to remember that when I'm at work Monday.
________________________________
From: Daniel Stenberg <[email protected]>
To: libcurl development <[email protected]>
Sent: Saturday, June 14, 2014 2:31 PM
Subject: Re: the survey summary
On Fri, 13 Jun 2014, Daniel Stenberg wrote:
> http://curl.haxx.se/docs/survey/survey2014.html
One of the most surprising results (to me) is that "docs" was voted the most
"worst area" in the project with a big margin. (Admittedly twice as many also
voted it as one of the best areas).
I'd like to understand this better. What exactly is considered bad and what
can we do about it? I think I'm having my nose a little too deep in all the
details to see this clearly. I was under the impression our documentation was
pretty good...
What's the biggest problem with the current docs? What's the biggest thing we
lack? Please share some ideas and thoughts here!
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
