Developer Meeting Agenda

[ljwolf]

Hi folks!

With the increasingly moribund gitter interface, it might be good to move our discussions somewhere? I think GitHub discussions are a great way to keep things united on the same platform.

[ljwolf]

For instance, last month's developer meeting agenda lists next week's developer meeting agenda as available here, but I cannot access it? I think both @martinfleis and I will have updates from the scientific python summit from last week.

[sjsrey]

Permissions are now changed and you should have access.

[jGaboardi]

@ljwolf My workflow on this for the past several years is:

1. Copy the notes from the previous month
2. Create a fresh HackMD doc
   1. fresh doc needs updated permissions...
   2. Share -->
   3. swap "View Mode" to "Edit Mode"
   4. change "Note Permission" for Read & Write to either signed-in users or everyone
   5. Accept terms box and click Publish
3. Change the dates, chair
4. Remove unneeded notes
5. Update Previous Meeting and Next Meeting links
6. Add an entry to the Developer meetings Wiki

I am happy to keep doing this as time permits, but I have been falling behind a bit due to <reasons>.

[sjsrey]

PySAL Meeting 2023-08-03

Chair: Serge

Agenda

• meta release update (sr)
• pose proposal (sr)
• other

---

• Previous Meeting
• Next Meeting -- need link to new doc
• Next Chair:

[martinfleis]

• esda release
• libpysal.graph updates and plans

[sjsrey]

Meta Release Discussion

• Update our tooling
• Adopt a tag scheme
  • What tags get used in the meta release from the packages
  • come up with a subset used across the package
  • @knaaptime and @sjsrey will draft up and circulate list of common tags

[sjsrey]

ESDA Release

• Cut an ESDA Release
• Regroup with Debian on the numba issues

[sjsrey]

Geograph work

• it is living on the geography branch
• it handles roundtriping between W and Graph
• Will coexist with W for a transition period (length to be determined)
• @martinfleis teaching SDS in the fall and wants to use the new stuff
• @knaaptime and @sjsrey are also doing NARSC
• make available on main in roughly 2 weeks
• release in end of august
• second release end of September

[sjsrey]

For Dev Notes

• We go back to hackmd
• One document that captures all meeting notes
• Most recent meetings at the top

[sjsrey]

PySAL Dev Meeting 2023-11-02

Agenda

• Submodule -> libpysal (serge)
• CZI proposal (martin)
• other

[martinfleis]

• permissions (mgwr...) (martin, james)
• libpysal.graph API for IDs (martin, eli)
  • fix index check for precomputed graph distances libpysal#616 (comment)
• Coordination (martin)
  • Add Wilkinson formula interface and scikit-learn style estimators spreg#103
• CI
  • Ruff format, extended pre-commit hooks following Scientific Python recommendations
• AGILE 2024 (Glasgow) PySAL workshop? (Martin)
  • application: https://docs.google.com/document/d/1ZQdF5pXE1HzzQqjcmKxBXIeqguN1SQr0/edit?usp=sharing&ouid=101400752976219419227&rtpof=true&sd=true

[jGaboardi]

(I can join for the first ≈20 minutes)

• admin permissions on:
  • GitHub
    • legendgram – permissions for the steering council legendgram#17
    • mgwr – permissions for the steering council mgwr#131
    • spint – permissions for the steering council spint#39
    • spvcm – permissions for the steering council spvcm#16
  • PyPI
    • all the above, I think. Maybe others.
• conga-forge feedstocks...
  • Now I think we have steering council on all feedstocks.
• libpysal linting update

[ljwolf]

• revisit governance

[gegen07]

• Spopt AZP failure was fixed. PR is under review.
  • Fix CI failure due to AZP multiple valid MST spopt#406

[martinfleis]

PySAL Dev Meeting 2023-12-07

Agenda

• CZI
• Tooling updates
  • Ruff Format
  • extended pre-commit hooks following Scientific Python recommendations
