Just for the record, here is what the licensing info currently states:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
__________
My understanding of the license, and of changes to the license if they should occur, is that: if DNN Corp starts to charge for the updates, the community will definitely suffer and DNN may become a slowly dying platform. However, if there are enough community members who want to contribute to an open-source project, we could simply take all of the source code released under the BSD license and start a "fork" in the road with a new open-source project.
After all, I believe I read somewhere that DNN was started based off of a "community site" template made by microsoft to demonstrate ASP.NET capabilities.
Still, if it changed, I think my future sites would be made in something open source that uses linux servers... like Drupal. While drupal scared me off because it was less intuitive to use, I recently started playing around with it more and find it's not that difficult and VERY extensible.