To make use of Telerik you need extensions that take advantage of it. For example, there needs to be a Telerik menu skin object or provider (ie. Extensions) as well as a skin that references the skin object or provider. Currently, the Professional version of DNN ships with a HTMLProvider that uses the Telerik editor but the Community edition doesn't have one (yet). Since this just happened in November, it will take time for the core to write wrappers for people, such as yourself, to really see the benefit of the Telerik integration (in all editions, including Community) but we are working on it. 

Judy,

The Telerik component was available in community edition the same time it was available in Professional. However, developers have to take advantage of this using their own Telerik license (which comes w/ DNN Pro or can be purchased separately) or wait for a core wrapper to be written for each control. This means that pro and community both had this option available at the same time, with the 5.2.0 release, and will continue to do so for as long as the partnership exists (I have no details on this but I see it existing for a long time). 

Now, to get to details about the provider example you are referencing. The reason Pro was able to launch with this is Telerik licensing reasons, it is a product that is distributed by DNN Corp, that doesn't require a core wrapper to be written first (developers can ONLY use telerik if they have a license, or a core wrapper is written). This does make sense, from a licensing perspective, but I will spare you from further details. I currently do not know what the time frame is for any of the wrappers to be written therefore I have no idea when this will happen. 

One thing that I do know is we will be seeing a couple things from the skinning contest that utilize Telerik and after the contest completes these will be available for download.