<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 9, 2017 at 12:37 PM, Wallacy via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><span class=""><div dir="ltr">Em qui, 9 de nov de 2017 às 03:42, Ted Kremenek <<a href="mailto:kremenek@apple.com" target="_blank">kremenek@apple.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">These are some really interesting analogies. How would you imagine the community “governance” of these “plugins” (which I assume would be libraries or packages) to be managed? </div></blockquote><div> </div></span><div><div>Pretty much like a TV/Games/etc community forums. The owner (In this case Apple/Core Team) invite some people to help (Moderators etc) to maintain the main project, look if everyone is follow the rules, etc. </div><div><br></div><div>Also is similar as other opensource projects.</div></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">What does it mean for the “full community” to manage them, and provide the rough guarantees you suggest?</div></blockquote><div><br></div></span><div>NPM has thousands of projects, is impossible to check all of then. And besides be a good reference, here we have the opportunity do to something better... Because...Because...Because I believe we can ;)<br></div><div><br></div><div>So what i expect?</div><div><br></div><div>Lets make some assumptions here, just to play a little:<br></div><div><br></div><div>Let assume we build a Indexer like IBM Swift Package Catalog ( <a href="https://packagecatalog.com/" target="_blank">https://packagecatalog.com/</a> ) over Swift.org.<br></div><div><br></div><div>And like Swift Source Compatibility Suite to be "indexed" the author of the project needs to send the request to be accepted.</div><div><br></div><div>Lets assume the same rules as Compatibility Suite:</div><div><h3 style="box-sizing:border-box;margin-top:24px;margin-bottom:16px;font-size:1.25em;line-height:1.25;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol"">Acceptance Criteria</h3><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px">To be accepted into the Swift source compatibility test suite, a project must:</p><ol style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px"><li style="box-sizing:border-box">Target Linux, macOS, or iOS/tvOS/watchOS device</li><li style="box-sizing:border-box;margin-top:0.25em">Be an <i style="box-sizing:border-box">Xcode</i> or <i style="box-sizing:border-box">Swift Package Manager</i> project (Carthage and CocoaPods are currently unsupported but are being explored to be supported in the future)</li><li style="box-sizing:border-box;margin-top:0.25em">Support building on either Linux or macOS</li><li style="box-sizing:border-box;margin-top:0.25em">Be contained in a publicly accessible git repository</li><li style="box-sizing:border-box;margin-top:0.25em">Maintain a project branch that builds against Swift 3.0 compatibility mode and passes any unit tests</li><li style="box-sizing:border-box;margin-top:0.25em">Have maintainers who will commit to resolve issues in a timely manner</li><li style="box-sizing:border-box;margin-top:0.25em">Be compatible with the latest GM/Beta versions of <i style="box-sizing:border-box">Xcode</i> and <i style="box-sizing:border-box">swiftpm</i></li><li style="box-sizing:border-box;margin-top:0.25em">Add value not already included in the suite</li><li style="box-sizing:border-box;margin-top:0.25em">Be licensed with one of the following permissive licenses:<ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:0px"><li style="box-sizing:border-box">BSD</li><li style="box-sizing:border-box;margin-top:0.25em">MIT</li><li style="box-sizing:border-box;margin-top:0.25em">Apache License, version 2.0</li><li style="box-sizing:border-box;margin-top:0.25em">Eclipse Public License</li><li style="box-sizing:border-box;margin-top:0.25em">Mozilla Public License (MPL) 1.1</li><li style="box-sizing:border-box;margin-top:0.25em">MPL 2.0</li><li style="box-sizing:border-box;margin-top:0.25em">CDDL</li></ul></li></ol></div></div></div></blockquote></div>i’m okay with this as long as point 9 is changed to accept copyleft licenses like GPL. currently this is a huge hole in the SSCS which i am sure will cause issues down the road<br></div></div>