BLOG: get involved with pyOpenSci #403
Conversation
There was a problem hiding this comment.
This is great Jesse. I left some feedback, questions and comments. i don't actually need to read this again unless you want me to! i'm going to approve. i suspect however once you add more comments i might have to "approve" again. as lately i've been noticing that with github. just ping me if that is the case! or if you have questions
| comments: true | ||
| --- | ||
| ## <i class="fa-regular fa-heart"></i> The pyOpenSci mission | ||
| Founded in 2018 by our Executive Director, [Leah Wasser](https://github.com/lwasser), pyOpenSci builds diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. While a diverse, inclusive community is at our core, radiating out from it are the three petals–how we accomplish our community goals–of pyOpenSci. These are: |
There was a problem hiding this comment.
I love this. i've been playing with a bit more powerful language around pyOpenSci supports scientists in tackling the world's greatest challenges by helping them make their science more open and collaborative. ... and then we do this by ... building diverse community and technical skills...
| 2. [Community partnerships](https://www.pyopensci.org/partners.html) | ||
| 3. [Training and open educational resources](https://www.pyopensci.org/blog/pyos-education-announcement.html) | ||
|
|
||
| A great primer for all things pyOpenSci is our [pyOpenSci lightning talk template [currently WIP]](https://docs.google.com/presentation/d/1205l8y75SI9spdklKnxDZzwwjArHvpeIpwFGZOvVLjc/edit?usp=sharing). |
There was a problem hiding this comment.
i really like the slide deck but i think we should talk about it. i can provide feedback separately in the asana task. what i'd do for now is turn this into an html comment and then we can uncomment when it's ready!
There was a problem hiding this comment.
sounds good - I'll delete it from this version!
| ## <i class="fa-solid fa-bullhorn"></i> Promote pyOpenSci online and in-person | ||
| pyOpenSci is active on both [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci), and you’re welcome to tag us on social media, as well as to [reach out with questions](mailto:media@pyopensci.org)! We also have [a series of brand assets and guidelines](https://docs.google.com/presentation/d/1glwf3BEPxo5H6pOHp6d55r2sbw8x-8kQZ9GzoLXwEDc/edit?usp=drive_link) if you need a copy of our logo, information on our fonts, and/or access to various illustrations we use. | ||
|
|
||
| Dependent on timing, cost, and location, we’d also be more than happy to send you a set of pyOpenSci stickers to share! Please reach out to [media@pyopensci.org](mailto:media@pyopensci.org) to inquire about your event. |
There was a problem hiding this comment.
maybe be more specific. Are you going to a large, recognized Python meeting that pyOpenSci can't attend and you want to support us there? Please reach out...
just to avoid the ... anyone going anywhere asking for stickers - we want to focus on the bigger meetings i think right now because we can't afford too much!
There was a problem hiding this comment.
makes sense! updated!
|
|
||
| Dependent on timing, cost, and location, we’d also be more than happy to send you a set of pyOpenSci stickers to share! Please reach out to [media@pyopensci.org](mailto:media@pyopensci.org) to inquire about your event. | ||
|
|
||
| Please feel free to use any information from [our website](https://www.pyopensci.org/) and our [pyOpenSci lightning talk template [currently WIP]](https://docs.google.com/presentation/d/1205l8y75SI9spdklKnxDZzwwjArHvpeIpwFGZOvVLjc/edit?usp=sharing), to share about the work pyOpenSci is doing. And don’t forget to share your personal experiences with pyOpenSci as well! |
There was a problem hiding this comment.
how about something like... are ou going to a python meeting and want to give a lightning talk about pyOpenSci?... we can help... you can use any of the graphics or slides from this slide deck...
but i think we need to make changes before people can use that deck
There was a problem hiding this comment.
agreed - I'm going to pull the talk template, and add in that they can reach out on socials or email us.
| Please feel free to use any information from [our website](https://www.pyopensci.org/) and our [pyOpenSci lightning talk template [currently WIP]](https://docs.google.com/presentation/d/1205l8y75SI9spdklKnxDZzwwjArHvpeIpwFGZOvVLjc/edit?usp=sharing), to share about the work pyOpenSci is doing. And don’t forget to share your personal experiences with pyOpenSci as well! | ||
|
|
||
| ## <i class="fa-solid fa-handshake-angle"></i> Volunteer with pyOpenSci | ||
| If you're looking to be more hands-on with pyOpenSci, consider joining our Review Team or Editorial Board, digging into some code and working from our Help Wanted board, or writing a guest blog post! |
There was a problem hiding this comment.
link to editor guide and reviewer guide?
| To join our review team, [fill out our reviewer form](https://docs.google.com/forms/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform). We will contact you if we have a package that we need reviewers for. It’s OK if you’ve never reviewed a package before! We’ll walk you through it. | ||
|
|
||
| ### pyOpenSci's Editorial Team | ||
| The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks: |
There was a problem hiding this comment.
maybe link tot he editor guide here instead? i just think a link (that rhymed 😆 ) is important to our guidebooks here!
you can also link to the editorial board listing on the website if people want to see who's already on the board.
|
|
||
| It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas! | ||
|
|
||
| ### Apply to be a pyOpenSci editor |
There was a problem hiding this comment.
question - this is great. i am not sure if this is a valid concern. we don't want people signing up all of the time... it's only right now that we need editors. what happens otherwise is peope llose interest and we waist time reaching out to them in say 3 months if you know what i mean? can we provide a time cap like through june or july or something?
|
|
||
| If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org). | ||
|
|
||
| ### pyOpenSci's GitHub Help Wanted board |
There was a problem hiding this comment.
| ### pyOpenSci's GitHub Help Wanted board | |
| ### Contribute to pyOpenSci |
| If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org). | ||
|
|
||
| ### pyOpenSci's GitHub Help Wanted board | ||
| pyOpenSci maintains a [GitHub Help Wanted board](https://github.com/orgs/pyOpenSci/projects/3) filled with a wide variety of issues, ranging from highly technical to beginner-friendly. The status column makes it easy to identify the issue category, and the label column helps to further clarify any needs around the issue. |
There was a problem hiding this comment.
The message here should be. more like - do you want to contribute to an open source project that is supporting other open science projects? we need your help!
check out our help-wanted board where we ....
all contribtors get added to our website
| pyOpenSci maintains a [GitHub Help Wanted board](https://github.com/orgs/pyOpenSci/projects/3) filled with a wide variety of issues, ranging from highly technical to beginner-friendly. The status column makes it easy to identify the issue category, and the label column helps to further clarify any needs around the issue. | ||
|
|
||
| ### Write a guest blog post for pyOpenSci | ||
| We are always looking for guest bloggers on [the pyOpenSci blog](https://www.pyopensci.org/blog/index.html)! If you’d like to write about a pyOpenSci package, your experiences with pyOpenSci, or how you’re using free and open Python tools in your scientific endeavors, we’d love to hear from you! Email our Community team at [media@pyopensci.org](mailto:media@pyopensci.org) for more information. |
There was a problem hiding this comment.
| We are always looking for guest bloggers on [the pyOpenSci blog](https://www.pyopensci.org/blog/index.html)! If you’d like to write about a pyOpenSci package, your experiences with pyOpenSci, or how you’re using free and open Python tools in your scientific endeavors, we’d love to hear from you! Email our Community team at [media@pyopensci.org](mailto:media@pyopensci.org) for more information. | |
| We are always looking for guest bloggers on [the pyOpenSci blog](https://www.pyopensci.org/blog/index.html)! If you’d like to write about a pyOpenSci package that has been accepted into our ecosystem, your experiences with pyOpenSci, or how you’re using free and open Python tools in your scientific endeavors, we’d love to hear from you! Email our Community team at [media@pyopensci.org](mailto:media@pyopensci.org) for more information. |
There was a problem hiding this comment.
we don't want people to write blog posts about random packages because it might feel like we're endorsing packages that we haven't reviewed yet. but otherwise this is wonderful.
|
oh also @kierisi if you rebase against main these pr's should start passing CI. let me know if you have questions. |
|
@lwasser looks like I'm good to go ahead with the merge! thanks for the quick turnaround on this! |
blog post with details on getting involved with pyOpenSci. two things of note: