Define a survey for implementers to understand their pain points, concerns and needs.

[benjagm]

As part of the strategy to engage implementers defined in #412, we'd like to design a Survey for implementers to understand their pain points, concerns and needs and design a program to engage with them.

Jobs to be done:

• Research similar surveys.
• Design sections and questions.
• Validate survey with early adopters.
• Build survey.

[benjagm]

Similar surveys:

• https://github.com/cncf/surveys/blob/main/maintainer/2019/maintainer-survey-questions-2019-h1.md
• 2022-open-source-software-supply-chain-survey.pdf
• 2023-open-source-maintainer-survey.pdf
• 2021_Tidelift_Maintainer_Survey_FINAL.pdf
• 2017 GitHub Open Source Survey

[benjagm]

This is the work in progress version of the Survey: Survey

The sections I am suggesting are:

• Questions to build the Implementer’s profile
• Questions to understand the types of implementations
• Questions to get to know the implementations’ engagement and governance
• Questions to get to know the Implementations’ status
• Questions to understand the implementer's challenges and pain points
• Questions to identify areas of improvement
• Questions to present opportunities

Happy to get feedback.

[gregsdennis]

Maybe we should have a brief definition of what we consider to be an "implementation." For example, I have JsonSchema.Net to provide validation/annotation functionality, but I also have as extensions to that library JsonSchema.Net.Generation and JsonSchema.Net.DataGeneration. These provide different functionality, so does that make them different implementations?

[benjagm]

Maybe we should have a brief definition of what we consider to be an "implementation"

This would be amazing. In the new website we are going to publish the glossary and it would be the perfect place for this definition.

[benjagm]

Another survey example by CHAOSS Community.
Help the CHAOSS project improve our tools and metrics.pdf
Survey_ Help the CHAOSS project improve our tools and metrics - CHAOSS.pdf

[gregsdennis]

Interestingly, the definition of an "implementation" came up again in a separate context. Here's the result: json-schema-org/json-schema-spec#1440

[benjagm]

A first draft of the implementers survey is ready to review here:

(https://docs.google.com/document/d/1gpyeJkHvnSpx0AC59XO7K91usG3TVfiEaM4mEz8pM4Y/edit?usp=sharing)

[Relequestual]

@benjagm What are the next steps/timelines for this? =]

[benjagm]

What are the next steps/timelines for this?

The whole plan is available in #412, it contain steps but it doesn't contain dates.

[github-actions]

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️

[github-actions]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the main branch has fixed it. Please, create a new issue if the issue is not fixed.