RE: tungsten libraries

[Paul Angus <pa...@ticketmaster.com>]

Might be worth a comment in the commit pointing to the origin on the fork and the Apache license contained in it.  But I'd agree with Rohit.

Also - Can we remember not to cross-post private and public :thankyou:

Paul

-----Original Message-----
From: Rohit Yadav <ro...@apache.org>
Sent: Tuesday, January 24, 2023 10:30 AM
To: private@cloudstack.apache.org
Cc: dev <de...@cloudstack.apache.org>
Subject: Re: tungsten libraries

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 <da...@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,
>
>
This message is confidential and may be legally privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system; you must not copy or disclose the contents of this message or any attachment to any other person. We may monitor email traffic and the content of internal and external messages sent to and from us to ensure compliance with internal policies and for the purposes of security.

Ticketmaster UK Limited. Registered Office: 30 St John Street, London EC1M 4AY. Registered in England and Wales. Company Number 02662632.