Strategy for engaging implementers

[Relequestual]

Problem: Implementations not updating support for newer versions of JSON Schema. Engaging implementers and encouraging updated implementations would be of benefit to the ecosystem. Opening a two way line of communication with implementers will hopefully result in increasing their involvement with the community at large, and increase participation in new activities in the JSON Schema org.

@benjagm to define define success criteria, deliverables, and breakdown of tasks.

Notes on deliverables:

@Relequestual:

• Create a basic badging system for implementations to identify as a JSON Schema related implementation
• Update badging system to include draft/version support information (inc link to Bowtie)
• Define a JSON Schema for structured self reporting of the implementation, their supported versions, and supported features/interfaces. Related to Identify a list of critical interfaces that implementations should have and empower implementers with better resources #408
• Raise Issues for top few implementations in each language to suggest self reporting
• On the new website, identify implementations which self identify/self report
• On the new website, identify implementations which are on Bowtie (and their compliance)
• Raise Issues on remaining known implementations to encourage self reporting
• Automate creating website PRs for self reporting implementations

General

• We could provide token financial support to implementers who are maintaining their implementation
• Suggest implementations add Repo Status and Project Type badges (which we can then use on the website and ecosystem diagram later)

Assessed as high impact/medium effort during our collaborators summit 2023.

Scope

The scope of this project includes:

• Identify the implementers we are targeting. This include contact details.
• Create a survey targeting the implementers to understand their pain points, concerns and needs.
• Create a plan to maximize the survey response and the implementers interested on joining.
• With the data captured, define a Minimum Viable Maintainers Program whose benefits are intended to mitigate some or most of the pain points captured in the survey.
• Update the website with the program benefits, how to apply and current members.
• Create a badging system.
• Create a system for self-reporting.
• Create a communications campaign to praise new members and promote network effect.

Objectives

The objectives of this project are:

• Strengthening the relationships with JSON Schema implementers.
• Support implementers.
• Generate trust in the industry by presenting JSON Schema as an Ecosystem.
• By improving the relationship with implementers we hope to increase the TSC members and the Spec contributors.
• Increase the Community engagement.

Plan

• Research
  • Identify the implementers capturing: contact details, and implementations details. #436
  • Define a survey for implementers to understand their pain points, concerns and needs. #451
  • Create a plan to promote and maximize the survey response. This include curated personal communications and avoid automatic/massive messages.
• Program Design
  With the data, design a Minimum Viable Maintainers Program with clear benefits to help implementers.
  • Use md in the Community repo with the details of the program.
  • Create a form to apply.
  • Define application criteria, benefits and responsibilities.
  • Define a gamification system to communicate and reward implementers.
  • Define a communication plan to actively engage and communicate with implementers.
  • Create the branding of the program.
  • Update the website with the program benefits, how to apply and current members.
  • Financial support to members of the program.
  • Bounty : https://prettier.io/blog/2023/11/27/20k-bounty-was-claimed
• Badging system
  • Create a basic badging system for implementations to identify as a JSON Schema related implementation
  • Update badging system to include draft/version support information (inc link to Bowtie)
  • On the new website, identify implementations which self identify/self report
  • On the new website, identify implementations which are on Bowtie (and their compliance)
• Self-reporting System
• Comms Plan
  Create a communications campaign to praise new members and promote network effect.
  • Templates to celebrate new members.
  • Messages to encourage applications.

Success Metrics

The metrics for measuring the success of the documentation project includes:

• +##% YoY Social media growth.
• New members in the TSC.
• New Spec contributors.
• +##% YoY Community Engagement Metrics.
• +##% YoY JSON Schema adopters.
• Increase adoption of the current spec version by existing tooling

Risks

The risks associated with this project includes:

• Low number of applications.
• Negative perception of the community if we send automatic communications. We should send individual/personal messages.
• Defining a program with benefits that implementers don't need. This is why the survey is critical.

[benjagm]

As peer the last OCWM #429:
@benjagm to modify the plan to add gamification and proactive engagement with implementers.

[benjagm]

@benjagm to modify the plan to add gamification and proactive engagement with implementers.

I have modified the Program design section to add action items to cover these aspects.