Identify the repositories inside and outside the organization.

[benjagm]

This issue is part of 2023-24 Roadmap Issue to refine the contributor journey #410.

The objective is to identify the repositories inside and outside the organization and the contribution status so we can asses the JSON Schema Github org Contributor Journey.

The list of repositories to consider for the exercise will be:

• https://github.com/json-schema-org/website
  • POC: @benjagm
  • Contribution Status: Active
  • Contribution Needs: Front-end contributors, case studies and blog posts.
• https://github.com/json-schema-org/JSON-Schema-Test-Suite
  • POC: @Julian
  • Contribution Status: Active
  • Contribution Needs: Code reviews
• https://github.com/json-schema-org/community
  • POC: @benjagm
  • Contribution Status: Active
  • Contribution Needs: Community builders people to join the CoC Committee
• https://github.com/json-schema-org/.github
  • POC: @benjagm
  • Contribution Status: Active
• https://github.com/json-schema-org/json-schema-spec
  • POC: Core Team
  • Contribution Status: Active
  • Contribution Needs: Spec contributions
• https://github.com/json-schema-org/brand
  • POC: @benjagm
  • Contribution Status: Active
• https://github.com/json-schema-org/json-schema-vocabularies
  • POC: @gregsdennis
  • Contribution Status: Active
  • Contribution Needs: Identifying and listing more known vocabularies
• https://github.com/json-schema-org/json-schema-linting
  • POC: @gregsdennis
  • Contribution Status: In development
  • Contribution Needs:
• https://github.com/json-schema-org/referencing
  • POC:
  • Contribution Status: Inactive
  • Contribution Needs: N/A
• https://github.com/json-schema-org/json-hyperschema-spec
  • POC: @jdesrosiers
  • Contribution Status: Inactive
  • Contribution Needs: N/A
• https://github.com/json-schema-org/vocab-database
  • POC:
  • Contribution Status: Inactive
  • Contribution Needs:
• https://github.com/json-schema-org/vocab-idl
  • POC: @gregsdennis
  • Contribution Status: In development
  • Contribution Needs:
• https://github.com/bowtie-json-schema
  • POC: @Julian
  • Contribution Status: Active
  • Contribution Needs:

[Julian]

I don't think I see a ton of open issues on the test suite repo which require Python code contributions -- though they indeed exist (e.g. adding a sanity check to ensure IDs are unique globally across the suite, which is json-schema-org/JSON-Schema-Test-Suite#423).

But if I were to summarize the biggest need at the minute, I suspect given we still have 10+ PRs open, it's "review open PRs and get them ready to merge" for that repo.

[benjagm]

What about referencing and vocab-database repositories? @Relequestual

[Relequestual]

What about referencing and vocab-database repositories? @Relequestual

I would say it's inactive.
It has an open PR: json-schema-org/vocab-database#4

We (I) really didn't have time to properly hand hold them through what our (my) expectations would be for running such a project. It feels like they mostly made something, put it up for comments, but weren't interested in collaborativly building something from the ground up (which takes much longer).

Before we accept another similar project, we should think more carefully about the requirements to get started, the expected way of working, and expected outputs.

[benjagm]

Thanks you all! This is super helpful.

[benjagm]

Closed as completed. Huge thanks everyone!