It is ok to use external libs that are MIT licensed. The rules are stricter when it comes to taking code into ASF projects particularly when forking a full git repo.
On 2024/07/16 12:52:58 Michele Sciabarra wrote: > I do not think it is possible to ask this to hundreds of contributors for > the taskfile project. > The important thing is to know if we can use taskfile and its dependencies > as it is licensed with the MIT license. > > Dependencies can be kept outside, and I do not think it is something > unusual. Plenty of apache projects uses libraries for repos not under the > apache organization. > > Michele Sciabarra | CEO > > m: +44 747 984 8388 > e: [email protected] > l: https://linkedin.com/in/msciab > Nuvolaris Inc | 1209 Orange Street , Wilmington DE > www.nuvolaris.io [image: linkedin icon] > <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon] > <http://bit.ly/nuvtube> [image: twitter icon] > <https://twitter.com/NuvolarisIo> > > > On Tue, 16 Jul 2024 at 14:49, PJ Fanning <[email protected]> wrote: > > > If we want an Apache repo, we will need a Software Grant to be signed. The > > grant will also let us relicense our fork to use the Apache Software > > License. Ideally, we also need iCLAs to be signed by all significant > > contributors to the fork(s) and the original repos (prior to the point they > > were forked by us). > > > > On 2024/07/16 12:15:44 Michele Sciabarra wrote: > > > Hello, > > > > > > our cli tool, ops, uses Task (https://github.com/go-task/task) as > > execution > > > engine. > > > In turn Task uses mvdan shell as interpreter. > > > > > > They are MIT licensed so I checked with JB we can use it. > > > > > > They are used as libraries actually, and compiled in the cli as libraries > > > so it is not different than any other library in go. Also go libraries > > are > > > commonly forked and forks used. > > > > > > However since we had to do a few changes we forked it and changed the > > code. > > > I thought it would have been better to keep the fork in the codebase. But > > > we can keep outside if we need a "grant" to distribute the code. > > > > > > Please advise to the best course of action. > > > > > > > > > > > > > > > > > > Michele Sciabarra | CEO > > > > > > m: +44 747 984 8388 > > > e: [email protected] > > > l: https://linkedin.com/in/msciab > > > Nuvolaris Inc | 1209 Orange Street , Wilmington DE > > > www.nuvolaris.io [image: linkedin icon] > > > <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon] > > > <http://bit.ly/nuvtube> [image: twitter icon] > > > <https://twitter.com/NuvolarisIo> > > > > > > > > > On Tue, 16 Jul 2024 at 13:48, PJ Fanning <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > I noticed that a new git repo has been created. > > > > > > https://github.com/apache/openserverless-openserverless-mvdansh-fork.git > > > > > > > > As an aside, does it need to have openserverless in the name twice? > > > > > > > > My main question is whether the plan is to fork mvdan.sh? > > > > https://github.com/mvdan/sh > > > > > > > > The issue with this is that the original code is not Apache licensed > > and > > > > we would need a Software Grant to fork it and use inside an Apache > > project. > > > > > > > > https://www.apache.org/licenses/contributor-agreements.html#grants > > > > > > > > Regards, > > > > PJ > > > > > > > > > >
