Repository navigation
Add AGENDA.md: project agenda as of 2026-11-06 - #314
Merged
Merged
Conversation
Merge queue for PRs #310-#313, stale PR and issue triage, release 1.2, the live-tools and runtime lines, a survey of what charm4py can use of Charm++'s GPU support (device-resident data, device-to-device messaging, the GPU-aware load balancer), docs and ownership. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
lvkale
enabled auto-merge (squash)
November 6, 2026 23:08
ritvikrao
approved these changes
Nov 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A project agenda file kept in the repository so it can be edited by PR.
Sections: merge queue for #310-#313, stale PR and issue triage, release 1.2, the live-tools line (appSpector, liveViz, steer), the runtime line (Ray API, GPU d2d), a survey of which Charm++ GPU capabilities charm4py programs can use today (device-resident data per chare, direct GPU messaging, the GPU-aware load balancer) with a proposed order of work, docs and tutorial, ownership.
Comments and edits welcome; the file is meant to be revised at each project meeting.
🤖 Generated with Claude Code