Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
11–20 of 305 posts
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#12Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#13Having been on the receiving end of competitors running 'benchmarks' on a service I worked on, and the trumpeting the very contrived and out of context figures, I can understand why Atlassian is trying to prevent it from happening to them.
Pity that it probably won't work.
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#14>you will not and you have no right to: ... (f) perform or publish any benchmark tests or analyses relating to the Cloud Services without Cloudflare’s written consent;
https://www.cloudflare.com/terms/#react-modal:~:text=(f)%20p...
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#15(i) publicly disseminate information regarding the performance of the Cloud Products;
But can we take a minute to talk about the combination of these two :
(h) use the Cloud Products for competitive analysis or to build competitive products;
(j) encourage or assist any third party to do any of the foregoing.
Does this mean as a jira user I can’t help build a jira competitor for a client of mine ( we are a tech agency). If this is the case I would really have a hard time using jira and being compliant. After all, who is the arbiter on what jira is exactly?But does this also mean people can’t do reviews on the platform as means to compare to other platforms? I’m a bit speechless here, it’s a wtf sort of thing.
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#16Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#17The most innocent explanation is preventing benchmarks against similar tools which could be unflattering. Though the only other company that resorts to such insecure measures is Oracle.
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#18------------------------------------------------------
Section 3.3: Benchmarking Can you explain Atlassian's stance on Benchmarking?
Like many other software companies, Atlassian has this language in its terms to protect users from flawed reviews and benchmarks. By requiring reviewers to obtain Atlassian’s consent before publicly disseminating their results, Atlassian can confirm their methodology (i.e. latest release, type of web browser, etc.) and make sure they deliver verifiable performance results. Atlassian is not trying to prevent any users from internally assessing the performance of our products.
The language related to the public distribution of performance information has been included in our customer agreement since 2012.
Customers can obtain Atlassian's consent by filing a Support ticket. The Support engineer will then need to bring in a PMM for approval of the data/report.
------------------------------------------------------
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#19You have product X, and your competitor Y publishes whitepapers and ads comparing their performance to yours, showing yours is terrible. You think they rigged the tests, and want to publish your own X vs. Y comparison but Y's TOS prohibits it.
Once one major Y does this, many others follow suit as a defensive measure against Y.
I seem to recall seeing some where X's TOS would try to limit the prohibition to just that situation, such as saying that you could only publish X vs. Y performance comparisons if either there were no restrictions on others publishing Y performance comparisons or Y granted X an exception to Y's prohibition.
Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
#20This is what happens when the "clueless" start "innovating". I've had several conversations over the years with members of Atlassian technical teams. They always wanted to work on performance, but never allowed (priorities).
They are in "good" company (Oracle, China, etc.). What's preventing anonymous performance benchmarks, though?