Skip to content

User surveys #32

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
alimanfoo opened this issue May 6, 2020 · 3 comments
Open

User surveys #32

alimanfoo opened this issue May 6, 2020 · 3 comments

Comments

@alimanfoo
Copy link
Member

Issue to discuss user surveys.

@alimanfoo
Copy link
Member Author

Suggested by @Carreau.

@Carreau
Copy link

Carreau commented May 6, 2020

Thanks @alimanfoo,

This is following the community call and in particular the discussion about "SingleFile" zarr, what the usage/user base of Zarr is.

I'm suggesting to start small user survey in order to build expectation of such user survey among the Zarr Silent Majority to have a sens to send a signal, and gave them a chance to send this survey around.

Here some ideas of what question could be sent.


  • How long have you been using Zarr for

    • ( ) more than a year
    • ( ) about a year
    • ( ) a few weeks
    • ( ) what is zarr ?
  • In which Domains do you use Zarr

  • Which kind of store(s) are you primarily using.

    • Directory based
    • Single File based
    • Database Based
    • In Memory
    • Not sure
  • What is(are) you main pain points with using/not using Zarr:

    • Documentation
    • Integration with existing software, libraries.
    • Verbosity
    • Performance
    • Ease to share/get datasets
    • Collaboration with other people
    • Other
  • Misc comments (open field).

  • Enter your email to be notified about the availability of this survey results, analysis and next survey.


Rust 2019 survey , Stackoverflow developer survey

This could be used as a baseline with a survey say every 6 month or year.

We could use google forms for something that small, or ask NumFOCUS whether there is a surveymonkey or alike.

Outside of open fields which may contain sensitive informations that might need to be cleaned, I suggest/suppose the results will be an open dataset.

@Mubarraqqq
Copy link

Hi @joshmoore @MSanKeys963 can I still make a contribution to this issue?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants