Skip to content

Meeting 2019 04 05

Jump to bottom
Josh Hursey edited this page May 9, 2019 · 1 revision 
        Josh Hursey (IBM)
	Thomas Naughton (ORNL)
	Shinji Sumimoto (Fujitsu)
	Kathryn Mohror (LLNL)
	Jim Garlick (LLNL)
	Nick Radcliffe (Cray)
	Sid Jana (EEHPC-WG | Intel)
	Barry Rountree (LLNL)
	Ken Raffenetti (ANL)
	Jithin Jose (Microsoft)
	David Solt (IBM)
	Swaroop Pophale (ORNL)
	Aurelien Bouteiller (UTK)
	Stephen Herbein (LLNL)
	Tom Scogland (LLNL)

Agenda

  • Discuss PMIx standardization process
    • Question: Timeline/Process: Proposal -> vote -> acceptance
    • Question: How to define voting rights and quorum?
    • Question: Implementation requirement
    • Process suggestion: pmix-standard
      • Move from RFC to a ticket based process
      • (0) Create a GitHub Issue for discussion on the idea
        • Link related PRs linked to it
        • For small items - no need for an Issue, go directly to a PR
          • Definition of “small” is somewhat flexible
          • Does it need large group discussion before drafting standard text
        • Create an Issue template
          • Describe the expectations for starting the discussion
          • Standard set of headings to fill in
      • (1) Post a Pull Request with standard text
        • PRs can be adjusted after posting
          • Post a new commit (no squash) so that the history is preserved
          • Discussion and iterative updates chronologically associated
          • If there is a competing or significantly different wording then a new PR can be created.
        • Suggest that we post a PR against pmix-standard for discussion (instead of a separate RFC process)
        • The PR as a ‘draft PR’ on GitHub while in this discussion/refinement stage
        • Need to preserve the use cases, examples, and thought process associated with the PR.
          • Add to the discussion on the PR presentations, and intermediate drafts of the document
        • Define a template for a PR? RFC structure?
          • Maybe add a checklist of “Don’t forget to update history” (etc.) Mark acceptance process
            • Mark the date of teleconf when accepted
          • Link to the reference implementation
          • Maintain all artifacts related to acceptance are immediately available on the ticket.
            • Record what the votes are - either on the PR or Issue on a Wiki or meeting page
      • (2) Once implementation is completed then RFC is marked as draft ready for review.
      • (3) Discussion occurs on RFC ticket/PR until a consensus is reached
        • Consensus process:
          • Need a direct link from the PR to the consensus discussion so that it is easy to see the discussion that happened on the teleconf and how the agreement was reached.
      • (4) Presented for discussion on the next teleconf - first review
      • (5) Presented for discussion on the following teleconf - second review
        • No objection then merged - both implementation and document
      • A question of how to mark the ‘stability’ of the interface once it is merged
        • Moving from experimental -> stable
    • Should we have companion documents for extended information regarding implementation details/options?
    • For PRs that need to be iterated upon by a working group - maybe flag the PR as not for broader consideration.
    • GH Issue with special label:
      • We need a forum for discussing a suggestion or issue without requiring standard language.
      • Could we start this as a GH Issue for discussion where folks can discuss options and refine the concept before moving to a formal PR to change the standard.
    • Clearly mark Optional features that are accepted to the standard
  • (Dave) Working group: Implementation agnostic document
  • (Stephen) Working group: Slicing/Grouping of functionality
  • (Josh) Wiki to collect use cases
  • Mailing list:

Action Items

  • (Josh/Kathryn) Copy the Google Doc notes to the wiki as weekly entries
    • Maybe target maintaining the minutes here during the meeting then copy them to the GH wiki afterward. Is there an easy way to do that?
  • (Stephen) Write up the current thoughts from this meeting on the standardization process:
    • Start a GH issue, and a PR to update the README
    • Contributing document

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally