-
Notifications
You must be signed in to change notification settings - Fork 22
Meeting 2019 09 13
Josh Hursey edited this page Sep 13, 2019
·
1 revision
- (Dave) Working group update: Implementation agnostic document
- Mailing list: https://groups.google.com/forum/#!forum/pmix-forum-wg-impl-agnostic
- Meeting: Tuesday's at 9 am (Central)
- Tracking:
- (Stephen) Working group update: Slicing/Grouping of functionality
- Mailing list: https://groups.google.com/forum/#!forum/pmix-forum-wg-func-slices
- Meeting: Wednesday's at 11 am (Central)
- Tracking:
- Use Case Items:
- Business Card Exchange: https://github.com/pmix/pmix-standard/issues/191
- Debugging: https://github.com/pmix/pmix-standard/issues/216
- ASC Quarterly Meeting planning update
- Announcement: https://groups.google.com/d/msg/pmix-forum/R7B7W9DbGvo/OuAfEzXfAAAJ
- Finalize Agenda (Must be finalized by Sept. 17) https://github.com/pmix/pmix-standard/wiki/ASC-Q4-2019-Meeting
- Call for nominations
- Call for additional working groups
- PMIx Standard: Open GitHub Issues and PRs
- PMIx Governance: Open GitHub Issues and PRs
- https://github.com/pmix/governance/pulls
-
https://github.com/pmix/governance/issues
- Conflicting conditions for elevation to Stable Status https://github.com/pmix/governance/issues/5
- Create new section for general guidance and philosophy https://github.com/pmix/governance/issues/6
Joshua Hursey (IBM)
Michael Karo (Altair)
Howard Pritchard (LANL)
Danielle Sikich (Intel)
David Solt (IBM)
Ken Raffenetti (ANL)
Swaroop Pophale (ORNL)
John DelSignore (TotalView)
Kathryn Mohror (LLNL)
Stephen Herbein (LLNL)
- WG: Implementation agnostic document
- Worked through last few cleanup items for Chapter 1
- Good point to broaden discussion outside of the working group.
- Dave will circulate a PDF draft of PR #175
- Moving forward to the next chapters
- Discussion items:
- “Specification” vs “Standard” use in the document. Try to convert these to be consistent throughout the document.
- How do we want to bring these changes into the document (part-by-part, or all at once)?
- Removal of items in Chapter 1 that may make later chapters a bit more confusing until they are updated.
- If we bring it all together then it would be too much.
- Suggestion: Bring in one chapter at a time. Maybe wait to merge in Chapter 1 until next couple chapters are ready.
- Will bring forward for discussion at the ASC meeting
- Worked through last few cleanup items for Chapter 1
- WG: Slicing/Grouping of functionality
- Reviewed which of the PMI1 functions are in the PMIx standard (how they are represented)
- Debugging Use Case discussed
- ASC Meeting:
- Work up slides
- Discuss how to integrate these into the standard
- Use Case Items
- Debugging:
- Please take a look and add comments
- Tool integration document in development
- Should this be part of the standard or a companion?
- Debugging:
- ASC Quarterly Meeting planning update
- Agenda
- Working groups
- Present on their goals
- Outline the work completed, in progress, and future
- Implementation agnostic document
- Present Chapter 1 changes
- Slices
- Present the Use cases so far
- Discuss: How use cases will be incorporated in the document
- Add breaks to plan around - add a timeline
- Define time periods with well defined breaks
- Allows folks to tune in for the important events
- If we go faster then breaks can go longer
- Discussion: What is the goal of the Friday meetings with the advent of the quarterly meetings.
- Add future agenda item on research topics
- Working groups
- Agenda
- PMIx Standard Issues and PRs
- A new PR against the v4 standard for comment:
- PMIx Governance Issues and PRs
-
https://github.com/pmix/governance/pull/7
- Guidance on a forcing mechanism to drive releases in a timely manner with flexibility to delay if required.
- Suggested a couple of wording adjustments, but general approval.
- Will be added to ASC agenda
-
https://github.com/pmix/governance/pull/7