Eric Charles

I see needed definitions and clarifications on the proposed features. Looking at the changes, only cellid and docid are sent, which is fine for server-side model. There should be a...

Thx @goanpeca for exploring this. So we have 2 options: 1. Use `jupyterlab/benchmarks` repo to store the artefacts with git-lfs. 1. Create and use `jupyterlab/benchmarks-data` repo to store the artefacts...

Based on @ivanov comment on https://github.com/jupyter/enhancement-proposals/pull/101#issuecomment-1608419185 and on question shared yesterday at the SSC meeting by @ibdafna I am converting my `Yes` to an `Abstain`. I am also formalising here...

How this PR relates/articulates/coordinates with https://github.com/jupyter/enhancement-proposals/pull/99 and https://github.com/jupyter/enhancement-proposals/pull/103?

> This JEP is very detailed and logical which is great, my doubt is rather on the foundation on which it applies. We don't have a well defined Markdown definition...

cell outputs and attachment are mentioned at several places, but it is not clear to me if there is an option to have a companion file to markdown to persist...

> in a followup JEP. Well, I would feel more comfortable that this important topic be handled in this JEP to make sure all bits make sense. It can make...

> how you make sure, e.g., that companion files remain available or urls remain valid when the notebook is moved around -- but these difficulties are about tools and workflows,...

> Since a Quarto qmd file is already a functional alternative representation of a notebook (converted to ipynb for execution and back to md afterwards, including output cell contents), and...

> Before you, I remember that at least one other person has proposed the same thing on Discord. Consider this comment also a +1 from me. Yes, I have been...