dropping support for Gitpod and our Docker image builds
Hi all, We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml). Since it's a cron job that doesn't show up on PRs, but I get the notifications. Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff. Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r... https://hub.docker.com/u/numpy We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code ( https://github.com/numpy/numpy/tree/main/.devcontainer) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134. It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/, hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env". So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy). Thoughts? Cheers, Ralf
Hi all,
We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Factions%2Fworkflows%2Fgitpod.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn)). Since it's a cron job that doesn't show up on PRs, but I get the notifications.
Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff.
Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/1?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Ftree%2Fmain%2Ftools%2Fgitpod&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/2?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2F.github%2Fworkflows%2Fdocker.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/3?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2F.github%2Fworkflows%2Fgitpod.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r... (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/4?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2Fdoc%2Fsource%2Fdev%2Fdevelopment_gitpod.rst&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) https://hub.docker.com/u/numpy (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/5?redirect=https%3A%2F%2Fhub.docker.com%2Fu%2Fnumpy&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn)
We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code (https://github.com/numpy/numpy/tree/main/.devcontainer (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/6?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Ftree%2Fmain%2F.devcontainer&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn)) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134 (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/7?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fissues%2F23134&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn). It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but
I'm in favor of dropping Gitpod, IMO during sprints as well, it yielded less utility than expected initially, and breaks far too often (as summarized above). It would also be good to be free from docker rot given their recent changes. --- Rohit On Mar 20 2023, at 9:09 pm, Ralf Gommers <ralf.gommers@gmail.com> wrote: they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/ (https://link.getmailspring.com/link/26A16109-F730-429D-B189-C4597C5AF7E4@getmailspring.com/8?redirect=https%3A%2F%2Fgithub.com%2Fcodespaces%2F&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn), hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env".
So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy).
Thoughts?
Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: rgoswami@quansight.com
On Mon, Mar 20, 2023 at 3:13 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
Hi all,
We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml). Since it's a cron job that doesn't show up on PRs, but I get the notifications.
Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff.
Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml
https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r... https://hub.docker.com/u/numpy
We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code ( https://github.com/numpy/numpy/tree/main/.devcontainer) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134. It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/, hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env".
So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy).
Thoughts?
Cheers, Ralf
That's fine with me. I did run it a couple of times to see what it did and the setup time excruciating :) If removing it also reduces the maintenance burden, so much the better. Chuck
Hi, this sounds all reasonable to me, and as mostly a lurker on this list my input shouldn't carry too much weight anyway. I wanted to point out one thing: Docker does continue to offer free access for Open Source projects, it's just that they restructured the way of how to do this. So if there is still value in Docker, an application to the Docker-Sponsored Open Source tier should certainly fit Numpy. A bit more information is at https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-th... Cheers Klaus On 20/03/2023 22:09, Ralf Gommers wrote:
Hi all,
We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml <https://github.com/numpy/numpy/actions/workflows/gitpod.yml>). Since it's a cron job that doesn't show up on PRs, but I get the notifications.
Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff.
Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod <https://github.com/numpy/numpy/tree/main/tools/gitpod> https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml <https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml> https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml <https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml> https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r... <https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.rst> https://hub.docker.com/u/numpy <https://hub.docker.com/u/numpy>
We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code (https://github.com/numpy/numpy/tree/main/.devcontainer <https://github.com/numpy/numpy/tree/main/.devcontainer>) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134 <https://github.com/numpy/numpy/issues/23134>. It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/ <https://github.com/codespaces/>, hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env".
So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy).
Thoughts?
Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: klaus.zimmermann@smhi.se
Hi all, As a heavy user of Gitpod (mostly for quick fixes) I would also like to point out that you *can* still use it - it's just that the development environment won't be set up by default. I agree it has been breaking far too often and requires a lot of optimization to reach reasonable setup times, and while I haven't been using the codespaces setup I can see the gain in maintenance effort there. Cheers, Melissa On Tue, Mar 21, 2023 at 9:21 AM Klaus Zimmermann <klaus.zimmermann@smhi.se> wrote:
Hi,
this sounds all reasonable to me, and as mostly a lurker on this list my input shouldn't carry too much weight anyway.
I wanted to point out one thing: Docker does continue to offer free access for Open Source projects, it's just that they restructured the way of how to do this. So if there is still value in Docker, an application to the Docker-Sponsored Open Source tier should certainly fit Numpy. A bit more information is at
https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-th...
Cheers Klaus
On 20/03/2023 22:09, Ralf Gommers wrote:
Hi all,
We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml <https://github.com/numpy/numpy/actions/workflows/gitpod.yml>). Since it's a cron job that doesn't show up on PRs, but I get the notifications.
Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff.
Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod <https://github.com/numpy/numpy/tree/main/tools/gitpod> https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml <https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml> https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml <https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml>
https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r... < https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.r...
https://hub.docker.com/u/numpy <https://hub.docker.com/u/numpy>
We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code (https://github.com/numpy/numpy/tree/main/.devcontainer <https://github.com/numpy/numpy/tree/main/.devcontainer>) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134 <https://github.com/numpy/numpy/issues/23134>. It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/ <https://github.com/codespaces/>, hit
the
green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env".
So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy).
Thoughts?
Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: klaus.zimmermann@smhi.se
NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: melissawm@gmail.com
On Tue, Mar 21, 2023 at 12:20 PM Klaus Zimmermann <klaus.zimmermann@smhi.se> wrote:
Hi,
this sounds all reasonable to me, and as mostly a lurker on this list my input shouldn't carry too much weight anyway.
I wanted to point out one thing: Docker does continue to offer free access for Open Source projects, it's just that they restructured the way of how to do this. So if there is still value in Docker, an application to the Docker-Sponsored Open Source tier should certainly fit Numpy. A bit more information is at
https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-th...
Thanks for the suggestion Klaus. It doesn't really fit us. I've spoken to multiple maintainers of other projects who went through this application process. It's very bureaucratic, may take months, and is only meant for projects with needs a lot higher than hours (as determined by an actual interview apparently). On Twitter I've seen similar sentiments from maintainers. So I'm pretty sure it's not worth applying for that. Cheers, Ralf
On Mon, Mar 20, 2023 at 9:09 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy).
It seems everyone is happy with removing Gitpod. To close the loop on this, here is the relevant PR: https://github.com/numpy/numpy/pull/23444. Cheers, Ralf
participants (5)
-
Charles R Harris -
Klaus Zimmermann -
Melissa Mendonça -
Ralf Gommers -
Rohit Goswami