POST: community news aug 2024 #460
Conversation
|
pre-commit.ci autofix |
|
pre-commit.ci autofix |
There was a problem hiding this comment.
This looks great @kierisi . i'd throw in a few images where you can. if we've used the petals image before you could even copy the figure with the caption and alt text to reuse but also spruce up the page visually. and you could also link to our sprints blog post that was just merged and the scipy post too!
IDEA: just a thought. in the future we could periodically highlight a community contributor like Filipe in posts like you did for the editor teams. this just occured to me and is not related to this pr i just wanted to share the idea. i love highlighting Felipe here as it really brings attention to the people behind / driving pyOpenSci 's awesomeness!
this can be merged once you are happy with it. i'm happy with it.
|
|
||
| ## <i class="fa-solid fa-egg"></i> Hello, Hatch! | ||
|
|
||
| Education is one of the [three petals of pyOpenSci](https://www.pyopensci.org/blog/pyos-education-announcement.html), and to that end we strive to create resources that help learners navigate the Python packaging ecosystem with ease. This means that when we find our community members and scientists encountering consistent issues with trying to make their workflows more open and reproducible, or trying to build a Python package, we look for ways to lower (or ideally remove!) the barrier for learners. And this was exactly the scenario we were faced with in our beginner-friendly packaging tutorials. We decided that Hatch is a great user-friendly tool that scientists can use to package and share their code. However, in developing and teaching our [Get to know Hatch tutorial](https://www.pyopensci.org/python-package-guide/tutorials/get-to-know-hatch.html), we found scientists struggling to install a tool called [`pipx`](https://github.com/pypa/pipx) that can be used to install Hatch globally, rather than in a Python environment. This was causing a host of problems (in large part because `pipx` can be tricky to install on Windows machines!) |
|
|
||
| ## <i class="fa-solid fa-earth-americas"></i> Coming soon: a Spanish translation of the pyOpenSci Python Package Guide | ||
|
|
||
| This past May, during our [PyCon US sprints](https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html), pyOpenSci community member [Felipe Moreno](https://github.com/flpm) submitted [an issue to our Python Package Guide GitHub repository](https://github.com/pyOpenSci/python-package-guide/issues/287), asking if we had considered translating the guide to Spanish. Felipe is an experienced security engineering manager with a strong background in Python software development, data science and user-centered design, who leads the Security Data Science team at [Bloomberg LP](https://www.bloomberg.com/company/). Felipe has worked with other projects, setting up infrastructure support through [Sphinx](https://www.sphinx-doc.org/en/master/) for this kind of work. We were, of course, immediately thrilled with the idea, and took Felipe up on the offer! From there, Felipe built a PR that created a [translation guide for contributors](https://github.com/pyOpenSci/python-package-guide/pull/304), along with another PR that [provides internationalization support](https://github.com/pyOpenSci/python-package-guide/pull/298). |
|
|
||
| This past May, during our [PyCon US sprints](https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html), pyOpenSci community member [Felipe Moreno](https://github.com/flpm) submitted [an issue to our Python Package Guide GitHub repository](https://github.com/pyOpenSci/python-package-guide/issues/287), asking if we had considered translating the guide to Spanish. Felipe is an experienced security engineering manager with a strong background in Python software development, data science and user-centered design, who leads the Security Data Science team at [Bloomberg LP](https://www.bloomberg.com/company/). Felipe has worked with other projects, setting up infrastructure support through [Sphinx](https://www.sphinx-doc.org/en/master/) for this kind of work. We were, of course, immediately thrilled with the idea, and took Felipe up on the offer! From there, Felipe built a PR that created a [translation guide for contributors](https://github.com/pyOpenSci/python-package-guide/pull/304), along with another PR that [provides internationalization support](https://github.com/pyOpenSci/python-package-guide/pull/298). | ||
|
|
||
| Following Felipe’s initial efforts, several of our SciPy sprint attendees continued to work on translation of the pyOpenSci Python Packaging Guide, and you can see their progress in the [guide repository on GitHub](https://github.com/pyOpenSci/python-package-guide/issues?q=is%3Aopen+is%3Aissue+label%3Ascipy-24). This has resulted in 13 PRs to our packaging guide. Our next steps are to create an editorial team composed of members who are fluent in Spanish/native speakers. This team will be responsible for reviewing and merging these contributions. Stay tuned for updates on this incredible community-driven project! |
There was a problem hiding this comment.
@kierisi i've always thought about doing breakout setnences. i've read this in blog posts where this is a paragraph - and then the writer pulls a sentence or two out and restates it in larger text. do you know what i am talking about? We could do this here. something like
Filipe's efforts have yielded 13 translation pull requests to our packaging guide
if you don't know what i'm talking about because i'm explaining it poorly i can try to find a screen shot. but i see it in blog posts a lot.
There was a problem hiding this comment.
I know exactly what you mean! I've heard them referred to as pull quotes, and can start incorporating them.
|
|
||
| ## <i class="fa-solid fa-rainbow"></i> All the credit for our contributors | ||
|
|
||
| We have been absolutely floored by the community involvement with pyOpenSci over the last few months, and wanted to take a moment to recognize everyone who has been a part of our sprints at both [PyCon US](https://us.pycon.org/2024/) and [SciPy](https://www.scipy2024.scipy.org/)! In total we’ve had over 30 contributors submit 65 issues to six different pyOpenSci repos between the two events, which is incredible. |
There was a problem hiding this comment.
Wow 30 contributors is really amazing! this also could be a call out sentence!
correction to participant name (Bradon, not Brandon)
Co-authored-by: Leah Wasser <leah@pyopensci.org>
Co-authored-by: Leah Wasser <leah@pyopensci.org>
Co-authored-by: Leah Wasser <leah@pyopensci.org>
Co-authored-by: Leah Wasser <leah@pyopensci.org>
Co-authored-by: Leah Wasser <leah@pyopensci.org>
This is a draft version of the August Community News newsletter, which covers:
Everything rendered locally without issues, but I'll be sure to double-check the PR as well.