DNN Store and Open Source Community
September 10, 2006
I've done a DotNetNuke 4.0.2 install for a friend a while ago for his
http://www.jiggyjigs.com/ site.
He uses the
DNN Store project module which has quite a few
bugs in it. He's having trouble upgrading from v1 to v2 and I've noticed in the
forums that a guy has taken the code and is
selling it for
£50 with a few add-ons for multiple shipping costs, tax etc..
The issue is that if DNN store upgrades to a new version, it is my understanding on reading that the purchased modifications may not work. I can understand why he is trying to make money out of it, but for the good of the community it will cause all sorts of bother unless he keeps it inline.
It seems like he's been a very frustrated user and has sweated blood and tears to get it working, but he is not part of the Project team and looking at the posts made has not provided much code feedback in. I don't believe this is his fault as he just needed it working and sounded like he was very committed with DNN and the Store with the project he was on.
The real questions is, is this really how the Open Source .Net Community should be going?
Should the DNN Store Project team purchase the source code he has for sale and then put this back into the central source with all these fixes complete?
How can DNN encourage people to contribute rather than go it alone?
What factors made this guy go alone and what may have made him help the team instead?
For this community to work I think they need to work on this. After all, the bigger the contributions the bigger the product will become.





Comments
blog comments powered by