<p dir="auto">Julia has kick ass features for computation.<br>
However what is the point of computing so much if the data cannot be visualized/inspected ?</p>
<p dir="auto">Current 2d plotting capabilities are nice, but no real matlab/scilab/scipy competitor would be credible without  some kind of  3d plotting.</p>
<p dir="auto">One way of going would be to "port" mayavi to Julia.<br>
<a href="http://github.enthought.com/mayavi/mayavi/auto/examples.html" rel="nofollow">http://github.enthought.com/mayavi/mayavi/auto/examples.html</a></p>
<p dir="auto">Mayavi builds on top of VTK, so the 3d system itself would not be reinvented from scratch.</p>
<p dir="auto">I think this would be relevant feature to have for release 2.0...</p>
<p dir="auto">ps: 2d or 3d plotting systems in Julia should have SVG/PDF output, so it can be used in scientific publishing...</p>
<p dir="auto">I would like to discuss moving the Julia buildbots to something more maintainable than <code class="notranslate">buildbot</code>.  It's worked well for us for many years, but the siloing of configuration into a separate repository, combined with the realtively slow pace of development as compared to many other competitors (and also the amount of cruft we've built up to get it as far as it is today) means it's time to move to something new.</p>
<p dir="auto">Anything we use must have the following features:</p>
<ul dir="auto">
<li>
<p dir="auto">Multi-platform; it <em>must</em> support runners on all platforms Julia itself is built on.  This encompasses:</p>
<ul dir="auto">
<li>Linux: <code class="notranslate">x86_64</code> (<code class="notranslate">glibc</code> and <code class="notranslate">musl</code>), <code class="notranslate">i686</code>, <code class="notranslate">armv7l</code>, <code class="notranslate">aarch64</code>, <code class="notranslate">ppc64le</code></li>
<li>Windows: <code class="notranslate">x86_64</code>, <code class="notranslate">i686</code></li>
<li>MacOS: <code class="notranslate">x86_64</code>, <code class="notranslate">aarch64</code></li>
<li>FreeBSD: <code class="notranslate">x86_64</code></li>
</ul>
</li>
<li>
<p dir="auto">I would like the build configuration to live in an easily-modifiable format, such as a <code class="notranslate">.yml</code> file in the Julia repository.  It's nice if we can test out different configurations just by making a PR against a repository somewhere.</p>
</li>
</ul>
<p dir="auto">Possible options include:</p>
<ul dir="auto">
<li>
<p dir="auto"><a href="https://docs.gitlab.com/ee/ci/" rel="nofollow">GitLab CI</a> (Note: currently missing <a href="https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/1344" rel="nofollow">linux ppc64le support</a>)</p>
</li>
<li>
<p dir="auto"><a href="https://buildkite.com/" rel="nofollow">buildkite</a></p>
</li>
<li>
<p dir="auto"><a href="https://azure.microsoft.com/en-us/services/devops/pipelines/" rel="nofollow">Azure Pipelines</a> (Note: incomplete runner support)</p>
</li>
<li>
<p dir="auto"><a href="https://github.com/features/actions">GitHub Actions</a> (Note: incomplete runner support)</p>
</li>
</ul>
<p dir="auto">I unfortunately likely won't have time to do this all by myself, but if we could get 1-2 community members interested in learning more about CI/CD and who want to help have a hand in bringing the Julia CI story into a better age, I'll be happy to work alongside them.</p>