Alternatively, as more Binder tools get built for âconnecting people with sharable, interactive, reproducible environments in the cloudâ, at what point is it worth grabbing a website like âbinderproject.orgâ for a more high-level âwhat is the binder project and what does it do?â place as opposed to documentation for a specific tool?
We should definitely do that (grab a domain for Project Binder).
I think open-with-binder fits well into the mybinder.org documentation because right now mybinder.org is the only place it will open stuff on. (That could change in the future or become configurable but right now that is all it can do)
hadnât thought of that. Only potential downside is that mybinder.org (the service) and binder the project become more associated with each other. Not sure if that is a negative, just something to ponder.
thatâs a good point - maybe this is one way to think about it: if mybinder.org (the service) ever shuts down, does that necessarily mean that âThe Binder Projectâ is now also shut down? If so, then project.mybinder.org is probably fine. If not, then perhaps worth separating the two.
We can always redirect or keep the domain even if mybinder.org the service shuts down. Iâd want to host a page informing people about that on the root domain anyway for a while to come.
Should we go ahead and set that up starting with a github repo + jekyll + netlify combination?
Letâs start with project.mybinder.org to avoid having to deal with another domain registration. We can always change and add redirects in the future, but I like not adding new things to manage.
An analogy I like to use: Python.org provides links and resources for CPython, which is technically the reference implementation of Python, not the only implementation of the language. If CPython development stopped and the world switched to PyPy, Python.org wouldnât go away. Iâd mostly treat the mybinder.org service the same way: itâs the reference implementation and can reasonably live on the official project domain. Even if we canât run the reference service anymore some time in the future, the project domain can stay the same.