• Communication platforms
  • Proposal:
    • Internal mailing list for stuff everyone should know
    • Open GitHub discussions for stuff like agenda etc. Everyone from the community can interact.
    • Open chat instance that actually works (Discord/Slack??) with possibly closed internal channels for anything that does not need to be persistent (e.g. what is the link for the call today or hey, James, the CI is broken again.
• AGILE 2024 PySAL Workshop
• WRSA workshop 2024
• GeoPython 2024
• GIS584 Spring 2024
• governance
• spopt release coming soon
  • v0.6.0 release checklist spopt#414

[ljwolf]

Thank you for posting!

I indeed am not able to chair today, I could not find cover for my teaching ☹️

[knaaptime]

team will vote on discord vs slack for constant communication

[jGaboardi]

• Tooling updates
  • Team voted in favor of implementing Formatting via ruff libpysal#662

[jGaboardi]

PySAL Dev Meeting 2024-01-04

Chair: James

Agenda

• intros with/ Kamal Akbar
• communication platforms
  • any updates?
  • cast your vote! https://github.com/orgs/pysal/discussions/1291
  • tentative vote for discord --> @martinfleis will set up
• governance (James)
  • schedule Steering Council meeting? may quarterly?
    • @jGaboardi will schedule 3 meetings this year
  • update Code of Conduct Committee?
    • https://github.com/pysal/code_of_conduct
    • Steering Council will discuss transition from maintainer-based CoC Committee to NumFocus based
      • this was @martinfleis 's idea
• momepy refactoring in Q1
• spopt fresh release >> v0.6.0
  • trouble with macports install >> Failing to install v 0.6.0 with pypi tarball spopt#435
  • seems to be something different with files included
    • check difference with:
      • segregation, tobler, momepy
• esda, lib, meta releases?
  • • giddy
  • maybe tobler
  • deadline – 2024-01-24
• GeoPython (SR)
  • Deadline 1/15
  • let Serge know by this weekend
• News BOT (SR)
• Kamal (Spatial Causal Inference PKG)
• Future chairing
  • @sjsrey will set up future scheduling in advance

Next chair: @weikang9009 (2024-02-01)

[sjsrey]

GeoPython Submission Deadline 1/15

[martinfleis]

Discord server has been set up https://discord.gg/he6Y8D2ap3.

[knaaptime]

PySAL Dev Meeting 2/1/2024

Agenda

• highlights section for release (and meta release)
  • meta release on Jan 31, 2024
  • release notes, new release scripts/structure
  • highlights notes in the subpackage release
    • select a label for each PR - "enhancement" would be for highlights
  • package release news will be "automatically" posted on PySAL's website
• GSoC
  • NumFOCUS is not doing it
  • https://summerofcode.withgoogle.com/programs/2024
  • serge will lead (deadline: 2/6/24)
• reverse dependency testing
  • mgwr
  • spvcm: archive it
• @jGaboardi needs to organize the 3 SC meetings
  • Is it possible to have a Steering Council room within the Discord channel?
  • For active SC member + BDFL
• dev meetings on discord?
  • trial next dev meeting
• update chat links in repos
  • update Gitter to Discord across ecosystem #1296
• M1 runners on GHA
  • add Apple silicon CI envs across ecosystem #1298

[martinfleis]

PySAL Dev Meeting 2024-03-07

Agenda

• Steering Council update
  • documentation
  • code of conduct
• ...
• ...

[sjsrey]

I moved the SC item into the next discussion (sorry didn't see this initially when creating the agenda)

[sjsrey]

PySAL Dev Meeting 2024-03-07

Agenda

• Steering Council update
  • documentation
  • code of conduct
• esda/p-values
• gsoc update
• 584 projects
• other

[ljwolf]

I will not be at the meeting today due to travel, but am very keen to help out on the p-value question! If there's anything I can explain better, please let me know.

Further, a decision about the two-tailed option currently used in the global Moran tests would be good... to be consistent, we will need to allow for directed tests in the global stats, too!

[knaaptime]

PySAL Dev Meeting 2024-04-04

• pointpats api discussion
  • postponed for meeting with other interested devs
• esda
  • propagation of folding logic
  • release?
• CZI outcome
• GSoC

[martinfleis]

PySAL Dev Meeting 2024-05-02

• congrats Serge!
• pointpats api discussion
  • propose moving to singledispatch for handling heterogenous input types
  • may need to think about docstrings
• spglm outsourcing of GLM solvers - Rely on GLMs from scikit-learn or glum  spglm#50
  • sure; but nobody's priority :)
• esda pseudo-p significance calculation - [Draft] pseudo-p significance calculation  esda#281

[knaaptime]

next chair: Martin

[jGaboardi]

PySAL Dev Meeting 2024-06-06

Chair: Martin

• last month recap
  • congrats Serge!
  • more on pointpats api & esda calculation discussions?
• proper package versioning from feedstocks
  • exposing the package version giddy#212
• networkx.Graph vs libpysal.Graph terminology when both are needed API: distinction between libpysal and networkx graphs momepy#579
• Docker container aligned with meta releases?