<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Jun 6, 2018 at 4:29 PM Ben Craig <<a href="mailto:ben.craig@ni.com">ben.craig@ni.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_4124140526117238729WordSection1">
<p class="MsoNormal">I’ve heard some off-list questions about what wg21 can and cannot do, particularly when it comes to things regarding package management. I’m hoping to get some clarifications here.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>Does wg21 (and SG15) have the authority to produce a specification for a package / dependency manager?</b></p></div></div></blockquote><div><br></div><div>Specification? Perhaps.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_4124140526117238729WordSection1">
<p class="MsoNormal"><b>What if the package manager isn’t just a C++ package / dependency manager, but a general purpose package / dependency manager?</b></p></div></div></blockquote><div><br></div><div>Again, if it's specification.</div><div><br></div><div>Practically speaking, I expect SG15 to be primarily a clearinghouse for discussion between the community and the committee on questions of tooling and ecosystem - the output from SG15 may primarily be standing documents, position papers, etc, and very little of the normal WG21 output (specification). </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_4124140526117238729WordSection1">
<p class="MsoNormal">(BIG NOTE: I am not asking if wg21 and sg15 have the time or the willingness. I’m just asking if it is allowable. I don’t expect the time or willingness questions to be answerable on the mailing lists.)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Here’s a relevant note from the ISO Code of Conduct ( <a href="https://www.iso.org/files/live/sites/isoorg/files/publications/en/pub100397.pdf" target="_blank">
https://www.iso.org/files/live/sites/isoorg/files/publications/en/pub100397.pdf</a> )<u></u><u></u></p>
<p class="MsoNormal">“Agree to a clear purpose and scope: We are committed to having a clear purpose, scope, objectives and plan to ensure the timely development of International Standards.”<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Do we need to agree somewhere as to what the scope of wg21 is, or has that scope been agreed upon and set in a standing document somewhere?<u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="http://www.open-std.org/mailman/listinfo/tooling" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
</blockquote></div></div>