-
Notifications
You must be signed in to change notification settings - Fork 65
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
[JEP] subdomain and repository for publishing schemas under jupyter.org #108
Conversation
Thanks @Zsailer. This looks great. |
Co-authored-by: Afshin Taylor Darian <git@darian.email>
cc @jupyter/software-steering-council |
+1 My vote |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @Zsailer
|
||
## Packaging | ||
|
||
As a widely-implemented standard, JSON Schema can be used to build packages, at various levels of specificity, that could be consumed by both Jupyter downstreams. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another way to distribute and ensure single source of truth is the use of git submodules. But I guess that as it is not a common pattern in Jupyter ecosystem, we should focus on distributing packages.
Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
Pinging @jupyter/software-steering-council again for any last minute comments / votes. 😃 |
+1 |
This JEP has been in voting phase for over one month. We have 10 in favor and 1 person who did not vote. This JEP is approved! 🎉 |
Congrats to @Zsailer for getting this through. |
I've also belatedly approved this, thanks everyone! |
* Add JEP for adding $schema to notebook format * wip: update from meeting * Update add-schema-to-notebook-format.md change the schema to draft2020-12 * Update URI to align with JEP #108 --------- Co-authored-by: Filip Schouwenaars <filipsch@users.noreply.github.com> Co-authored-by: Angus Hollands <goosey15@gmail.com> Co-authored-by: Tony Fast <tony.fast@gmail.com> Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
Follow up to #107
Adds a JEP proposing to create a subdomain under jupyter.org and a repository for publishing machine- and human-readable JSON Schemas provided by the core Jupyter ecosystem.
cc @bollwyvl @tonyfast
Voting from @jupyter/software-steering-council