JEP document #4
Closed
JEP document #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@yuvipanda @Zsailer - Hoping you guys can take a look especially. |
|
@jaipreet-s Wow! This is fantastic! Thank you for initiating this. I'll review this first thing tomorrow and get back to you with comments. |
|
|
|
Since we've merged this in jupyter/telemetry#1, I'm closing this PR here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi all,
In the interest of working backwards from the JEP process, I've started the final JEP proposal documentation This encapsulates the design and discussions done here and offline.
I've attempted to layout the components of the telemetry system and each of their sub-components
A few sections are TBD and still work-in-progress. I am hoping someone who is more familiar with JupyterHub can pick up the that section.