I don't know if this violates any rules, as far as I both the fork repo is under valid apache license.
The standard process is to publish the jar in a public maven repo. Can this be done and we refer to the dependency like other dependencies? Regards. On Mon, 23 Jan 2023 at 13:43, Daan Hoogland <d...@apache.org> wrote: > LS, > > TL;DR we are about to merge a reference to a dependency in a (privare) > fork of an apl2 licensed project. > We are planning to merge the (backend-) plugin for tungsten in the coming > days. If regression tests show no big failures of course. There is one > issue I want devs and PMCs opinions on. Please see our esteemed comment on > the subject [1]. > Do we find including a dependency this way acceptable? I personally have > no problem with it but want to make sure I am not violating any laws, > by-laws or feelings with merging it like this. > We are still doing regression tests in advanced zon with security groups > for this, and lazy consensus applies. > Please be heard if you see a reason not to do this. > > [1] https://github.com/apache/cloudstack/pull/7065#issuecomment-1398857494 > > thanks, > >
