Nina.. 

My response did answer the specific question "While the BSD license allows for redistribution, we ask that users instead download the package from DotNetNuke.com."  The license does allow for redistribution, however we have asked individuals not to do so for the reasons outlined here and as re-iterated in numerous forum posts over the past 5 years.  If you could see past your personal animosity towards me for a second, you would see that this is not a question where a simple yes/no response suffices.

As for the Hosters and control panel vendors;  we have separate agreements with them that were covered under our agreement as part of the Microsoft Shared Hosting program which has been in place for almost 3 years now.  We actively encourage Hosters and control panel vendors to move the latest versions of the platform.

We are not blind to the realities of the consulting and hosting markets.  I fully expect that a consultant may customize the installation package that they use for their clients, just as I expect Hosters will customize the installation package they use for their clients.  However, in both of those cases, the consultant/hoster is performing the installation and is aware of any differences between the official DotNetNuke package and the package that was actually installed.  Also, because of the business relationship, the customer anticipates that some level of support will be provided by the consultant/hoster.  This same relationship does not exist where a community member provides a re-packaged distribution for download by the general community.  Finally, hosters and control panel vendors have specifically worked with us to get installation features implemented to simplify the provisioning process.  To the best of my knowledge, hosters and control panel vendors are not doing anything outside of what was specifically developed to address their installation needs.

You indicate in your response that you don't see a problem with Ismet redistributing the package, however, this would not stop with Ismet.  Every locale would be justified in creating their own little fork and every person with a small bug-fix would also want to do the same.  Could I redistribute DNN if I am just changing the installation template?  That doesn't really change functionality.  What about a custom siteurls.config or a custom dotnetnuke.config?  And if I can make those minor mods, how about a simple change to default.aspx to change the default charset for the page?  Well, there is also this one little bug I wanted to fix as well... it is just a single line of code and doesn't even require a re-compile.  Soon we would have thousands of packages bearing the DotNetNuke name, but which in fact are different from the official download.  This is a bad precedent that only creates confusion for customers and is something we will actively discourage in all of its forms. 

I do appreciate Ismet's offer to help and have provided a way he can help that allows him to aid the Turkish community, while still honoring the DotNetNuke trademark and that also doesn't cause confusion within the community.