I requested a document number (P2566) and moved the document contents to
GitHub where it can now be found here
<https://github.com/tahonermann/std-proposals/blob/master/d2566r0.html>.
A rendered view can be found here
<https://rawgit.com/tahonermann/std-proposals/master/d2566r0.html>
courtesy of rawgit.com.

Pull requests are welcome! Please add yourself as a co-author in any PRs
as you wish.

I intend to leave the document in a draft status for now pending
additional feedback.

Tom.

On 3/8/22 12:52 PM, Tom Honermann via SG15 wrote:
>
> Yes. I started with a Google Doc to make early collaboration as low
> overhead as possible. Once comments there have settled down, I'll move
> it to a Github repo and provide a link.
>
> Tom.
>
> On 3/7/22 12:01 PM, Gabriel Dos Reis via SG15 wrote:
>>
>> +1.
>>
>> Would this eventually turn into some form of paper in a github repo
>> against which one could submit a pull request and track diffs?
>>
>> -- Gaby
>>
>> *From:* SG15 <sg15-bounces_at_[hidden]> *On Behalf Of *Peter
>> Brett via SG15
>> *Sent:* Monday, March 7, 2022 1:46 AM
>> *To:* sg15_at_[hidden]
>> *Cc:* Peter Brett <pbrett_at_[hidden]>
>> *Subject:* Re: [SG15] Modules Build System Scenarios
>>
>> Hi Tom,
>>
>> This is a really helpful document – thank you.
>>
>> I hope it will eventually become a paper!
>>
>> Peter
>>
>> *From:* SG15 <sg15-bounces_at_[hidden]> *On Behalf Of *Tom
>> Honermann via SG15
>> *Sent:* 05 March 2022 07:10
>> *To:* sg15_at_[hidden]
>> *Cc:* Tom Honermann <tom_at_[hidden]>
>> *Subject:* [SG15] Modules Build System Scenarios
>>
>> EXTERNAL MAIL
>>
>> Following the 2022-03-05 SG15 telecon, I decided to make an attempt
>> at describing the various build system scenarios we've been
>> discussing. Please see the following Google doc.
>>
>> * https://docs.google.com/document/d/1JWW7Q-94nx6ObpupePkA2NAER7rylJQZpw4t755aeZQ/edit?usp=sharing
>> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fdocs.google.com%2Fdocument%2Fd%2F1JWW7Q-94nx6ObpupePkA2NAER7rylJQZpw4t755aeZQ%2Fedit%3Fusp%3Dsharing__%3B!!EHscmS1ygiU1lA!T1BZbJU6vg_Hgs1GtJ0QI56F9Fve5gJaJxC6_G6EnDN-KVn1vWy4h7V3PgZNJw%24&data=04%7C01%7Cgdr%40microsoft.com%7C8d8ee3a692064238ffc308da001f473f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637822431600767036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=k2dq4lkvgRIL4s4UBRMuhSw8KvlT3iV2t4cNXdJZSKQ%3D&reserved=0>
>>
>> Please feel free to edit the doc or add comments to it; the doc is
>> publicly shared.
>>
>> I know Google Docs is not convenient or even accessible to everyone.
>> If you are not able to view the doc, let me know and I'll send a copy
>> as an attachment. For now, I'm hoping that collaborative editing will
>> help fill in gaps and correct mistakes and misunderstandings.
>>
>> The solution sections are vague and, for the last scenario, probably
>> unrealistic. I just wanted to include something as a starting point.
>>
>> Tom.
>>
>>
>> _______________________________________________
>> SG15 mailing list
>> SG15_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg15
>
> _______________________________________________
> SG15 mailing list
> SG15_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg15