Hi

I've decided to build a DNN Blog module since I find the standard blog module a bit inflexible especially for multiple users etc.
However even though we could build one from scratch there are lot of basic functions that same just fine.

So my question is: is it kosher to use parts of the source code for the DNN Blog module and then go ahead and sell that as a new module?

I've seen on SnowCovered.com that many of the modules on there use the fckHTML editor for example. So where is the red line on this sort of thing when it's open source?

Thanks for the link, well I really just wanted to keep the core structure and then edit and build on top a whole other set of features.

I'm not legal expert by a long shot but if I'm reading this correctly:


"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."


Doesn't that mean that in theory you could even take the orginal DNN Blog module as it is and resell it if you wished providing the one condition stated which is that the copyright notice must be included?

Not that I intend to do that but it's interesting to know what the limitations are, seems like there aren't any to me... :)
 

Yes, you can - but it is a matter of fairness to the developers not to do it. Besides, make sure you keep in line with trademark conditions for the DotNetNuke name, which are more strict.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN