feat: Add more info around org values#77
Conversation
|
|
||
| The mission of pyOpenSci is to support diverse community around the free, open | ||
| python tools that drive open, reproducible scientific workflows. | ||
| The mission of pyOpenSci is to support building a diverse community of practice around the free, open Python tools that drive open, reproducible scientific workflows. |
There was a problem hiding this comment.
"support building" sounds awkward to me. I like "support" on its own, or if you wanted something more active, you could say "build and support". Or "expand and support a diverse" to emphasize the theme of building on existing work?
There was a problem hiding this comment.
Also, on https://www.pyopensci.org/handbook/governance/index.html we state the mission as "pyOpenSci is an non-profit organization whose mission is to build diverse, supportive community around the free and open Python tools that drive open science." The mission statement should be the same in all places.
| others work rather than recreating already developed workflows. Building on | ||
| top of existing workflows supports science developing and evolving at a quicker pace. | ||
| other's work rather than recreating already developed workflows. Building on | ||
| top of existing workflows accelerates science as it prevents scientists from needing to rebuild existing workflows from the ground up. |
There was a problem hiding this comment.
These two sentences are pretty repetitive. What if the second one said something like "This accelerates science by allowing researchers to focus on novel questions and approaches." Feel free to wordsmith!
| without paying costly subscription fees. | ||
|
|
||
| This free and open source software is critical to supporting development of | ||
| This free and open-source software is critical to supporting the development of |
There was a problem hiding this comment.
I don't think "open source" is generally hyphenated.
There was a problem hiding this comment.
i've had this question for a while and googled this topic. I'll keep it unhyphenated, but in some places like the microsoft style guide, it's hyphenated!! Let's decide that as an org we don't hyphenate it. 😆 if I add it to grammarly it will remind me not to. I have no opinion here.
|
hi, @kcranston, I am going to rebase this pr, but I won't update it until after our mission and vision sessions that we are having in the upcoming weeks!! I have noticed the feedback, however, and do want to address it after we've had our EC sessions!! |
2 participants
No description provided.