Skip to content

Commit 52f69f5

Browse files
authored
Add: blog post - CZI funding
Add: new blog post - czi funding announcement
2 parents 9e156f5 + c3dade8 commit 52f69f5

File tree

6 files changed

+84
-8
lines changed

6 files changed

+84
-8
lines changed

.github/workflows/build-site.yml

-5
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,6 @@ jobs:
2828
build_only: true
2929
build_dir: _site
3030

31-
- name: all dirs
32-
run: |
33-
ls
34-
pwd
35-
3631
- name: Check HTML using htmlproofer
3732
uses: chabad360/htmlproofer@master
3833
with:

Gemfile

+1
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,4 @@ source "https://rubygems.org"
33
gem "github-pages", group: :jekyll_plugins
44
gem "jekyll-include-cache"
55
gem "webrick"
6+
gem "html-proofer"

README.md

+7
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,13 @@ for creating this site. To set up a **development environment** and **run the si
3232

3333
Please test your changes locally prior to submitting a pull request (PR).
3434

35+
36+
### Want to build with new blog posts to be published in the future?
37+
38+
If you are publishing a blog post with a date that is in the future, you can build the site locally using the `--future` option to view it as follows:
39+
40+
`bundle exec jekyll serve --future`.
41+
3542
## Contributors ✨
3643

3744
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):

_data/authors.yml

-3
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,6 @@ Leah Wasser:
1212
- label: "GitHub"
1313
icon: "fab fa-fw fa-github"
1414
url: "https://github.com/lwasser"
15-
- label: "Twitter"
16-
icon: "fab fa-fw fa-twitter-square"
17-
url: "https://twitter.com/leahawasser"
1815
- label: "LinkedIn"
1916
icon: "fab fa-fw fa-linkedin"
2017
url: "https://www.linkedin.com/in/leah-wasser-0138883/fo"
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
layout: single
3+
title: "CZI Funds pyOpenSci"
4+
excerpt: "CZI has received funding from the Chan Zuckerberg Foundation. Learn more about how this funding will support pyOpenSci over the next 2 years."
5+
author: "Leah Wasser"
6+
permalink: /blog/czi-funds-pyOpenSci-2024.html
7+
header:
8+
overlay_color: "#666"
9+
overlay_filter: 0.6
10+
categories:
11+
- blog-post
12+
- community
13+
toc: true
14+
comments: true
15+
---
16+
17+
## A bright 2024 is ahead for pyOpenSci
18+
19+
We are thrilled to announce that pyOpenSci has received 2 years of funding to cover core operations from the [Chan Zuckerberg Initiative (CZI)](https://chanzuckerberg.com/). These CZI funds will be used to continue critical pyOpenSci work that:
20+
21+
* supports Python open source maintainers in developing the usable and maintainable scientific software the enables open science;
22+
* helps scientists navigate a complex Python packaging ecosystem;
23+
* diversifies the scientific Python open source community.
24+
25+
26+
## Open science builds trust and enables more people to participate
27+
28+
Open and reproducible science builds trust and accelerates research and
29+
discovery. Open science supports scientific research that is both transparent and
30+
reusable. Free and open source software is critical to open science as it ensures that
31+
the analyses of research data are broadly accessible. To build truly open research workflows, scientists need to use free and open source software (FOSS). FOSS removes the barriers that licenses and other fees may create making diverse participation more accessible.
32+
33+
### Broad inclusion is critical for both open source and open science
34+
35+
Broad inclusion of underrepresented and historically excluded individuals is critical to pyOpenSci's mission. The open source ecosystem has been found to be [even less diverse then the broader tech community](https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/). To help remedy this, pyOpenSci empowers everyone to participate in both the development and use of open source software. This
36+
empowerment enables open science to reach its full potential.
37+
38+
### Open source maintainers need support
39+
Despite the importance of open source software to fundamental
40+
open science principles, open source maintainers do not get the support they
41+
need. Maintainers need both institutional and community support in learning
42+
and engaging in open source software development, maintaining tools and engaging
43+
with the broad user base that may begin to use their tools in support of open science.
44+
45+
## pyOpenSci is pushing for change
46+
47+
pyOpenSci is pushing for change. We envision a world where:
48+
49+
* The scientific Python open source ecosystem is diverse and inclusive;
50+
* Individuals developing open software are supported;
51+
* Scientists have the skills needed to both contribute to open source and also develop collaborative open science workflows; these skills have significant overlap.
52+
53+
## pyOpenSci builds a supportive and inclusive world through three programs
54+
55+
<figure>
56+
<a href="/images/pyopensci-pillars-flower.png">
57+
<img src="/images/pyopensci-pillars-flower.png" style="max-width:100%" alt="A flower petal image with 3 flower petals and a flower center. In each petal there is text. The first says software peer review, the second community partnerships and the third packaging resources and recommendations. The center circle of the flower says diverse inclusive community.">
58+
</a>
59+
<figcaption> pyOpenSci supports scientists developing open source software through three programs: 1) peer review of scientific software, 2) community partnerships and 3) packaging resources and recommendations. These three programs are supported by a diverse and inclusive community that cares about the open source software that is needed for open science.
60+
</figcaption>
61+
</figure>
62+
63+
The three programs pyOpenSci runs are:
64+
65+
* [Peer review of scientific Python software](https://www.pyopensci.org/about-peer-review/index.html) - The pyOpenSci software peer review process helps scientists find the vetted and trusted tools they need to build reproducible open science workflows. We also empower our community with critical open science skills that support contributing to open source software.
66+
67+
* [Community partnerships with domain-specific scientific Python communities](https://www.pyopensci.org/partners.html). Domain-specific communities partner with PyOpenSci to leverage pyOpenSci's peer review process as a way to track vetted, high quality tools. Communities also support the development of Python packaging packaging guidelines in an effort to streamline the development of packaging recommendations across the scientific Python ecosystem.
68+
69+
* Training and resources to help scientists develop and maintain high-quality, accessible, open source software. Our community developed the [Python packaging guide](https://www.pyopensci.org/python-package-guide/), which provides resources and tutorials that help scientists navigate a complex Python packaging ecosystem. The Python packaging guide also makes recommendations for community accepted best practices.
70+
71+
## Looking forward to 2024
72+
73+
pyOpenSci is excited to grow a more inclusive and supportive scientific Python community in 2024!
74+
75+
We are always looking for volunteers to support our community programs.
76+
If you are interested in getting involved with pyOpenSci, [learn more here](/get-involved-contact.html).

images/pyopensci-pillars-flower.png

153 KB
Loading

0 commit comments

Comments
 (0)