Re a Pants user survey, I wrote a very rough draft...
# development
f
Re a Pants user survey, I wrote a very rough draft here. I welcome any feedback and other comments. Will also discuss general next steps at today's Pants Team Meeting.
👍 1
🙏 2
And if any one wants to help me out with developing the survey, please let me know!
and it probably needs questions on the user's familiarity with Bazel and other build orchestration systems
👍 1
w
I'm counting something like 43 questions so far - based on previous surveys (and surveys in general), the rate at which people answer questions drops dramatically the longer the survey. I don't know the survey mechanism itself, but I think it would be good to see this split into the top 3 most important, hard-hitting questions - and then a set of questions for those users who will continue and fill out a long survey regardless. I'm reading through for places we can trim down the selections right now (e.g. joining JVM languages). it's less granular, but I feel it's more approachable 🤷
f
Yeah I wasn’t sure how pants-specific it should be, but it seemed like a question on experience with such systems in general could be useful for context, but as mentioned there’s already quite a few questions
w
I love the question though, it's important given how many other build orchestration tools there are - I just found a couple more recently
👍 2
f
I'm counting something like 43 questions so far - based on previous surveys (and surveys in general), the rate at which people answer questions drops dramatically the longer the survey.
Yup, this is definitely a rough draft to get the ideas out for collaborative discussion. Part of the work to come (which would love help with) is editing this down to ask just what we need to actually ask for a useful survey.
w
👍 Working on it 🙂
All as suggestions though, as I want to keep the context tracked
f
🙂
c
I took a stab at suggestions for trying to make it shorter. I think sections around community/IC-contributing and corporate dollars could be longer. ex: • How have you interacted with the pants community (slack, github issues, PRs etc) • Free form ^^ how did it go? • What did you find challenging about contirbuting code to pants? • What would help you contribute code to pants? Something about ways of financial contributing: • sponsorship vs per hour consulting for bug fixes vs retainer support vs pooled funds for sponsored projects (like a per Big Feature kickstarter? https://klarasystems.com/ tries to do something like this)
b
Thanks for starting this. I've made some comments/suggestions through the document and then had the hubris to write a "Huon's thoughts" section at the end: https://docs.google.com/document/d/1Qea3w2VhD_GT8KEaAf1p2iiZ5aiLszewqn4UsEGqhGY/edit#heading=h.898b1cxtix6i