DevNotes_07Aug2026_Technical

New Topics to Discuss

• Reporting to Fortnightly meeting: Jeff unable to attend
• Next Refactor Hackathon
  • https://github.com/SasView/sasview/wiki/RefactorHackathon%E2%80%902026%E2%80%90III
  • Planning for September
  • Answer the poll: Poll - Sept. 16-18 looking pretty good right now
  • James proposal for a Project Board with more specific work packages
    • Finish data explorer -> Plotting -> Perspectives (MuMag, then Invariant, with Fitting last (most difficult))
    • Project boards for each section and each perspective
    • Hope to be in a state to work on Perspectives during contributor camp* (depends on James' availability)
• Planning for Contributor Camp
  • Register and get travel approval!
  • Discussion on presentations, projects, and collaborations
    • What will be taught and what will be worked on depends on who attends!
    • Introductory presentations at the start (to orient new contributors) - many people need presentations for travel purposes
      • James: The refactor status to-date
    • Expected projects to be worked on
      • GSC based on discussions
      • Refactoring Project
      • Sasmodels refactor/rework
      • Magnetic SANS(?)
      • MCR-ALS project
      • Automating Releases
• Agentic AI Usage
  • Who is using it, what tools, and how?
  • How are users using AI, and how would they like to use it in the context of SasView?
  • Context files in repo discussion
• Release branch rulesets conflicts
  • Branches named release[-_][0-9.]* cannot be modified, except by repo owners and admins
  • Branches are deleted when PRs are merged
  • If an admin or owner merges a PR for a protected branch, the exception takes precedence, so the branch is deleted
    • Others have the same issue: https://github.com/orgs/community/discussions/152926
  • Potential solution(s):
    • GitHub workflow that restores the branch whenever deleted: https://github.com/orgs/community/discussions/152926#discussioncomment-12636248
    • Don't create PRs using release branches. Instead branch off the release branch for merge purposes.
  • Proposed Solution:
    • Create new branch off the release branch for merge purposes. Maintains clean release branch HEAD and alleviates the issue with deletion.

Next bug fix release

• 6.2.0 is officially released!
  • Flatpak release status? Next week
  • Conda forge build issue: https://github.com/conda-forge/sasview-feedstock/pull/56
    • pyausaxs: No conda build and pip wheel has issues on Intel Macs - James and Marie to work with Christian
• Release manager for 6.2 bug fix releases: Paul S.
• 6.2.1 timeline discussion
  • Release date: Before contributor camp - mid to late October
  • Potential PRs to include:
    • Composite model failures: SasView #4082 and SasModels #749
    • Old What's New cards: #4046
    • Fix fit_started flag: #4067
    • Magnetic model calculations always run: #4072
  • Other known issues:
    • Invariant Issues #3986
    • Mutli-slicers and batch #4081
  • Include new torus elliptical shell model?

Status updates of ongoing projects

• CodeScene (Jeff)
  • CodeScene integration: Two PRs open - SasView, SasModels
• MCR-ALS Project
• SasModels Refactor
• SASBDB Project:
  • One PR ready for review: SasView #3913
  • AI agent context file included (reason for the discussion)
• James' project(s)

Outstanding PRs

• SasView (26 open, 11 ready for review)
  • Ready to merge?
    • Pytest from base directory: #3974
    • Magnetic model calculations always run: #4072
  • Needs reviewers
    • Old cards in What's New: #4046
    • Fix fit_started flag: #4067
    • On tag auto-upload to release: #3932
  • Under review:
    • Undo project: #3995 - Jeff to revisit
  • More work to do:
    • Cancel concurrent nightly builds: #3947
    • Pixi configuration: #3842
    • Online doc location: #3926 vs. #3943
  • In draft PRs - who needs help?
• SasModels (9 open, 5 ready for review)
  • Ready to merge?
    • Unused step warning: #737 - to merge
  • Needs review:
    • Peak Voigt Model: #743
    • Fractal S(Q) accuracy: #722
    • Structure Factor Models: #719
  • What to do with Better Integration in #608?
• SasData (4 open, 1 ready for review)
  • Refactor Trend: #216 - Jeff K. reviewing
• SasView.github.io (2 open, 1 ready for review)
  • Update Acknowledgement Section on Website: #37
• Saspubs (1 open, ready for review)
  • Acknowledgement template: #11

ADRs and other Discussion

• To Finalize
  • https://github.com/orgs/SasView/discussions/3475: Release automation - create issues for each step - Assignee is Jeff - NOT AN ADR
    • Zenodo generation: build_tools/release_automation.py - Piotr to look into Zenodo DOI generation that he knows of in other repos
    • Pypi publishing: Work started in sasdata. Finalize and port to sasview and sasmodels - Piotr to work on https://github.com/SasView/sasdata/blob/master/.github/workflows/test.yml#L84
    • Upload binaries to releases: Already working for nightly build. Port in progress for sasview PR
• Ongoing discussions:
  • https://github.com/orgs/SasView/discussions/3934: Defining the release process and release manager
    • Much of the process is outlined in https://github.com/SasView/sasview/wiki/DevNotes_DevGuide_ReleaseChecklistTemplate
    • Deleted release branch makes this a higher priority
  • No Link: Contributing to SasView: Define the process, i.e. what the requestor needs to provide, level of support from the existing community, and what that gets the contributor
    • https://github.com/SasView/sasview/wiki/contribution_acknowledgments to an ADR - Paul B. to convert prior to the Nov. Contributor Camp
  • Discussions to bring up:
    • SasModels scripting question: https://github.com/orgs/SasView/discussions/3540 - Close?
    • Sourceforge: https://github.com/orgs/SasView/discussions/2344 - Close Sourceforge and the discussion?

AOB?