Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreMy experience getting Store into productionMy experience getting Store into production
Previous
 
Next
New Post
9/11/2006 3:51 PM
 

Hi jthake,

I think your blog is a pretty reasonable commentary on the current open-source "state-of-affairs."  I can read between the lines too, and the difficulty as you point out, is not painting everyone with the same brush.  Some people really do contribute unselfishly, others find a happy medium between commercial interests and community sharing, while others only look to make a buck...

In some cases, it would be difficult to see where the gray areas are; but one would hope that if it was REALLY apparent, the core team would interject.  I don't think pointing out offenders should be done publically, because you just never know what is going on in the background - appearances can be misleading.  Point it out to a care member - they want to make sure the community "eco-system" stays healthy, and this kind of thing can form a very real cancer...

Cheers!

 


Rob Poretti - Poretti Productions
 
New Post
9/11/2006 4:50 PM
 
I guess I should try to defend myself here after incurring the wrath of the open source advocates!!!

I first started using store about 6 months ago, frustrated by the bugs, my project was delayed again and again with no sign of a new release of Store.  Then 1.00.01 came out (still beta), and some bugs were fixed but not enough to make the module usable.

I was faced with either dropping DNN in favour of OsCommerce or zencart or enhancing store on my own.

With indsight, I should have abandoned DotNetNuke completely, but I didn't, so I started fixing store and upgrading it.

I spent at least a month's worth of man-days (in my spare time - this isn't what I do for a living!) putting the upgrade together, and while I agree that's is a little profiteering, the selling of my work gives developers (and business users) who are now in the position I was six months ago an option - they can buy my code, then replace it with Store when it becomes usuable in the next release.

You may or may not agree with my methods, but six months ago I would gladly have paid for this code.  I could even argue that the availability of my code helps DNN by keeping more developers faithful to the platform, and not abandoning it as I nearly did because it's ecommerce support is currently (and sadly) unusable.

For the future, I've splintered my own development, and don't really expect my own sites to ever upgrade to the next release of Store.  I have plans to upgrade and further enhance my module, tailoring the enchancements and release cycles to my own needs.  When this happens, my module will become unrecognisable from the Store beta to which it's roots belong.

All I'm doing is extending a framework, in exactly the same way as we all extend the .Net Framework in all the .Net Development we do.

I'd also like to point out that now that my workload has decreased, I am posting on these forums helping other developers to solve their problems with store.  Not once have I mentioned the fact that my module is for sale or tried to sell it to the users on these forums (in fact only the previous two posts have drawn attention to that fact!), and I've never suggested that anyone buy my code over using Store.
 
New Post
9/11/2006 7:29 PM
 

Hi All,

As a member of the Core Team, a Moderator, and as the Store Lead I think this thread has run its course and should end, we need positive posts, not negative. 

Here is my feeling on all that has been posted so far.  First, I will address the use of the store code to make money and then I will address how to become a member of the store team.  Both of these are hot topics in this thread.


Athompson

We have all been roasted in the forums (I get roasted at least once a month) so please don’t take it too personally.  This is part of the fun of being part of an open community.

I personally would have loved to see you jump in and help the store team; however, I am not upset or offended.  One of the great parts of being Truly Open Source is the ability to take some work, re-brand it, maybe make some changes (though you don’t have to), and then resell it to anyone that will buy it.  The whole point of the eCommerce module is to make money, you are making it in the code instead of a product, cool!  The fact that you did enhancements makes it even better. However, what I would ask is that you totally re-brand it so people are not confused and that Core DNN upgrades run without trashing someone’s store.  When I say re-brand, I am taking new name, namespace, class, db tables, db procs, etc so that in no way the two stores will conflict.  The other thing is that you should leave the DNN Copyright in the source code that you have used and give credit in the documentation.  Other than that, I say have at it. 

One of the most discouraging things I see in Open Source today is the combination of the phrase Open Source with a restrictive license such as a GNU.  Once you add a restriction it is no longer Open Source.  Open Source means no restrictions...  If you want to help the team, please feel free, if you want to sell it, do it, but do it responsibly by observing my requests above.

Vitkoz

Much like the DNN Core Team, people who are very active, report, repair, help others, and post their workarounds/fixes/enhancement ideas are the people that are invited to be part of the team.  Just saying I will help is not enough, we need to see you in action.  There is more overhead than you realize to become a team member and we only want to do the work if you are going to contribute.  The only way to know you will contribute is to see you doing so.  If you want to assist, you don’t need a title, just start posting and we will go from there.  Djbaldwin is a great example of this.  He was actively posting, positive, offered help, posted ideas, posted code, etc.  He was a very logical choice for a team member and has been a GREAT addition.

I hope this clarifies things and brings this post to an end.


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
9/11/2006 9:47 PM
 
I wasn't trying to roast anyone. It's fair enough that people go off and write new code enhancements etc. if stuff is that buggy and they need it ASAP.

How do we get the source code for the dlls?

Obviously I can get the source code behinds for the controls etc. and sql scripts...but what about for the class libraries? I'd like to help debug this error I'm getting with the ShippingTax stuff, but need to trail through the class libraries to see exactly what is going on.

Thanks again,
Jeremy
 
New Post
9/12/2006 6:24 PM
 
Makes perfect sense.

Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreMy experience getting Store into productionMy experience getting Store into production


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out