[Starlingx-discuss] Contributor Survey

[Seiler, Glenn]

Ildiko, team
I think there are logical steps in the progression of someone using a project like StarlingX.
First is just to download it, (or build it) and try to run some sample VMs or containers.
Second would be to start a PoC or evaluation and maybe contribute to the project.
Only after the first two steps would anyone start to consider deployment.

So I think asking about deployment will not get us where we want to be.
I think we focus on the first step, almost exclusively. 
- do they even know about StarlingX!!
-have they downloaded it? Do they plan to?
-have they had any problems...
-what can we do to make it easier for them...

I think that is step 1.

We can agree to skip that step and go straight to what they want to deploy on the edge, but those are really two very different surveys.
If we want to focus on what they deploy at the edge, we have to acknowledge they very well may not even be deploying StarlingX....after all it is still very young and companies can take many months or years before they deploy.

-glenn


-----Original Message-----
From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] 
Sent: Wednesday, February 20, 2019 11:26 AM
To: Zvonar, Bill
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Contributor Survey

Hi Bill,

Thank you for adding the contributor focused questions.

On the today’s call we’ve discussed the base idea being to have a high level user survey type of questionnaire that focuses on understanding the use case and motivation for companies who are planning to deploy or use an edge platform and ask their plans and current stage with StarlingX. Our motivation is to start building and growing the ecosystem around StarlingX and understand the market a little better as well.

When it comes to contributions we listed two options. We can either add a question or two to the above initial survey to see if a certain responder is also interested in contributing or we can run it as a separate survey.

If we can make it happen on the tooling side we could also consider showing deeper dive questions if someone says they are interested in contributing and not displaying those questions if that’s not a primary interest for them at this point.

In my view if we run a contribution focused survey we need to set the scope and decide what challenges we would like to get an answer to when we put together the questions. Like whether we would like to find roadblocks or bottlenecks that make it harder for people to join or learn which area they are interested in and if the latter what the next step is once we have the results and whether the survey is the best way to reach out to new contributors who are just getting started to help them.

What do others think or would be interested in learning about?

If you would like to participate in drafting the survey(s) please check out the etherpad and add comments and ideas!

Thanks,
Ildikó


> On 2019. Feb 20., at 18:50, Zvonar, Bill <Bill.Zvonar at windriver.com> wrote:
> 
> Hi Ildiko,
>  
> As discussed in the Community Marketing Planning call today, I’ve placed a draft of a Contributor Survey up on [0].
>  
> It’s not quite the same as the survey you started, it’s more directed at individuals who have already expressed an interest in contributing – a survey like this will help them understand how & where they can do so.
>  
> It’s a draft – comments welcome from the community.
>  
> Bill… 
>  
> [0] https://etherpad.openstack.org/p/stx-user-survey
>  
>  
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss