<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Aug 22, 2018, at 11:11 AM, JF Bastien <<a href="mailto:jfbastien@apple.com" class="">jfbastien@apple.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class=""><div class=""><ul class=""><li class="">Create a new repository, under the LLVM Foundation, to host Parallel STL work. This includes an implementation which can support multiple backends, correctness tests, and performance tests.</li><li class="">This repository will be importable into <a href="https://libcxx.llvm.org/" class="">libc++</a> and <a href="https://gcc.gnu.org/onlinedocs/libstdc++/" class="">libstdc++</a>. Details will be worked out later as this will be experimental for a while.</li><li class=""><span class="" style="background-color: rgba(255, 255, 255, 0);">Contributions occur as usual, under </span><a href="https://llvm.org/docs/Contributing.html" class="" style="background-color: rgba(255, 255, 255, 0);">LLVM’s contribution policy</a> (specifically, the <a href="http://llvm.org/foundation/relicensing/devpolicy.patch" class="">revised</a><a href="http://llvm.org/foundation/relicensing/devpolicy.patch" class=""> policy</a>)<span class="" style="background-color: rgba(255, 255, 255, 0);">.</span></li><li class="">New mailing lists will be created for the project (<font face="Courier New" class="">pstl-dev@</font><span class="Apple-converted-space"> </span>and<span class="Apple-converted-space"> </span><font face="Courier New" class="">pstl-commits@</font>), as well as new bugzilla components, and associated Phabricator setup.</li></ul></div></div></div></div></blockquote><br class=""></div><div class="">One specific question I’d like to see considered: we’re talking about splitting libc++ off to its own mailing list now. Does it make sense for pstl to share that list, or should we add two new lists?</div><div class=""><br class=""></div><div class="">Besides the seeming alignment between the two projects, this would encourage collaboration across the code bases and would reduce spam moderation burden.</div></div></div></blockquote><br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">Tom and Mikhail might know better: they likely only want emails from pstl, which is why I suggested having its own list. The new libc++ lists should be fairly low traffic, and I agree with you that it might help with some extra collaboration. I’m OK with either.</div></div></blockquote></div><br class=""><div class="">I know that people generally prefer to get as little email as possible, but I prefer to push teams together when practical instead of building islands.</div><div class=""><br class=""></div><div class="">Beyond that, moderating a mailing list is a nontrivial amount of effort and involves getting a lot of email, so I’m not sure that they’d actually end up with less net emails ;-)</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div></body></html>