# Next steps for Pangeo / PyOpenSci Collaboration

**URL:** <https://discourse.pangeo.io/t/next-steps-for-pangeo-pyopensci-collaboration/2902>\
**Category:** Meta\
**Created:** [November 4, 2022, 6:58pm UTC](https://discourse.pangeo.io/t/next-steps-for-pangeo-pyopensci-collaboration/2902 "2022-11-04T18:58:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![TomAugspurger](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/tomaugspurger/32/21_2.png) [@TomAugspurger](https://discourse.pangeo.io/u/TomAugspurger)\
**Post date:** [November 8, 2022, 2:54pm UTC](https://discourse.pangeo.io/t/next-steps-for-pangeo-pyopensci-collaboration/2902/3 "2022-11-08T14:54:06Z")

</div>

I can volunteer to help out from the pangeo side. I agree that the main work item here is updating our [Package Guidelines](https://pangeo.io/packages.html).

If folks are OK with me working on this, I’ll focus on deduplicating our guide with what’s covered by PyOpenSci’s guides, focusing on the bits that are pangeo-specific (where pangeo will roughly mean “geoscience”, maybe “scalable geoscience” in this context).

> Is there an overall vision or framework we want to use to organize and classify the packages in our ecosystem?

I think this is worth a discussion (which we can do asynchronously here). I’ll make another post later with my thoughts.

From there, I’ll probably follow @lwasser’s advice and just help out with editorial duties, rather than trying to submit various packages through the process.

---

_[View the full topic](https://discourse.pangeo.io/t/next-steps-for-pangeo-pyopensci-collaboration/2902)._