vdom currently has some incompatibilities with JupyterLab that are forcing us to remove it from the core distribution. Given that vdom has not been maintained for 3+ years, we think that the best way of doing so would be to first migrate the vdom Jupyter extension packages underneath the nteract org umbrella. That way, if vdom ever gets revived again, the vdom extension packages can also be easily revived. Without this migration, users who wish to fork/contribute would be forced to dig through the old JupyterLab git history to extract the extension source code.
A few questions:
- Are there any objections to this proposed migration?
- Can we get consensus on a repository name? I was thinking
nteract/vdom-extension.
vdomcurrently has some incompatibilities with JupyterLab that are forcing us to remove it from the core distribution. Given thatvdomhas not been maintained for 3+ years, we think that the best way of doing so would be to first migrate thevdomJupyter extension packages underneath thenteractorg umbrella. That way, ifvdomever gets revived again, thevdomextension packages can also be easily revived. Without this migration, users who wish to fork/contribute would be forced to dig through the old JupyterLab git history to extract the extension source code.A few questions:
nteract/vdom-extension.