Skip to content

Commit ad047ef

Browse files
committed
CONTENT: update resources
1 parent 50d3db2 commit ad047ef

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

_pages/resources.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,18 @@
11
---
22
layout: single
3-
title: "More Resources"
3+
title: "pyOpenSci Resources"
44
author_profile: false
55
published: true
66
site-map: true
77
permalink: /resources/
88
---
99

10-
Here are some links to our resources and related sites:
10+
We are currently working on all of our organization-wide documentation and
11+
governance. The guidebook links below are being updated and we welcome feedback!
1112

1213
* [**pyOpenSci Github Organization**](https://github.com/pyOpenSci): Contains our [software-review](https://github.com/pyOpenSci/software-review) repo that hosts the peer-review process. Also contains our guidebook, cookiecutter, and governance repos (see below).
1314

14-
* [**pyOpenSci Discourse Forum**](https://pyopensci.discourse.group/): Our community forum for discussing all things pyOpenSci. Have feedback or ideas about the review process? Need help finishing or maintaining your Python package? Have a question about how to use one of pyOpenSci’s packages? Our forum is the best place for these types of discussion.
15+
* [**pyOpenSci Peer Review**](https://www.pyopensci.org/peer-review-guide/): Contains information for package authors and reviewers.
1516

16-
* [**pyOpenSci Guidebook**](https://www.pyopensci.org/peer-review-guide/intro): Contains information for package authors and reviewers, including our [package guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html#packaging-guide), our [peer review process](https://www.pyopensci.org/peer-review-guide/intro.html), and tips for [package maintenance](https://www.pyopensci.org/peer-review-guide/open-source-software-peer-review/policies-and-guidelines.html#after-acceptance-package-ownership-and-maintenance). If you are interested in submitting a package to pyOpenSci, start with our [author guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html) and the links within it.
17+
* [**pyOpenSci's Governance**](https://www.pyopensci.org/governance/): Where we discuss the direction and scope of pyOpenSci. We're a community organization, so please feel free to create an [issue](https://github.com/pyOpenSci/governance/issues) if you have any questions or concerns!
1718

18-
* [**pyOpenSci's Governance Repo**](https://github.com/pyOpenSci/governance): Where we discuss the direction and scope of pyOpenSci. We're a community organization, so please feel free to create an [issue](https://github.com/pyOpenSci/governance/issues) if you have any questions or concerns!
19-
20-
* [**pyOpenSci cookiecutter**](https://cookiecutter-pyopensci.readthedocs.io/en/latest/): We created a cookiecutter template to make packaging your python code easier. The cookiecutter follows all our guidelines from our [packaging guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html#packaging-guide).
21-
22-
* [**rOpenSci**](https://ropensci.org/): We draw inspiration from rOpenSci, a community to help promote, teach, and grow best-practices in software development for the Scientific R stack. They have a wonderful array of resources for R, such as their [collection of scientific R packages](https://ropensci.org/packages/). If you use R, we encourage you to get involved with them.

0 commit comments

Comments
 (0)