curl and libcurl user survey 2018
In order to better understand where we are and where to go next, this is a set of questions to poll interests and opinions from users of curl and libcurl. The questions are mostly the same as last year and the year before that, to make it easier for us to see year-by-year changes and detect trends.

You answer anonymously (to the extent you can be anonymous in a Google form), but please stay honest and fair. Answer only once per person. Just skip the questions you can't or won't answer.

The poll is open fourteen days from Tuesday May 15th until midnight (CEST) Monday May 28th 2017.

Please share this link to other fellow curl and libcurl users to allow us to get the widest possible feedback.

How are you using curl/libcurl ?
Check the protocols you use curl/libcurl for
Within the let's say last 2 years or so.
Do you use curl/libcurl on multiple platforms?
You use curl/libcurl on which platforms?
If you use curl on Windows, which Windows versions?
Select the ones you use curl on (if any)
Do you typically build curl/libcurl yourself?
If you use more than one approach, check the ones that apply for you!
Tell us which libcurl features you use?
Select all the ones you've used recently (the last year)
Which SSL backends do you typically use?
How many years have you been using curl?
Select the channels you are subscribed to or participate in:
How do you access libcurl?
There are numerous, tell us how you use libcurl!
What kind of person are you?
Where do you live?
Did you answer this survey last year?
To help us understand survey response changes and more!
How have you contributed to the curl project?
Are you involved in other open source projects?
What are the primary reasons you haven't contributed or don't contribute more to the project?
Mark all you think fit!
What could the curl project do/change to get (more) contributions from you?
Your answer
How good is the project and its members to handle...
If you don't have an opinion, just move on to the next section...
Patches and pull-requests
Really bad
Really good
Bug reports
response times, polite responses, accurate fixes - the total impression you have
Really bad
Really good
Female contributors and other minorities
Really bad
Really good
Attribution and giving credits
Really bad
Really good
Helping newcomers to the project
Really bad
Really good
Information about what's going on
Really bad
Really good
Handling security-related issues
Really bad
Really good
Pick the best and the worst
Which are the curl project’s best areas?
You can select up to 5 good areas
Which are the curl project’s worst areas?
You can select up to 5 bad areas
Competition
If you couldn't use libcurl, what would be your preferred alternative?
libcurl's primary competitors for your use case
Future!
If you miss support for something, tell us what!
If you miss support for something, tell us what!
- something you want or need or miss
Your answer
What feature/bug would you like to see the project REMOVE?
- something you think doesn't belong in there
Your answer
Which of these API(s) would you use if they existed?
If it was provided by the curl project and it worked in a way you'd agree with
Should curl join an umbrella project?
To safeguard code and ensure its future. Like GNU, Apache, Software Conservance, Sofware for Public Interest or another in similar spirit.
Do you wish to attend the next curl://up meeting/conference?
We know there can be many obstacles, but this question is about intent and wish. What would you like?
Should libcurl get rewritten in another language?
What should "curl 8.0" be?
Which question would you like to see in this survey next year?
Your answer
Submit
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Additional Terms