-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Year 2024 #2190
Comments
And one more notable change (I made it today): I updated the Home page and generation scripts. |
Wieee @mathbunnyru!!! Congratulations on the global talent visa! Thank you for a nice writeup about the year and for all your amazing contributions! I hope to find an opportunity to meet with you in the future, London isn't so far from Uppsala/Sweden. Happy holidays @mathbunnyru! |
Thank you @consideRatio! ❤️ |
As part of my New Year gift to this repo (haha), I almost completely rewrote the script generating the wiki home page. This is how it looked before the change: https://github.com/jupyter/docker-stacks/wiki/Home/7ec293a264f0a4257b0ee40b8d66a2bea4ea6868 |
Congratulations, @mathbunnyru \o/ Happy new year to you too :) |
Thanks @yuvipanda ❤️ |
Thank you all contributors and users.
It's been a nice year for our images and the Jupyter ecosystem.
Notable changes
Sorry if I missed something, but I think these are quite notable changes that happened to our images:
tensorflow
andpytorch
notebooksstart.sh
is now an ENTRYPOINTWhat the future holds
Well, this repo is doing quite well without much interaction.
I look forward to having GitHub-hosted arm64 runners.
They should be available early next year: issue, blog
When we switch to GitHub-hosted arm64 runners, we should have less infrastructure code, faster builds, and, maybe, a bit more reliability.
Also, with more and more AI around, It's possible that users would want to have these features included with our images by default.
Few more thoughts
At this point, I think the quality of the images we produce mostly depends on the quality of the packages we use.
There are almost no manual changes that this repo needs on a regular basis - I am only updating tag examples in docs. Updating Python and Ubuntu versions is a rare thing and it's ok to have manual PRs for that.
Fun fact -
tig images/
is less than 50 commits and fits on one page (on my screen).One more thing
On a personal side, I moved to London this year and got a UK Global Talent visa.
If you have contributed to this project (or Jupyter ecosystem) or mamba, and you plan to spend some time in London, let me know, I'm always happy to have a coffee (beer and cider are also fine) 🙂
You can DM me on LinkedIn: http://linkedin.com/in/mathbunnyru/
Happy holidays 🎉
The text was updated successfully, but these errors were encountered: