geojupyter · mfisher87 · Feb 12, 2025 · Feb 10, 2025 · Feb 11, 2025 · Feb 11, 2025
diff --git a/blog/20250114-core/index.md b/blog/20250114-core/index.md
@@ -0,0 +1,137 @@
+---
+title: "GeoJupyter core community meeting 2025-01-14"
+description: |
+  The first monthly gathering of the GeoJupyter core community. Open to all!
+date: "2025-01-14"
+author:
+  - name: "The GeoJupyter community"
+categories:
+  - "Meeting notes"
+tags: [meeting-notes]
+---
+
+# GeoJupyter core community meeting 2025-01-14
+
+- [Join us on Zoom](https://berkeley.zoom.us/j/99659397059?pwd=519zZJlcAa1TCyJWRYyYbaYDfuaXNo.1)
+  - [What time is the meeting in my time zone?](https://dateful.com/convert/utc?t=4pm)
+- [Previous meetings](https://geojupyter.org/blog/#category=Meeting%20notes)
+- [GeoJupyter](https://geojupyter.org) handy links:
+  - [GitHub org](https://github.com/geojupyter)
+  - [Community calendar](https://geojupyter.org/calendar.html)
+  - [Zulip chat](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter)
+
+
+## Attendees
+
+* Ciera Martinez / DSE
+* Matt Fisher / DSE
+* Qiusheng Wu / UTK
+* Maryam Vareth / BIDS
+* Martin Renou / QuantStack
+* Tammy Woodard / Clark CGA
+* Greg Mooney / QuantStack
+* Nicolas Brichet / QuantStack
+* Kyle Barron / Development Seed
+* Fernando Pérez / DSE/BIDS/Berkeley
+
+### Action items
+
+- [ ] All: Please read the [GeoJupyter announcement blog post](https://geojupyter.org/blog/20250108-introducing-geojupyter/)!
+- [ ] All: Please introduce yourself in our Zulip [“welcome” thread](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter/topic/Welcome)!
+- [ ] All: Consider upcoming events below – will we see you there?
+- [ ] All: Consider “What needs can the core team address right now?” below. Can you help with any of these things?
+- [ ] All: How are we doing? What do you think of our goals and needs? Have we missed anything? For any feedback, please create a new topic on Zulip, or reach out to Matt Fisher in whatever medium you prefer!
+- [x] ~~Matt: Create shared drive~~
+  - [Drive](https://drive.google.com/drive/folders/0AIppYlSqLkZNUk9PVA) Let me know if you need access!
+- [x] ~~Matt: Schedule JupyterGIS catch-up meeting on shared calendar~~
+  - Checking with QuantStack for timing preference
+- [x] ~~Matt: Create a bucket for use case ideas~~
+  - [https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter/topic/Early.20use.20cases.20brainstorming](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter/topic/Early.20use.20cases.20brainstorming)
+
+### Discussion
+
+1. 👋 Introductions
+   1. Ciera: Thank you for showing up!!!
+   2. Ciera: Introduce yourselves - shoot for 30 seconds. Ciera first, then popcorn! Matt will go last.
+      1. Who are you? Your affiliation? Why are you excited about GeoJupyter?
+   3. Matt: finance tech, then NSIDC, now here! So excited to learn from all of you ♥️
+      1. Thank you all for meeting together!
+      2. Expecting Fernando at 8:15.
+   4. Matt: About GeoJupyter
+      1. ☂️ An “umbrella effort” to improve user experiences working with geospatial (& temporal) data in JupyterLab.
+         1. 🤩 Check out [JupyterGIS by QuantStack](https://github.com/geojupyter/jupytergis), the first project in the [GeoJupyter GitHub org](https://github.com/geojupyter)
+      2. 🚀 [Mission](https://github.com/geojupyter/geojupyter.org/blob/main/elevator-pitch.md) (PRs welcome!)
+         1. Reimagine **geospatial interactive computing** experiences for education, research, and industry.
+         2. Combine the **approachability** and **playfulness** of desktop GIS tools, the **flexibility**, **efficiency**, and **reproducibility** of coding-driven GIS methods, and the **collaborative** and **storytelling** power of Jupyter to enable more researchers, educators, and learners to confidently engage with geospatial data.
+      3. 🥅 Goals (3 - 6 months; non-exhaustive 😉):
+         1. Interview users: >12 completed. See blog post for early findings.
+         2. Have one demoable / teachable use case for EGU - April 27, 2025.
+         3. Develop and “bakeoff” additional use cases!
+         4. Build relationships with early users (classrooms, workshops, great documentation and tutorials) and contributors (community programming, welcoming environment, …)
+2. 💬 How would you like to communicate?
+   1. ✅ Things we have so far:
+      1. ⚡ Real-time chat: [Zulip](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter). Please join!
+      2. ⚡ [Shared calendar](https://geojupyter.org/calendar.html): You can add it to your personal calendar by clicking “Add to Google Calendar” at the bottom of the calendar.
+      3. ⚡ [GeoJupyter.org](http://GeoJupyter.org) website - [open source](https://github.com/geojupyter/geojupyter.org), open a PR! anyone can contribute content, e.g. blog posts, to communicate with the community.
+      4. ⚡ [Community meetings](https://geojupyter.org/calendar) - open, like Jupyter meetings
+         1. Every 2nd Thursday of every month at 8AM PT / 4PM CET – thanks for being here ♥️
+         2. Post [here on Zulip](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter/topic/Scheduling) (or DM Matt) if this time is a struggle for you and we’ll attempt to find a better one or add a new time.
+      5. ⚡ Code of conduct: not published yet; starting with [Project Jupyter’s](https://jupyter.org/governance/conduct/code_of_conduct.html). Be kind to others ♥️
+   2. **👂 What else?**
+      1. Mailing list? Atom/RSS feed?
+      2. Note-taking tool?
+      3. Additional meetings or events to increase collaboration?
+         1. JupyterGIS catchup! Add to shared calendar
+      4. Shared drive! E.g. sharing presentations, videos, etc.
+3. 🗺️ Early strategy proposal
+   1. 👥 One early primary audience
+      1. We can’t be pulled in too many directions at this stage; we want to build some thing(s) that meet(s) a specific need so we can get feedback.
+      2. University educators and students. Strong interest from university communities (UC Berkeley, CU Boulder, Stanford, Clark).
+   2. 🎬 One early use case
+      1. Begin showing GeoJupyter rather than telling.
+      2. It should be usable in a teaching scenario (workshop, tutorial, classroom).
+      3. It should address a concrete user need or improve a user experience.
+      4. Candidate use case: [Geospatial debugging](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter/topic/.22Bouncing.22.20between.20JupyterGIS.20and.20a.20Jupyter.20Notebook/near/492346479)
+         1. A very common workflow: Build an analysis or tutorial in a Jupyter Notebook, but constantly writing out intermediate files (transferring between computers if necessary)  and “bouncing” between the notebook and QGIS to validate the data. High friction, high cognitive load, disruptive to screen sharing when teaching or collaborating.
+         2. How can we substitute JupyterGIS for QGIS in this workflow and eliminate unnecessary and frustrating steps? One line of Python, not counting import.
+         3. QuantStack has already done 99.99…% of the work 🎉
+      5. Fernando use case
+         1. Open a notebook from JupyterGIS session, pre-populate some cells: Markdown header cell with some details about data; code cells containing an object for each data layer in JGIS and necessary python imports to operate on.
+         2. QuantStack: Code generation exists for interacting with the JupyterGIS document itself.
+         3. QuantStack: What if the JupyterGIS project file itself was a notebook?
+            Discussed very briefly in [https://github.com/geojupyter/jupytergis/issues/41](https://github.com/geojupyter/jupytergis/issues/41)
+      6. **…? Need ideas! 💡**
+4. 📅 Upcoming events - will we see you?
+   1. April 27, 2025: European Geosciences Union. Want to have something to show, not just tell!
+   2. May 13-15, 2025: Matt and Fernando considering teaching a workshop @ [CSDMS 2025 annual meeting](https://csdms.colorado.edu/wiki/ESPIn2025) at CU Boulder SEEC building.
+   3. Week of May 19th, 2025: Potential hackathon event in Boulder, CO! 🥳
+      1. Hybrid is a strong priority!
+      2. Coding contributions to the core of GeoJupyter
+   4. May 28-30, 2025: Matt and Fernando considering attending/teaching workshop @ [ESIIL Innovation Summit](https://esiil.org/2025-esiil-innovation-summit) at CU Boulder SEEC building
+   5. July 7-13, 2025 - [SciPy](https://www.scipy2025.scipy.org/) in Seattle
+   6. JupyterCon - not ready for public announcement
+   7. 2025 - PyData Paris, organized by QuantStack
+   8. Summer 2025 - [OSGeo conference](https://www.osgeo.org/events/)
+      1. March 26-29 - FOSSGIS in Münster (in German)
+      2. [FOSS4G](https://2025.foss4g.org/) Europe, July 14-20 in Bosnia and Herzegovina
+   9. Quantstack attending:
+      1. GeoPython [https://2025.geopython.net/](https://2025.geopython.net/) in Feb. 2025
+      2. Living Planet Symposium [https://lps25.esa.int/](https://lps25.esa.int/) in June 2025
+5. **💪 What needs can the core team address right now?**
+   1. Generating candidates for new use cases! Please post on Zulip!
+   2. Talk about and explore candidate use cases
+   3. Explore .ipynb as JupyterGIS project format
+      1. A mechanism to hedge against file format decisions
+      2. Current format is structured JSON. Simple. Can extend the notebook format to include the same information in notebook metadata.
+      3. Visualization concerns - tooling for modern (in-memory) formats less stable.
+      4. JupyterGIS should support any data formats like QGIS does.
+      5. What about bundling everything needed to make a map in the project file? Different from the QGIS paradigm, provides significant value!
+         1. “Sidecar formats” - active discussions in Jupyter community **<TODO: Link!>**
+   4. Community programming advice! What community programming would you suggest to increase collaboration and engagement at this stage? Please post on Zulip!
+   5. Try out [JupyterGIS](https://github.com/geojupyter/jupytergis)! Make contributions! 🚀
+   6. **What else do you think we need? 👂**
+   7. …? 👂
+6. **☑️ Review action items**
+   1. If you have more you’d like to talk about, post a new topic on Zulip, reach out to Matt Fisher on Zulip, or [book a meeting](https://geojupyter.org/interviews/sign-up.html) (doesn’t have to be an interview)!
+7. Misc
+   1. Fernando @ AGU: Attended 3 hour GHG workshop. Part in notebooks, part in QGIS. Immediately illustrated why GeoJupyter is important. QGIS in JupyterHub with VNC on a crowded shared wifi is a miserable experience! People began falling behind the instructor. In a GUI workflow, if you miss a step in a workshop, you can’t go back and see what button you were supposed to press!
diff --git a/blog/20250211-core/index.md b/blog/20250211-core/index.md
@@ -0,0 +1,124 @@
+---
+title: "GeoJupyter core community meeting 2025-02-11"
+description: |
+  A monthly gathering of the GeoJupyter core community. Open to all!
+date: "2025-02-11"
+author:
+  - name: "The GeoJupyter community"
+categories:
+  - "Meeting notes"
+tags: [meeting-notes]
+---
+
+# GeoJupyter core community meeting 2025-02-11
+
+- [Join us on Zoom](https://berkeley.zoom.us/j/99659397059?pwd=519zZJlcAa1TCyJWRYyYbaYDfuaXNo.1)
+  - [What time is the meeting in my time zone?](https://dateful.com/convert/utc?t=4pm)
+- [Previous meetings](https://geojupyter.org/blog/#category=Meeting%20notes)
+- [GeoJupyter](https://geojupyter.org) handy links:
+  - [GitHub org](https://github.com/geojupyter)
+  - [Community calendar](https://geojupyter.org/calendar.html)
+  - [Zulip chat](https://jupyter.zulipchat.com/#narrow/channel/471314-geojupyter)
+
+
+## Attendees
+
+Your name / GitHub ID / affiliation / When you take a break, what's your favorite thing to do?
+
+* Matt Fisher / mfisher87 / Schmidt DSE / Sit in the sun outside and pet my dogs, Ricky & Waffles!
+* Greg Mooney / gjmooney / QuantStack / Make more coffee
+* Nicolas Brichet / brichet / QuantStack / ?
+* Martin Renou / martinRenou / QuantStack / Chop wood
+* Arjun Verma / arjxn-py / QuantStack / Usually go for a walk
+
+
+### Action items
+
+- [ ] Matt: Establish a way to redirect folks interested in GeoJupyter from Jupyter
+    Discourse to Zulip or GitHub. Either:
+  - Set up a notification alert on Jupyter Discourse for the term "GeoJupyter"
+    so we can start directing folks from there to our communication channels.
+  - Set up an empty / read-only category in Jupyter Discourse for GeoJuypter
+    which redirects folks to our communication channels.
+- [ ] Undergrad outreach.
+  - Ciera: Berkeley.
+  - Matt: Stanford, Clark, UT, more?
+
+
+### Standing items
+
+- [ ] Event planning
+  - Hackathon in-person Boulder, CO, May 22-23
+    - No updates. Will have updates for next meeting!
+- [ ] Team communication
+  - :tada: What is working well?
+    - Hackathons! :100: Productive and great for building social connections! :heavy_plus_sign:
+    - Zulip! I love topics.
+  - :wrench: Opportunities for improvement? Be nitpicky!
+    - I think we could use more networking within GeoJupyter between distant
+      organizations, e.g. DevSeed + QuantStack or DevSeed + Clark University Geospatial
+      group.
+    - We did awesome brainstorming during hackathon, it'd be really nice to see these
+      discussion continuing asynchronously over Zulip or GitHub
+      - Some people are reluctant to jump in to discussions where they don't know what's
+        going on. We can be more welcoming and encouraging for those who are reluctant!
+      - (personal take) I find interaction on Github easier to track and follow than
+        Zulip, we could try to encourage people to interact more on Github, less on
+        Zulip?
+        - Can be difficult to follow notifications in Zulip. Can keep up with
+          notification backlog in GitHub more easily. Can be difficult to find
+          discussions in Zulip 3 months later. GitHub can be less chit-chatty.
+        - Zulip for non-devs, GitHub for devs? Zulip as "upstream" of GitHub
+        - Also GitHub Discussions. More oriented to users. Could use this as a "when in
+          doubt" bucket -- if you're not sure if it's an "issue", just open a discussion
+          and we'll move it if it's an issue.
+    - Jupyter has used [Discourse](https://discourse.jupyter.org/).
+      Should we check there from time to time?
+      Matt: Set up notifications to be alerted if anyone mentions GeoJupyter on the
+      Jupyter Discourse. Then we can comment to let them know how to participate!
+      - Nicolas: Create a read-only GeoJupyter channel which links to Zulip! Redirect
+        folks from Discourse to Zulip. Matt: Look in to this.
+      - Arjun: Should we add a GeoJupyter category to Discourse?
+
+
+### Follow-up from previous meeting(s)
+
+- [ ]
+
+
+### New agenda items
+
+- [ ] [Hackathon debrief](https://geojupyter.org/blog/20250205-virtual-hackathon/)
+    - So much fun :D Thanks to all who attended!
+    - Please spread the word to help keep the momentum going :)
+    - Next in 1 week from tomorrow, Feb 19.
+      See the [community calendar](https://geojupyter.org/calendar)
+- [ ] Governance & stuff: What do we need? Looking to your expertise.
+      Goal: [Align with Jupyter subprojects](https://jupyter.org/governance/software_subprojects.html?responsibilities-of-jupyter-subprojects=#responsibilities-of-jupyter-subprojects)
+      & clarify current project status (i.e. NOT official subproject)
+      - Voila started as independent, became a subproject officially.
+        QuantStack (Sylvain) has experience with the process!
+    - Team compass: source of truth for community resources, policy, & practices.
+      This is something we can start now.
+    - Steering council: Not needed yet.
+    - SSC rep: Not needed yet.
+- [ ] Distributing power in the community
+    - Not going to solve today!
+    - Please start thinking about what roles need to be defined in our community.
+    - Ciera: Make sure we include a younger generation, maybe undergrads!
+      Reach out to Qiusheng for undergrads.
+      Empower to participate and make decisions!
+      **Ciera point of contact for Berkeley undergrads!**
+- [ ] Coffee chats!
+    - Cross-org coffee chats!
+- [ ] Update from JupyterGIS:
+    - [ ] The Python API now works in the JupyterLite deployment: https://jupytergis.readthedocs.io/en/latest/lite/lab/index.html?path=france_hiking.jGIS
+    - [ ] Soon to be publishing JupyterGIS 0.4.0 https://github.com/geojupyter/jupytergis/milestone/3 :tada:
+    - [ ] Working on a blog-post announcing JupyterGIS on the Jupyter blog :tada:
+      - Martin will share draft in GeoJupyter Logistics channel
+
+
+
+### Pushed to next meeting
+
+- [ ]