Hi, forgive me, but I've had a few days of vacation and I just read the post.
The ExternsJS folder, was Alina's first commit but she was supposed to check the licenses, as Harb told her. Anyway, I think the one we should take forward is in the "feature/ExternsJS_InspireTree" branch (I created it to be able to work comfortably without interfering with the SDK compilation until we were clear how we should configure the pom's/builds...). We have to decide whether to create a single ExternsJS.swc or a swc for each of the Js libraries that we include. I seem to remember that Harb commented that, perhaps, it would be good to separate each JS in a swc. I don't know about the licensing issue, I think Alina was going to look into it with the information Harb gave her but I don't know how far she got. I, for my part, updated almost all the files, because the version that had been uploaded was not the latest. Where do I go from here, independent SWC? Hiedra -----Mensaje original----- De: Hugo Ferreira <[email protected]> Enviado el: domingo, 5 de diciembre de 2021 13:14 Para: Apache Royale Development <[email protected]> Asunto: Re: ExternsJS library Thank you. When I get time, I will migrate my 2 components Microsoft Office Add-In and Stimulsoft Reports Engine (Viewer and Designer) to ExternJS project. New components I will add directly to this new project. Harbs <[email protected]> escreveu no dia domingo, 5/12/2021 à(s) 11:22: > 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 <[email protected]> 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-notice > s> > > 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 <[email protected] > <mailto:[email protected]>> 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. > > > >
