<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">Now that we’ve settled on the license legalese to get to, we need to start the process of relicensing. We’re still sorting through all of the details of what this will take, but the first step is clear: new contributions to LLVM will need to be under both the old license structure and the new one (until the old structure is completely phased out). From a mechanical perspective, this is pretty simple, but I want to make sure that the community is aware of this and has time to digest and discuss any concerns.</div><div class=""><br class=""></div><div class="">In order to spell out what this will look like, we’ve gone ahead and revised <a href="http://llvm.org/docs/DeveloperPolicy.html" class="">http://llvm.org/docs/DeveloperPolicy.html</a> to reflect what the new structure will look like. While the license text is the canonical truth, the DeveloperPolicy serves a few purposes: it explains to non-lawyers what the license means, provides rationale for the design, and deals with relicensing process topics.</div><div class=""><br class=""></div><div class="">I’ve attached a draft of the revised document below. Please take a look and let me know if anything should be further clarified or if you have any other questions and comments. Thanks!</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div><div class=""></div></body></html>