-
Notifications
You must be signed in to change notification settings - Fork 22
Meeting 2019 05 17
Josh Hursey edited this page May 30, 2019
·
4 revisions
- PMIx standardization process (try to limit to 30 min)
- GitHub Issue templates:
- https://github.com/pmix/pmix-standard/pull/187
- If no objection I would like to merge this tomorrow
- GitHub PR templates:
- (Dave) Working group: Implementation agnostic document
- Meeting Tuesday's at 9 am (Central)
- https://github.com/pmix/pmix-standard/issues/175
- (Stephen) Working group: Slicing/Grouping of functionality
- Doodle Poll closes May 17: https://doodle.com/poll/tn448ikhgnxndu9s
- https://github.com/pmix/pmix-standard/issues/182
- (Josh) Use Case gathering
- Open GitHub Issues
Joshua Hursey (IBM)
Kathryn Mohror (LLNL)
Geoffroy Vallee (Sylabs, Inc.)
Ken Raffenetti (ANL)
Thomas Naughton (ORNL)
Jim Garlick (LLNL)
Swaroop Pophale (ORNL)
Stephen Herbein (LLNL)
David Solt (IBM)
- PMIx standardization process
- Discussion of https://github.com/pmix/pmix-standard/issues/181#issuecomment-491351488
- Without levels: a straw vote of participants might be too light of a process. Let’s make sure more folks are looking at the discussion that might not have otherwise been paying attention - gather voices from the community.
- With levels: straw vote of participants may be fine.
- Suggestion to table this majority decision until a later time. Leave the language loose for now.
- Proposal: Don’t hold PR 183 for 3 remaining items. Keep issue open until the three issues below are resolved.
- Delay for reasonable amount of time
- Levels
- Majority straw voting in extraordinary circumstances
- Reading of PR 183 for 2 weeks from today.
- Discussion of https://github.com/pmix/pmix-standard/issues/179
- Level 1:
- Interface can change via a deprecation mechanism
- A bit more flexible in its lifespan
- Level 2:
- Stronger deprecation mechanism
- Interesting comment about difference between ‘API’ and ‘Attributes’
- Idea: Make separate documents that only have ‘level 2’ vs ‘level 1 + 2’ to help users only see the ‘level 2’ document.
- Needs more thinking/discussion
- Level 1:
- Discussion of https://github.com/pmix/pmix-standard/issues/181#issuecomment-491351488
-
https://github.com/pmix/pmix-standard/pull/187
- No objection - Merged
-
https://github.com/pmix/pmix-standard/pull/188
- From a Typo PR to merge
- Should there be a fast track for those types of changes?
- Yes. Give the community some time to review. At least 2 reviewers then merge.
- ‘Ask for forgiveness policy’ so it can be taken back out for discussion if there is an issue.
- From a Typo PR to merge
- Need for a crisp scope statement for PMIx
- (Dave) Working group: Implementation agnostic document
- Met on Tuesday and looked at the first chapter.
- Still reviewing the document to identify places that need to be reviewed/refined
- (Stephen) Working group: Slicing/Grouping of functionality
- Wednesday’s at 8 am (PT)/10am (CT)
- Meeting weekly to get started then less frequently thereafter
- Will work towards opening issue to discuss "Define scope of PMIx standard"
- https://github.com/pmix/pmix-standard/issues/182
- (Josh) Use Case gathering
- Will bring over wireup discussion, and some of the RFC use cases
- Once these are posted then we can reach out to others
- https://github.com/pmix/pmix-standard/issues
- (Josh) Create use case for wireup with PR template