# Let's connect and keep the conversation going! Add a source for the formula and include if both formulae are computationally and mathematically equivalent. Add a note somewhere that we have stopped support for gitpod. Digital version reach wider audience, especially outside conferences in North America Digital version can be any size, but we can keep to rectangular size Paper version needs to fit rectangular size, hence use of panels Recognizing desire for print version is contributor factor to wanting a 'full comic experience' The value is more in documenting processes and people rather than thrilling story or camera angles Working more as a documentary movie rather than cinematic story-driven movie Need to realistically rescope to fit in other important factors eg gathering community input, representing a relatively complex topic (contributor workflow) Letting go of artist ego to fully utilize 'comic book' medium 6 characters? Hard to sustain coherent script for 6 characters Several different characters: contributor workflow would probably need at least. Zoomed out scope, eg role of maintainers or community members Zoomed in scope, eg people working together during a sprint Especially since contributor workflow has several different scopes Similar to (*kwkvHzegb0z4TzeHsuF_GQ.png) May end up with blog style: informational images with text underneath to explain in more detail Due to time constraints, may not be able to make full flowing story panel to panel Letting go making full 'comic book style' Reviews stage open for 2 weeks (late May-early June) Using Google Docs, since easier to comment on images than on Github PR on NumPy github issues through mailing list, slack and community meeting channels. Could do later, perhaps future review stage Getting more user input would be best practice: but may not fit in timeline User Persona: Could get input eg Twitter Metaphor should not core topic (contributor workflow) make more complicated Use of metaphor: to make a complicated topic friendly At Newcomer(May 4) NumPy Docs (May 8), Commmunity (May 10) Completed Gathering community input stage and 3 brainstorming sesions Now at Outlining stage for GSOD-NumPy 2023 (May 15-26) * Open up as contribution opportunity- testing with Sphinx 7 In order to prove it is working, we need to actually deploy the docs which means merging the change to `main`, so we would have to do a controlled experiment on the devdocs deployment. What is up with Sphinx 6? There is an open issue around the need to pin to sphinx 5, and breathe also requires sphinx5. As a general pattern: be aware that scipy often has improved interfaces to things that are computed "by-hand" in numpy Speak to Pamphile about adding educational materials based on his recent academic papers: Could be a Sphinx gallery for better discoverabilty A guide for common performance issue questions Monte Carlo estimation for pi - possible example Best practices for random number generators for parallelization We can use the xray dataset for the illustration Understanding NumPy striding while doing a transpose * Core problem: No free infrastructure for data like there is for source code * Future SPEC? How to host data since every project is doing it's own thing * **Action item**: Start with scikit-learn data # Follow-up from last meeting / discussions If you’d like to work on any of them, leave a comment on GitHub (below the relevant issue). Inessa: issues related to the NumPy educational content: To suggest a topic for future presentations, leave a comment in this tracking issue. Presentation topics for NumPy Newcomers’ Hour For more information, refer to the Reporting Guidelines section on. If you see violations, take a screenshot, intervene in a respectful manner, and report it to the CoC Committee via email. For now, in short, please be kind and generous towards one another. If you haven't read it yet, please take some time to do so later on as it already applies to you. Like all NumPy spaces, and everyone participating in them, this meeting will follow our (). It's important for us to have a healthy community. We want to take a moment to remind you that this meeting is meant to be welcoming and inclusive. How to contribute to the NumPy documentation: Getting started with building documentation: () - anything that is not yet ready for an issue or PR or needs a discussion Join via Zoom: (To dial in, find your local number: )
0 Comments
Leave a Reply. |