General advice: It’s worthwhile reading the whole document at https://infra.apache.org/licensing-howto.html <https://infra.apache.org/licensing-howto.html> a few times until it’s all clear because these rules tend to take a while to “get”.
It’s also important to learn the difference between: “Category A" https://www.apache.org/legal/resolved.html#category-a <https://www.apache.org/legal/resolved.html#category-a> “Category B” https://www.apache.org/legal/resolved.html#category-b <https://www.apache.org/legal/resolved.html#category-b> and "Category X” https://www.apache.org/legal/resolved.html#category-x <https://www.apache.org/legal/resolved.html#category-x> In short: You can use licenses from the “a” list, but you might need notices depending on the license. Never use the “x” list. If we need something from the “b” list, it’s best to find something else, but if necessary it can be added to binary distributions (with appropriate mention). > On Dec 5, 2021, at 1:07 PM, Harbs <harbs.li...@gmail.com> wrote: > > Permissively licensed code can be included, but for MIT, we need to add a > pointer: > > https://www.apache.org/legal/resolved.html#category-a > <https://www.apache.org/legal/resolved.html#required-third-party-notices> > https://infra.apache.org/licensing-howto.html#permissive-deps > <https://infra.apache.org/licensing-howto.html#permissive-deps> > > > HTH, > Harbs > > P.S. I’ve been meaning to go through the code that was added and help from an > Apache policy perspective, but I haven’t found the time yet. If someone can > do that, it would be great! > >> On Dec 5, 2021, at 2:12 AM, Hugo Ferreira <hferreira...@gmail.com >> <mailto:hferreira...@gmail.com>> wrote: >> >> Hi, >> >> I just updated my local Git copy of Royale and saw the ExternJS folder with >> the tree component inside. >> This means that I can add other components ? >> What about the JS file and possible legal issues ? >> Perhaps use an external URL reference for this JS files. >> >> Regards, >> Hugo. >
