Add Juanita's introductory blogpost #179
Conversation
lwasser
left a comment
lwasser
left a comment
There was a problem hiding this comment.
This is so great @juanis2112 thank you!! i made some comments about making the headers a bit more descriptive for people who skim text.
I also think we should pull out a few quotes in the blog and highlight them.
i did not build this locally yet. maybe you can make the changes i requested and then i can suggest where the quotes could go once we have a final draft.
wonderful job on this!!
| overlay_color: "#DD751C" | ||
| categories: | ||
| - blog-post | ||
| - highlight |
There was a problem hiding this comment.
We will want to unhighlight another post so this one shows on the home page. i suggest the oldest of the past 3 posts - we can just remove that tag for that post
|
|
||
| ## Introduction: About Me | ||
|
|
||
| Hello, everyone! I'm Juanita, and I'm excited to share my story with you. I'm currently a computer science PhD student at UC Santa Cruz and the community manager of the Scientific Python project (which you will hear more about in a bit 👀). I’m originally from Colombia, and I completed my undergraduate studies in pure mathematics at Universidad Javeriana while also taking some music courses. I'm a passionate singer, and my favorite color is orange 🧡. I recently joined pyOpenSci as a community lead to help with community building and outreach (super excited about it!), so today I want to share my journey through my involvement in open-source scientific Python projects, which is basically how I got here. 😊 |
There was a problem hiding this comment.
let's add a link to the scientific python home page here!
| </figure> | ||
|
|
||
|
|
||
| ## Verse 2: Joining the Community |
There was a problem hiding this comment.
| ## Verse 2: Joining the Community | |
| ## Verse 2: Joining the Scientific Python Community |
just an idea - again to try to make the headings a bit more descriptive for people who will only skim your post
There was a problem hiding this comment.
Also what about a stronger word? i mean you didn't just join. you are BUILDING the community.
|
|
||
| ## Verse 2: Joining the Community | ||
|
|
||
| Later on, I took on the role of community manager for the [Scientific Python project](https://scientific-python.org), which aims to better coordinate the ecosystem and grow the community. This responsibility has allowed me to explore various avenues of engagement. From recording documentation videos and developer interviews to managing social media channels and organizing events, I have had the opportunity to contribute to the growth of this remarkable project. While I may not have been experienced in some of these areas initially ([TikTok](https://www.tiktok.com/@scientific.python), anyone? 😅 ), I have enjoyed every aspect and been driven by my firm belief in the power of community. I believe that building a strong and healthy community around the scientific Python ecosystem is just as crucial as the tools themselves. |
There was a problem hiding this comment.
The last line here - what you believe is super powerful.
I suggest that we add it as a quote in the body of the blog separately. have you seen that before? people pull out a quote and highlight it. this is the one to use:
I believe that building a strong and healthy community around the scientific Python ecosystem is just as crucial as the tools themselves.
| </figure> | ||
|
|
||
|
|
||
| ## Chorus: Learning and Growing |
There was a problem hiding this comment.
maybe
Learning and Growing through Talking at meetings
or something like that?
|
|
||
| ## Bridge: Looking Ahead | ||
|
|
||
| Recently, I joined pyOpenSci, an organization that resonates deeply with my values. Their commitment to enhancing the scientific Python ecosystem through a rigorous peer review process aligns perfectly with my own aspirations. This process not only recognizes the hard work of scientists contributing to open Python tools, but also promotes standardization and increased visibility for these packages. I am excited to bring my past experiences to the table, helping to strengthen community building and outreach within this incredible project while eagerly learning from the talented individuals who are part of it. |
There was a problem hiding this comment.
It would be nice to link here to our peer review guide
https://www.pyopensci.org/software-peer-review/about/intro.html
|
|
||
| ## Outro: Gratitude | ||
|
|
||
| As a community manager at both Scientific Python and pyOpenSci, I have witnessed the wonders of the Scientific Python ecosystem. I have encountered countless remarkable individuals and witnessed the incredible projects they have created using the available tools. In my opinion, unifying the community and promoting project integration is the key to unlocking the full potential of this ecosystem. It's not just about coding; it's about coming together, sharing knowledge, and supporting one another. I am grateful for the opportunity to contribute to this vision and help build an extraordinary community around the scientific Python ecosystem while walking this journey alongside amazing people. 🫶 |
There was a problem hiding this comment.
this is another gem of a quote
It's not just about coding; it's about coming together, sharing knowledge, and supporting one another.
Thanks for the feedback :) I'll do another commit with the title changes and I'll look into putting the quote in the body. Not sure how to do it though. Co-authored-by: Leah Wasser <leah@pyopensci.org>
|
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM> Co-authored-by: Leah Wasser <leah@pyopensci.org>
|
I also improved the titles as suggested. let me know what you think :) |
|
ok wonderful!! i'm going to test our our new dev container that @crazy4pi314 made for us to see how this looks without building locally :) |
|
Seems like you can ignore the spurious htmlproofer linkcheck failure on Linkdin by adding the URL under
Have you considered just using something like Netlify for automatic site previews on PRs? The free tier should be more than enough and it only takes a few simple steps to set up. We use that or something similar on all the sites I'm involved with; we even used it for the Python docs until we switched to RTD for previews. Once we started using it, it was so handy to have an instant, fully working preview on every PR (both for reviewers and especially contributors) that it feels like going back to the stone age without it, haha. |
|
@CAM-Gerlach i have thought about implementing that. i just haven't had time!! i did set it up for another website i'm working on. it was easy. i wasn't sure if the previews would be free forever if we update the site regularly?? maybe we can open an issue and discuss? |
|
Sure. Opened as #197 |
|
Good morning @juanis2112 . I wanted to leave a bit of feedback that I have after talking this blog through with my board a bit the other day. One of the community challenges that we have at pyOpenSci is that it's confusing for people regarding what pyOpenSci is and what we are doing vs what the Scientific Python project is doing. I know that Stefan and Jarrod get similar questions! In the blog post verse 2 is about your amazing work with the Scientific Python ecosystem. And the focus they have is really development work around the bigger core packages which is super needed and critically important! The following paragraph - the chorus is also about talks you've given for Scientific Python. Which again is wonderful but it's really focused on that specific effort! There is a small section on pyOpenSci and supporting our work as well. But this internship that you have been doing with us is wrapping up this week. it's been so so wonderful to work with you!!! What a gift! Then the final paragraph is about Scientific Python project again with an image of everyone in that project with the tshirts. I thijnk what happens is the broader scientific Python ecosystem (people who are scientists using Python vs the Scientific Python project) is conflated in this blog. The efforts of Scientific Python project and pyOpenSci are super complementary! But the communities and target audiences are actually quite different. I worry this blog post mixes the two together in a way that will confuse folks more. And this has been a real challenge for me when i got into communities to talk. But it also really speaks to your devoted support for and engagement with the Scientific Python project (which i love!). Your incredible work with them SHOULD be highlighted and spotlighted. I just wonder if this post should live on the Scientific Python blog rather than ours given it's really focused on that community? i am concerned about this blog post confusing folks more. Let's talk this through a bit together this morning and see where we land. I just wanted to voice my concerns here openly so I can be transparent. |
|
@lwasser Let's go ahead and close this PR or edit and merge. |
|
thank you, @willingc . i'll close it now!! |
4 participants
I thought we could take a picture together this weekend @lwasser and I could add it to the 'Looking ahead' section but apart from that I think it is ready. I also built the website to check everything was correct but I don't have the pre-commit hooks installed yet so that might fail. I'm happy to install them and run them if you can guide me through it.
I would appreciate feedback on the figure captions and ALT text since that was not part of the initial draft and also please let me know if you have some specific guidelines for image compression or if the files are too big.