Legal-ese demystified

by Evan Hutnick | Comments 2

Hello Everyone!

I'd like to begin by introducing myself to the Telerik Blog scene. My name is Evan Hutnick and I work as a Developer Support Consultant in our US Sales office. I began here back in September of 2008 and have been on a fast-track to learning everything about Telerik.

But what does a Developer Support Consultant do, besides sound flashy? More or less, I'm one of the first lines of defense in the sales office for any sort of technical questions we receive. As a developer in my spare time, I've used Telerik controls (albeit only as a hobbyist before I started my career with Telerik) for quite a while and have a decent amount of technical knowledge of the products that we offer. Since I have the unique experience of working in sales and having technical knowledge, I often find the need to translate technical aspects of the products to terms and concepts that would be meaningful to non-technical people and vice versa. I also sometimes tackle that for licensing...

Now, as you all should already know, we have very user-friendly licensing policies.  Thinking back to Vassil's post (I'm continuing the demystifying, just on another topic), here's a two minute refresher of what we offer.  Our licensing is very liberal- we don't make you fight with license keys, authentication schemes, and we don't only give you a sample of our control suite as a trial- you get the full thing, just with a demo message that pops up every so many uses.  You only need to purchase licenses for those working with our UI controls, so forget any nonsense about build machines licenses.  Quite simply put, every developer who works with the controls needs a license, anyone not dealing with the UI doesn't.  Plus, if you're like me and spread your work out between your work pc, home pc, and laptop, one license covers all three as long as you're the only developer using them.  We make it easy so you can spend time developing instead of fighting with obscure licensing policies.

So what is this leading up to?  Stay tuned, tomorrow we dive into section 3-1 of our license agreement: Source Code.

About the author

Evan Hutnick

Evan Hutnick

works as a Developer Evangelist for Telerik specializing in Silverlight and WPF in addition to being a Microsoft MVP for Silverlight. After years as a development enthusiast in .Net technologies, he has been able to excel in XAML development helping to provide samples and expertise in these cutting edge technologies. You can find him on Twitter @EvanHutnick.

Posted in: community licensing

2 Comments

Frederic
Hi,
Just one thing.
What if we are selling an application that uses some of your components and that we would like to provide the source code of our application to our customers?
Obviously, they would need the Telerik's components used in the application (in binary form) for being able to compile the application.
How does licensing apply in this situation?
Thanks
Evan
Hello Frederic,

This type of situation is covered in the license agreement section 2-1: Redistribution rights.  This covers the basics of what you need to do in order to stay within the bounds of the license agreement with your product.  One key thing to keep in mind is that you can distribute our product in object code form (i.e., compiled) only, so you are not allowed to make any source from the Telerik controls available to your customers.  For information on how to do this, please send an email to support@Telerik.com or submit a support ticket requesting a copy of these instructions.

As for the copyright message (2-1.4), in web or desktop applications there is usually an "About us" section or documentation were this message can be included. For web sites, it is OK to have the message in the Terms of Use or Copyright sections, or even as a comment in the HTML code.

If you have any other questions definitely let us know!

Comments

  1.    
      
      
       
  2. (optional, emails won't be shown on public pages)
  3. (optional)
Read more articles by Evan Hutnick - or - read latest articles in Developer Tools