We had an interesting lecture about open source projects today at work. So I went to Titanium github repository to check what kind of license Titanium is using, but could not find a definite answer.
The closest I see there is:
Commercial Support, Licensing
We give our software away for FREE! In order to do that, we have programs for companies that require additional level of assistance through training or commercial support, need special licensing or want additional levels of capabilities. Please visit the Appcelerator Website for more information about Appcelerator or email info#appcelerator.com.
But that's very vague. What about commercial applications? payed applications? does a developer has to open-source his application in order to meet OSS requirements by Titanium? What about OSS that Titanium itself uses?
Appcelerator Titanium Mobile
Copyright 2008-2013 Appcelerator, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
See the reference https://github.com/appcelerator/titanium_mobile/blob/master/LICENSE
Related
The license key purchase page is no longer available. Is this software no longer supported and unavailable for license purchase or is the software now free for commercial use.
We want to build a commercial product using SonarSource Community Edition which we deployed on our own servers, I am not able to find relevant information regarding its licensing faqs, can we create the product using it and sell it?
SonarQube Community Edition is licensed under the GNU Lesser GPL License v3, as you can read on the License page on sonarqube.org.
If you want to know what you can legally do with this LGPL v3 license, you can chek the following page: https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3)
Dears, while I am installing sybase ase 15.7, I install sysam license server, but I don't know now how to generate license (EE:enterprise)
by default, Sysam generates a license file in licenses directory but this license is developer edition,
anyone know about this point.
please advice
You need to get to the Sybase (now SAP) web site, log in with your customer ID and geneate the license key. This is possible only when you have actually purchased the ASE Enterprise Edition. If you (or your company) did, but you don't know how to log in, contact SAP support to help you forward.
On the Visual Studio 15 CTP download page, it says this:
This release is unsupported and are not intended for use on production computers, or to create production code. We strongly recommend only installing this release in a virtual machine, or on a computer that is available for reformatting.
So... why can't I install it on a production machine? I'm not talking about creating production code (obviously not that!). But I can't even install it?
Is this because all pre-release software tends to come with the "it might explode your PC" caveat? Or is there something more to it, like the new compiler is just unable to live side-by-side with the old one from VS 2013?
The "we strongly recommended only installing this release in a VM, or on a computer that is available for reformatting" warning falls into the "it might explode your PC" bucket. However, that said, this release does not have a Go-Live license (which is different).
What is this Go-Live thing?
The license terms for Visual Studio pre-releases come in 2 buckets - Go-Live and, well, not Go-Live. The terms for a Go-Live license are basically the same as the released product: some amount of support (though not the full MS 10-year support policy), and no specific restrictions on what you do with your projects created with that prerelease build. Go-Live licenses are generally used for the RC releases that come shortly before general availability (aka RTM).
However, a non Go-Live license (such as the one applicable in this case) has the following clauses (emphasis added):
INSTALLATION AND USE RIGHTS.
•You may install and use any number of copies of the software solely for evaluation purposes to design, develop and test your programs. If you use the software on Microsoft Azure, additional charges and terms may apply.
•You may not deploy or distribute any program you design or develop with the software, except that you may deploy your programs internally solely to evaluate any deployment technologies contained in the software.
•You may not test the software in a live operating environment or public website unless Microsoft permits you to do so under another agreement.
Based on these restrictions, the recommendation is more strong that you don't install these on a production machine as it is solely intended for evaluation purposes.
I have been looking at whether our MSDN Premium Subscriptions would cover upgrading our developer’s machines from Vista OEM to Win 7 RTM MSDN.
The assumption here is that "design, develop, test, or demonstrate" covers the developer’s day job, so should cover the OS.
I have found that other development shops seem to make this same assumption.
Having looked at the MSDN Subscription Software Use Rights page this does not seem to be the case.
from the page :
"Many MSDN subscribers use a computer for mixed use—both design, development, testing, and demonstration of your programs (the use allowed under the MSDN Subscription license) and some other use.
Using the software in any other way, such as for doing email, playing games, or editing a document is another use and is not covered by the MSDN Subscription license.
When this happens, the underlying operating system must also be licensed normally by purchasing a regular copy of Windows such as the one that came with a new OEM PC"
So if you are not using the operating software install to purely "design, develop, test" read "use your visual studio license" and you answered a company email you are in violation of the license.
Is this indeed the case?
Is there a way that MSDN OS licenses can cover your day to day dev machine?
Did you make the same assumption as I did?
Yes that's the case. No you can't change the license.
MSDN license has always been a "technical" license that restricts the usage to development "sandbox" only. Your primary workstation must be covered by a regular non-dev license. Although I heard of some shops that (purposefully or not) violate this license and are very happy with the savings.
Based on this document the accepted answer no longer appears to hold true (at least for licensed users of Visual Studio Enterprise with MSDN).
Relevant excerpt (p13) says:
Production use of Office Professional Plus 2016
Office Professional Plus 2016 can be used by licensed users of Visual Studio Enterprise with MSDN or Visual Studio Enterprise – annual on
one device for production use
From this page the Office Professional Plus SKU contains Outlook, and although IANAL it would seem that use of Outlook is now allowed with an MSDN subscription.
With regard to the underlying OS this remains excluded. The relevant text from the licensing document says:
When there is mixed use the underlying operating system must be licensed normally by purchasing a regular copy of Windows such as the
one that came with a new OEM PC.