Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

jarrodmillman
Copy link
Member

@jarrodmillman jarrodmillman commented Sep 9, 2025

This is a first pass at formalizing what a "Scientific Python Developer Summit" is.

On the summit landing page https://scientific-python.org/summits/ it states:

The developer summits address topics of interest across several packages
(e.g., sparse arrays, benchmarking, packaging, teaching, specific science domains).
While we also organize some more topic focused developer discussions,
e.g., for the Domain stacks or Sparse Data.

That text needs some work. And we will also need to start formalizing what a "Scientific Python Domain Stack Summit" and/or a "Scientific Python Topic Summit". We can do that in a future PR or we can expand this PR.

@jarrodmillman jarrodmillman marked this pull request as draft September 9, 2025 23:09
Copy link

netlify bot commented Sep 9, 2025

Deploy Preview for scientific-python-org ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit bdef581
🔍 Latest deploy log https://app.netlify.com/projects/scientific-python-org/deploys/68c1b927bc30eb0008349025
😎 Deploy Preview https://deploy-preview-802--scientific-python-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 81
Accessibility: 100
Best Practices: 100
SEO: 100
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a "disclaimer" of some sort that the SP project endorses other collaborative events and meetings, just please don't call those "SP Developer Summit" -- as we don't want to diverge the meaning/scope/expectation of what an SP Dev Summit is.

We could maybe also offer some phrase/branding for those.

- Provide time for substantial collaborative technical work, while also leaving space for higher-level discussions where relevant.
- Focus on issues with cross-project impact, rather than narrowly scoped tasks that impact only a single package or work that one person could reasonably pursue independently.

The Scientific Python project welcomes and endorses many forms of collaborative events and developer meetings.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It probably makes sense to have something like this here, but there is some overlap with the summits landing page: https://scientific-python.org/summits/

Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I quite like what you have now

@jarrodmillman jarrodmillman marked this pull request as ready for review September 10, 2025 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants