You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
expressed interest: Shauna, Jason, Sophia, Josh (can also post to #contrib and alert CAB to see if interest there as well)
Note that there's a cross-org tech survey that went out recently, we should take a look at the questions and see if there's anything we wished they'd covered that could be included in our survey
The text was updated successfully, but these errors were encountered:
audience: one approach might be to go for a big survey with wide audience well beyond parsons, to answer bigger progressive tech and data questions, which would hopefully have the side effect of maximizing reach for the parsons questions
goals:
** to hear from people who stopped using parsons why they stopped
** to identify potential orgs that might be good sponsors (based on employees/etc who fill out the survey)
** identify and elevate common issues and problems
** get feedback about priorities (both technical, but also how much people get out of parsons parties, etc)
learn about general needs for progressive tech & data people; possibly also about general opinions on open source and alternative development approaches
** get a better sense of how tech & data
potential qs:
** Where do you work?
** Have you contributed?
** What problems have you run into when using/trying to use Parsons?
** What features do you wish Parsons had?
** Do you use Parsons as a package?
** Do you come to Parsons Parties or other community events?
** Do you use the Slack?
** What is the size of your data team?
expressed interest: Shauna, Jason, Sophia, Josh (can also post to #contrib and alert CAB to see if interest there as well)
Note that there's a cross-org tech survey that went out recently, we should take a look at the questions and see if there's anything we wished they'd covered that could be included in our survey
The text was updated successfully, but these errors were encountered: