Hi,
i have a question regarding the Telerik Licence Agreement. Especialy for this passage:
The SOFTWARE may not be distributed as part of products that have the same or substantially the same primary functionality as the SOFTWARE. (Example for RadControls for ASP.NET: you may purchase TELERIK RadEditor for ASP.NET and create a blog application/component. However, you cannot wrap RadMenu and offer it as a SharePoint WebPart or DNN menu skin object, since its primary functionality would be substantially the same as the SOFTWARE).
What does it mean?
Let's say if i purchase the normal Developer Licence without Source Code Subscription. I'm not able to build a webpart in Sharepoint which is using one of the Telerik Controls to extend one of the build in features (For example Navigation)?
Can you please clarify this for me?
Thx a lot and sorry for my poor english :)
best regards from Germany
Pascal
i have a question regarding the Telerik Licence Agreement. Especialy for this passage:
The SOFTWARE may not be distributed as part of products that have the same or substantially the same primary functionality as the SOFTWARE. (Example for RadControls for ASP.NET: you may purchase TELERIK RadEditor for ASP.NET and create a blog application/component. However, you cannot wrap RadMenu and offer it as a SharePoint WebPart or DNN menu skin object, since its primary functionality would be substantially the same as the SOFTWARE).
What does it mean?
Let's say if i purchase the normal Developer Licence without Source Code Subscription. I'm not able to build a webpart in Sharepoint which is using one of the Telerik Controls to extend one of the build in features (For example Navigation)?
Can you please clarify this for me?
Thx a lot and sorry for my poor english :)
best regards from Germany
Pascal
4 Answers, 1 is accepted
0
ManniAT
Top achievements
Rank 2
Rank 2
answered on 26 Apr 2009, 11:53 AM
Hi Pascal,
in simple words this particular part of the agreement means that you have to build an own thing.
Or in other word - you are not allowed to distribute the software in a way where it adds only some "shell around" but keeps to be the same as it is in original.
In this sample:
YES - build your "blogging engine" which uses RadEditor
NO - build a menu (navigation) component which offers (almost) the same as RadMenu to the enduser.
For better understanding - the last part in german:
Du darfst nichts machen, was nur eine "Ableitung" der RadControls ist.
Das Menü ist so ein Beispiel - du darfst zwar das Menü als solches verwenden - aber du darfst kein Ding machen, das nichts anderes tut, als einfach ein Hülle um die RadControls zu legen, und damit die Funktionalität der Controls als "eigenes Ding" anbieten.
Es geht letztendlich darum, dass du die RadControls nicht "wie sie sind" vertreiben darfst.
Noch ein Beispiel - du machst ein "Blog Dingens" in dem RadMenu zur Navi verwendet wird - und die Navi ist auch noch anpassbar.
Das ist OK - da die Navi nur Teil deiner Lösung ist.
Bietest du aber ein "Navi Addin" für irgendwas (Sharepoint, ASP.NET, DNN...) an, dann ist das nichts anderes als RadMenu mit Hülle - und das ist nicht erlaubt.
Beachte einfach folgende Richtlinie:
Könnte man dein Ding ersetzen, indem man statt dess dirket ein RadControl nimmt, dann ist es nicht erlaubt.
Und im Zweifelsfall (oft ist es wirklich klar) - einfach telerik kontrollieren und die Anwendung erklären.
ACHTUNG: bin auch nur Kunde - und das ist nicht mehr als meine Sicht der Dinge!!!
The last two sentences in english:
Guideline: If the thing that you build could be replaced by the direct use of a RadControl - it's not allowed.
In the matter of unclearness (sometimes things can be unclear) simply contact telerik, describe your use and ask them if it's legal.
ATTENTION: I'm nothing more than a customer and that's how I understand the agreement!
Regards
Manfred
in simple words this particular part of the agreement means that you have to build an own thing.
Or in other word - you are not allowed to distribute the software in a way where it adds only some "shell around" but keeps to be the same as it is in original.
In this sample:
YES - build your "blogging engine" which uses RadEditor
NO - build a menu (navigation) component which offers (almost) the same as RadMenu to the enduser.
For better understanding - the last part in german:
Du darfst nichts machen, was nur eine "Ableitung" der RadControls ist.
Das Menü ist so ein Beispiel - du darfst zwar das Menü als solches verwenden - aber du darfst kein Ding machen, das nichts anderes tut, als einfach ein Hülle um die RadControls zu legen, und damit die Funktionalität der Controls als "eigenes Ding" anbieten.
Es geht letztendlich darum, dass du die RadControls nicht "wie sie sind" vertreiben darfst.
Noch ein Beispiel - du machst ein "Blog Dingens" in dem RadMenu zur Navi verwendet wird - und die Navi ist auch noch anpassbar.
Das ist OK - da die Navi nur Teil deiner Lösung ist.
Bietest du aber ein "Navi Addin" für irgendwas (Sharepoint, ASP.NET, DNN...) an, dann ist das nichts anderes als RadMenu mit Hülle - und das ist nicht erlaubt.
Beachte einfach folgende Richtlinie:
Könnte man dein Ding ersetzen, indem man statt dess dirket ein RadControl nimmt, dann ist es nicht erlaubt.
Und im Zweifelsfall (oft ist es wirklich klar) - einfach telerik kontrollieren und die Anwendung erklären.
ACHTUNG: bin auch nur Kunde - und das ist nicht mehr als meine Sicht der Dinge!!!
The last two sentences in english:
Guideline: If the thing that you build could be replaced by the direct use of a RadControl - it's not allowed.
In the matter of unclearness (sometimes things can be unclear) simply contact telerik, describe your use and ask them if it's legal.
ATTENTION: I'm nothing more than a customer and that's how I understand the agreement!
Regards
Manfred
0
Hello Pascal,
Thank you for your inquiry.
The paragraph you have quoted refers to redistribution rights, that is when you would like to develop a commercial solution in which Telerik's software is integrated, and sell this same solution to your customers. Please note that the quoted clause ( "The SOFTWARE may not be distributed as part of products that have the same or substantially the same primary functionality as the SOFTWARE. ") does not prevent you from building SharePoint WebParts with Telerik's controls but only from redistributing these WebParts on their own.
It is okay to build and include SharePoint WebParts in an application you are developing for a client of yours - the only requirement is that the primary functionality of the application differs from the primary functionality of the Telerik's controls you have integrated.
We will be glad to consider your exact scenario and advise further on the matter. Hence, please describe in detail the product you would like to distribute – what is the intended functionality, are you going to ship the source code, are your customers end-users or developers?
I hope the provided information was helpful and we'll be looking forward to assisting you further.
Best wishes,
Lidiya
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thank you for your inquiry.
The paragraph you have quoted refers to redistribution rights, that is when you would like to develop a commercial solution in which Telerik's software is integrated, and sell this same solution to your customers. Please note that the quoted clause ( "The SOFTWARE may not be distributed as part of products that have the same or substantially the same primary functionality as the SOFTWARE. ") does not prevent you from building SharePoint WebParts with Telerik's controls but only from redistributing these WebParts on their own.
It is okay to build and include SharePoint WebParts in an application you are developing for a client of yours - the only requirement is that the primary functionality of the application differs from the primary functionality of the Telerik's controls you have integrated.
We will be glad to consider your exact scenario and advise further on the matter. Hence, please describe in detail the product you would like to distribute – what is the intended functionality, are you going to ship the source code, are your customers end-users or developers?
I hope the provided information was helpful and we'll be looking forward to assisting you further.
Best wishes,
Lidiya
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Pascal
Top achievements
Rank 1
Rank 1
answered on 29 Apr 2009, 09:39 AM
Hello Lidiya,
thank you for your Reply.
I can provide some scenarios:
1. Sharepoint uses Fields inherited from the SPField Class to display controls on NewForm.aspxm EditForm.aspx etc. These Fields are somewhat basic, let's say we want to create a custom field for this forms which is extended with Telerik Controls (Autocomplete, RadComboBox...).
2. Search Webparts for Sharepoint where the original textbox is replaced with a Telerik RadTextBox to provide more functionality like formatted input strings.
3. Use the RadGrid to replace the ListView from Sharepoint to support other Browsers than IE.
Basically, these solutions will be provided as Sharepoint Solutions to our Customers.
best regards
Pascal
thank you for your Reply.
I can provide some scenarios:
1. Sharepoint uses Fields inherited from the SPField Class to display controls on NewForm.aspxm EditForm.aspx etc. These Fields are somewhat basic, let's say we want to create a custom field for this forms which is extended with Telerik Controls (Autocomplete, RadComboBox...).
2. Search Webparts for Sharepoint where the original textbox is replaced with a Telerik RadTextBox to provide more functionality like formatted input strings.
3. Use the RadGrid to replace the ListView from Sharepoint to support other Browsers than IE.
Basically, these solutions will be provided as Sharepoint Solutions to our Customers.
best regards
Pascal
0
Hello Pascal,
Thank you for your follow-up.
The first and the third scenarios offer the same primary functionality as the integrated Telerik's controls and would therefore not qualify for redistribution.
As to the second one, if you meant to enhance a List Search WebPart, then this would match the Filtering functionality offered by our ComboBox control for ASP.NET, and would not qualify for redistribution. Please review this demo: http://demos.telerik.com/aspnet-ajax/combobox/examples/functionality/filteringcombo/defaultcs.aspx.
However, If you meant to enhance the out of the box Search WebPart, then in this case it is okay to replace the original textbox with Telerik's RadTextBox and redistribute the WebPart, as the new part will be offering additional functionality, adding on top of the primary functionality of RadTextBox.
Please be advised that you can still implement all 3 scenarios and use them in applications you are developing for clients of yours, but redistribution rights are given to WebParts which primary functionality significantly differes from the primary fnctionality of the Telerik controls that are included.
Let me know if I can assist you further.
Best wishes,
Lidiya
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thank you for your follow-up.
The first and the third scenarios offer the same primary functionality as the integrated Telerik's controls and would therefore not qualify for redistribution.
As to the second one, if you meant to enhance a List Search WebPart, then this would match the Filtering functionality offered by our ComboBox control for ASP.NET, and would not qualify for redistribution. Please review this demo: http://demos.telerik.com/aspnet-ajax/combobox/examples/functionality/filteringcombo/defaultcs.aspx.
However, If you meant to enhance the out of the box Search WebPart, then in this case it is okay to replace the original textbox with Telerik's RadTextBox and redistribute the WebPart, as the new part will be offering additional functionality, adding on top of the primary functionality of RadTextBox.
Please be advised that you can still implement all 3 scenarios and use them in applications you are developing for clients of yours, but redistribution rights are given to WebParts which primary functionality significantly differes from the primary fnctionality of the Telerik controls that are included.
Let me know if I can assist you further.
Best wishes,
Lidiya
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.