[DIPY] Comments about issues raised in the Sept 10th dev meeting
Hi, a few comments following yesterday's dev meeting. As for the GitHub CI, I was curious. I guess this is what Ariel mentioned: https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/ The YAML mechanism seems very similar to the Microsoft Azure Pipelines. The page says it is free for open source projects: https://github.com/features/actions Looks promising. As said, ITK moved to Azure Pipelines a while ago and they are very happy with it. On the new website, I ignore whether you finally kept the suggestion, but making all tutorials be folded/unfolded with a button seems very useful to me. As for the support channels, until recently I was not aware that there was a DIPY mailing list separate from the neurostars mailing list/forum. DIPY has also a gitter room. I'd dare to say that having a centralized channel for questions (although these days GitHub issues are also used to post questions, same may happen in twitter, etc.) would ease things for both users ans maintainers, since "everything" would be kept in the same site, and searchable. IMHO, discourse (a DIPY-own, separate from neurostars) is a very nice option for this. BTW, the new DIPY website looks stunning. Excellent job ! Cheers, JON HAITZ
Hi Jon, Thanks for following up on this discussion. Just to add that I chatted about this briefly with Stefan van der Walt and he mentioned that scikit image has moved to Azure pipelines, as have numpy and scipy, and so far they are very happy with the move. Importantly, you can get all three platforms going on AP, which seems like a big advantage. That said, with GitHub starting their own CI service, there's a bit of uncertainty about how things will play out in the long run. From a small experiment I did, it seems that GitHub's service is not ready for prime time. It is still in beta. Cheers, Ariel On Wed, Sep 11, 2019 at 10:22 PM Jon Haitz Legarreta Gorroño < jon.haitz.legarreta@gmail.com> wrote:
Hi all, Agree with all of you. We switched to Azure on FURY ( https://github.com/fury-gl/fury) and we are very happy. I think we should do this move for Windows and OSX and keep Travis or CircleCI for Linux. I do not recommend to put all our build on the same CI tool, we never know... I will start to look at that for DIPY this month. Serge K. On Sun, Sep 15, 2019 at 4:14 AM Ariel Rokem <arokem@gmail.com> wrote:
Hi, thanks for the updates both and for having tried GitHub CI Ariel ! Interesting. As for the argument of keeping Linux builds in Travis/CircleCI, IMHO, having all three builds in the same platform would ease the task of checking the build failures for developers. One gets the same user experience, and this makes it easier to follow the flow. If at some point, for whatever reason, Azure pipelines changes its policies and does not match the needs of DIPY, I guess we can roll back to CircleCI, Travis or AppVeyor without being penalized, or switch to GitHub CI if it proves to be a better option. But I may be missing some piece of information when saying this. Cheers, JON HAITZ On Sat, Sep 14, 2019 at 10:34 PM Serge K. <skab12@gmail.com> wrote:
Hi Jon, Thanks for following up on this discussion. Just to add that I chatted about this briefly with Stefan van der Walt and he mentioned that scikit image has moved to Azure pipelines, as have numpy and scipy, and so far they are very happy with the move. Importantly, you can get all three platforms going on AP, which seems like a big advantage. That said, with GitHub starting their own CI service, there's a bit of uncertainty about how things will play out in the long run. From a small experiment I did, it seems that GitHub's service is not ready for prime time. It is still in beta. Cheers, Ariel On Wed, Sep 11, 2019 at 10:22 PM Jon Haitz Legarreta Gorroño < jon.haitz.legarreta@gmail.com> wrote:
Hi all, Agree with all of you. We switched to Azure on FURY ( https://github.com/fury-gl/fury) and we are very happy. I think we should do this move for Windows and OSX and keep Travis or CircleCI for Linux. I do not recommend to put all our build on the same CI tool, we never know... I will start to look at that for DIPY this month. Serge K. On Sun, Sep 15, 2019 at 4:14 AM Ariel Rokem <arokem@gmail.com> wrote:
Hi, thanks for the updates both and for having tried GitHub CI Ariel ! Interesting. As for the argument of keeping Linux builds in Travis/CircleCI, IMHO, having all three builds in the same platform would ease the task of checking the build failures for developers. One gets the same user experience, and this makes it easier to follow the flow. If at some point, for whatever reason, Azure pipelines changes its policies and does not match the needs of DIPY, I guess we can roll back to CircleCI, Travis or AppVeyor without being penalized, or switch to GitHub CI if it proves to be a better option. But I may be missing some piece of information when saying this. Cheers, JON HAITZ On Sat, Sep 14, 2019 at 10:34 PM Serge K. <skab12@gmail.com> wrote:
participants (3)
-
Ariel Rokem -
Jon Haitz Legarreta Gorroño -
Serge K.