<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 2, 2017 at 10:58 PM, Xiaodi Wu <span dir="ltr"><<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><span class="">On Wed, Aug 2, 2017 at 21:55 Taylor Swift <<a href="mailto:kelvin13ma@gmail.com" target="_blank">kelvin13ma@gmail.com</a>> wrote:<br></span><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Swift Breeze <a href="https://github.com/swift-breeze" target="_blank"><i>was</i> on Github</a>,, i don’t know whose argument that strengthens here :)</div></div></blockquote><div dir="auto"><br></div></span><div dir="auto">No, no, I mean, doesn't GitHub itself fit the roles you defined earlier? And by implication, why would a project on GitHub do any better than GitHub itself at being a collection of repositories and at facilitating collaboration?</div></div></div>
</blockquote></div><br></div><div class="gmail_extra">Github is a big ocean, sis. Swift libraries would benefit from having a smaller grouping that’s just Swift libraries. That’s not to say cross-community collaboration isn’t beneficial — my library <a href="https://github.com/kelvin13/noise">Noise</a> benefited greatly from working with its counterpart in the Rust community, but Swift libraries do need their own space.<br></div></div>