Decide on a survey administration mechanisms

[mikesol]

I have seen two approaches to administering a survey:

1. Use a service
2. Build your own

Both are viable options. Rust does (1) and Haskell does (2).

My personal preference is (1). Even if we build something in PS, from an administration standpoint, there is no guarantee that the survey page or its network calls will go through without incident. Paying for a trusted service greatly reduces the risk. Rust went with Survey Hero because of its reliability in China, and I'd be inclined to do the same. To do this, though, we'd need a company to sponsor some or all of a subscription - either monthly for the period of the survey or yearly if we can't confidently predict for how long we'll need the service.

[thomashoneyman]

I would like to use a paid service, and I'm on board with Survey Hero. I bet we can get their education pricing, despite not really fitting the bill, because we're an open-source project.

I will have to discuss this with the core team, but we do have an infrastructure budget with some surplus at the moment, and I think that paying for the infrastructure to deliver the annual PureScript survey falls under its purview; with that in mind, a month to two months of Survey Hero is easily covered by the budget especially if we get educational pricing.