Comments (15)
@mihaitodor @relistan I've been working on this with @nehaduggal . I understand the challenge folks are having with the language in the current license and had another conversation with our legal team. We were able to adjust the language so that it isn't as restrictive. This change has been merged into the build for the upcoming release (coming in the next few weeks).
Sorry about the wait! Let me know if you have any questions.
from go-agent.
Still working on it, @relistan. I'm targeting early next week to have an update for you.
from go-agent.
Update: We pushed out v1.10 of the agent today and it contains the license update (along with a few other things).
from go-agent.
I should point out that these clauses are not present in at least two other agents:
- the Ruby agent: https://github.com/newrelic/rpm/blob/master/LICENSE
- the Node agent: https://github.com/newrelic/node-newrelic/blob/master/LICENSE
The changes in the Go agent license appear to have been intentionally introduced here
from go-agent.
@relistan - thanks for the feedback on the license. I'm discussing this with our Legal team.
from go-agent.
@victorNewRelic awesome, thanks!
from go-agent.
Any update here @victorNewRelic?
from go-agent.
Thanks @victorNewRelic
from go-agent.
Hi @relistan,
We've talked this through internally and we feel the existing terms are still aligned with our requirements. The intent of those terms is to make sure the New Relic Go agent is used only with the New Relic services, whether paid or "Lite" subscriptions. In the case where your subscription lapses, the subscription reverts to "Lite" so youβre fine.
Your situation with regards to the license limiting what you can do with your open source project presents a different kind of use case. At the end of the day, what you need is for all your library dependencies to be compliant with your project's license. New Relic's license will not be broadly compatible with open source licenses because of the provision that the Go agent only be used in conjunction with New Relic services. I wonder though, would an open source project want to include vendor specific instrumentation?
I'm a huge fan of open source authors including instrumentation in their projects and there's a way that folks can do that with OpenTracing without tying their projects to specific vendor implementations or licenses. New Relic doesn't support OpenTracing yet though.
Thanks,
-Victor
from go-agent.
Hi Victor. Thanks for reviewing but I think you guys missed the point of the argument. The main thing is that this prevents anyone from using the agent at all:
These files and their contents shall not be used in conjunction with any other
product or software, including but not limited to those that may compete with
any New Relic product, feature, or software.
The way this is worded, you cannot even use it compiled with any another library. That doesn't make sense. "In conjunction with" has the same legal definition that it does in plain English. This license prevents you from using the agent with anything at all.
Secondly, in our case we need to run a piece of software that is licensed with the AGPL. This requires that you open source any modifications to the software. Since we'd be instrumenting it with the Go agent, thus modifying it, we'd have to open source it. But we can't open source it under the terms of the New Relic agent license because anyone who uses it still has to register with New Relic to get a Lite subscription. This wouldn't comply with AGPL.
Third, in the case of general open source: it's not a problem at all to have New Relic instrumentation in a service as long as the instrumentation can be disabled. I'm not sure why you guys think that's a problem? Lots of things have instrumentation in them that people don't use. The problem with the license in this case is that it doesn't distinguish between compiling against the library and using the service. Which I believe are entirely separable (per, for example, Node and Ruby agents).
from go-agent.
@victorNewRelic Any response on this yet? I spoke with @benders who I believe was under the impression that there was some motion here. We're blocked on this, and honestly all of your customers should be blocked on this if they were to read the license.
from go-agent.
@victorNewRelic if you guys aren't going to take action it would be good to know that for sure so we can give up on the Go agent. I'd rather get resolution instead, but either way an update would be great.
from go-agent.
@relistan I am sorry for the delay in responding while we continue to work on this. The terms you mentioned were put in the agreement to prevent misuse of our code. It was never our intention to confuse folks with our language.
Use of this agent has presented use cases that we had not foreseen and not considered when we initially drafted the license. We are working with our legal team on clarifying the language and getting you a license that will work for your use case.
from go-agent.
@nehaduggal @victorNewRelic Is there any update on this? It's been almost 6 months since this issue was raised and it would be good to know if we should expect to be able to use this NewRelic agent in production anytime soon. Thank you!
from go-agent.
@vinhnewrelic Thanks! Looking forward to a saner license!
from go-agent.
Related Issues (20)
- Update google.golang.org/grpc from 1.54.0 to 1.56.3 HOT 2
- transaction.go reqBody(req *http.Request) turn nil body into non Nil body for request.Body == http.NoBody HOT 1
- Add support to CopyFrom method in pgx integration HOT 1
- fmt.Stringer support for user attributes (especially for SQL query parameters)
- UNKNOWN log levels when using the native log package HOT 2
- `.Ignore()` not ignoring transaction (go-agent + nrgin) HOT 6
- Integration for gqlgen HOT 2
- nrpgx5 data-race HOT 5
- Changelog Go agent EOL Policy link is broken HOT 1
- agent with nrzap is not forwarding logs to newrelic HOT 3
- WrapBackgroundCore background logger is not sending logs to new relic but transaction logger is HOT 12
- zap logger.With log message properties are not sent to new relic HOT 4
- Attributes are not forwarded to NewRelic for logs HOT 22
- go agent , but not see span, please help me ,thanks HOT 3
- Specify service version during initial newrelic configuration HOT 6
- Possible memory leak in Go agent HOT 11
- How to use AWS Lambda Web Adapter in golang app
- uber/zap WithField(...) not showing up in NR APM logs HOT 3
- potential bug in newAppRun HOT 2
- protobuf is deprecated HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-agent.