-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify the repositories inside and outside the organization. #425
Comments
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. |
What about referencing and vocab-database repositories? @Relequestual |
I would say it's inactive. 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. |
Thanks you all! This is super helpful. |
Closed as completed. Huge thanks everyone! |
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:
The text was updated successfully, but these errors were encountered: