No, we are not special.

That said, if the review is purely to integrate what we already discussed and approved and the review contents are purely editorial, then a github review sounds good to me.  If we were to do more than that, then usual operational rules apply.

-- Gaby

From: SG15 <sg15-bounces@lists.isocpp.org> on behalf of Ðí´«Ææ(Ò¹µÆ) via SG15 <sg15@lists.isocpp.org>
Sent: Tuesday, August 29, 2023 7:16:48 PM
To: Daniel Ruoso via SG15 <sg15@lists.isocpp.org>
Cc: Ðí´«Ææ(Ò¹µÆ) <chuanqi.xcq@alibaba-inc.com>
Subject: Re: [SG15] P2898R1 - Build System Requirements for Importable Headers
 
Not specifically for this proposal, I prefer to review on Github, , as it would make our work more transparent to people outside of WG21. I know there are policies in WG21. I am just wondering if SG15 is special. (e.g., the mail list of sg15 is more visible than other mail lists)

Thanks,
Chuanqi

------------------------------------------------------------------
From:Daniel Ruoso via SG15 <sg15@lists.isocpp.org>
Send Time:2023 Aug. 30 (Wed.) 03:10
To:sg15 <sg15@lists.isocpp.org>
Cc:Daniel Ruoso <daniel@ruoso.com>
Subject:[SG15] P2898R1 - Build System Requirements for Importable Headers

Hi,

We discussed this paper in Varna, and we had significant progress.

I have a PR on the modules ecosystem TR draft to incorporate the items we discussed.


To the best of my knowledge this is essentially just encoding the consensus we achieved in that meeting.

Do you all think we should have a meeting to review it? Or is the review in GitHub itself sufficient?

Daniel