[VOTE] Vote to decide on production of a new PRIF revision

[Katherine Rasmussen]

Hello all,

     After the vote passed to adopt changes to prif_deallocate_coarray(s), the technical content on the main branch of the prif repository has been updated. I have been asked by a Committee member to hold a vote on producing a new revision and in accordance with the PRIF governance, this email announces the PRIF Committee vote on a new revision and the technical content to be included.

      Vote: Do you support a new revision (revision 0.7) to be produced with the technical changes that are staged on the main branch of the prif repository? (The latest commit on the main branch at the time of the commencement of the vote is commit hash 101eba9ad35ea988365875a611b875a548c1cf47).

Please note, this vote is only on the technical changes that will be added to revision 0.7. If this vote passes, any non-normative changes that are required for a new revision will be discussed in PR and do not require formal votes. 

Please note, if this vote passes, a candidate document will be produced with all changes, both technical and non-normative, and a comment period will commence before the revision is published. 

      The decision to produce a new revision with the current staged technical changes must receive approval from 50% of votes (excluding explicit abstentions) to be ratified. Only PRIF Committee members may vote and the options are Yes, No, or Abstain. This vote will remain open until 5 PM (Pacific Time) on Tuesday, November 11th. In order to register your vote, please reply all to this email and state your vote. If voting against, then your vote must include comments that explain your rationale.

Thank you for your time,

      Kate Rasmussen

      Lawrence Berkeley National Laboratory

      PRIF Community Lead

[Richardson, Brad (JSC-EG311)[AMENTUM TECHNOLOGY, INC]]

I vote Yes.

Regards,

Brad

From: prif...@googlegroups.com <prif...@googlegroups.com> on behalf of Katherine Rasmussen <krasm...@lbl.gov>
Date: Tuesday, October 28, 2025 at 12:21 PM
To: PRIF Specification <prif...@googlegroups.com>
Subject: [EXTERNAL] [BULK] [PRIF-spec] [VOTE] Vote to decide on production of a new PRIF revision

CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC.

--
You received this message because you are subscribed to the Google Groups "PRIF Specification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prif-spec+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/prif-spec/CAGM9fz0sWDw6vXvedpU%3DGzGfmz11Ny57okUViN%3Du5YAOyyOmeg%40mail.gmail.com.

[Jean-Didier Pailleux]

I vote Yes

Jean-Didier

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/SA1PR09MB11178E1609BD5A905E2C5A64EB7FDA%40SA1PR09MB11178.namprd09.prod.outlook.com.

[etienne renault]

I vote YES.

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/CANWWDrf2fUjLyZvFw6fXRFermoPuU-mBhoTYKJ56hOXjPN4X%2BQ%40mail.gmail.com.

--

-------------------------
Renault Etienne
-------------------------

[Dan Bonachea]

I vote NO on the motion to ratify the current technical content in main, and encourage other committee members to change their vote to NO before the deadline on Tuesday .

Rationale:

PRIF issue #145 documents a PRIF integration challenge we've encountered with flang, which is technically already a problem for the current LLVM PR 165573 that upstreams TEAM features into flang. Due to happy coincidence, this is not expected to cause observable misbehavior for the TEAM feature. However it *is* expected to cause observable integration problems once we endeavor to upstream PRIF support for EVENT, NOTIFY, LOCK and CRITICAL into flang.

PRIF PR #146 demonstrates a proposed solution for the problem, which adds a few additional and reasonable constraints on PRIF-specified types. The Caffeine implementation already abides by these constraints, but formally including them in the PRIF specification ensures compilers can safely rely on these properties and be assured they will remain valid for any compliant PRIF library implementation. I believe this is important enough to justify delaying ratification of PRIF 0.7, to ensure this important improvement can be incorporated into the working draft.  Once that process is complete, then we can start a new PRIF 0.7 ratification vote.

Dan Bonachea
PRIF Technical Lead
Lawrence Berkeley National Laboratory

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/CAF6i2zzoPijUWb8axOA27%2BTFGePtoHFugOGmPP8PTqRQ3OoYVQ%40mail.gmail.com.

[Jean-Didier Pailleux]

I vote NO.

 

Jean-Didiier

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/CAJTO8-YvMhV8hMcbm7HBsA-g3LMvhMhOLoAHOObQO%3DoeKx_QoA%40mail.gmail.com.

[Katherine Rasmussen]

Thank you Jean-Didier for updating your vote. As a reminder, according to the PRIF Committee governance, when voting "No", you must give rationale for the vote. Can you please reply again to this thread and state your rationale?

Thank you for your time,
      Kate Rasmussen
      Lawrence Berkeley National Laboratory
      PRIF Community Lead

[Katherine Rasmussen]

I vote NO to produce a new revision at this time. My rationale is that the concerns in PRIF issue #145, which Dan describes in detail above, should be resolved before producing a new revision.

Kate Rasmussen

[Jean-Didier Pailleux]

Hi, sorry for forgetting my rationale

I vote NO to produce a new due to the details described in issue #145 because it must be considered in the new revision of PRIF.

 

Jean-Didier

[Richardson, Brad (JSC-EG311)[AMENTUM TECHNOLOGY, INC]]

I will change my vote to NO so that we can discuss a solution to #145 before the next revision is published.

Brad

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/bbca96945967436a8a640a6679cc70bf%40sipearl.com.

[etienne renault]

Based on the previous answer i vote NO to have the opportunity to discuss this topic further. 

To view this discussion visit https://groups.google.com/d/msgid/prif-spec/SA1PR09MB11178B9D33673E1ED549A7F4FB7C3A%40SA1PR09MB11178.namprd09.prod.outlook.com.