Legal-ese demystified

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.