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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The Day of DreadThe Day of Dread
Previous
 
Next
New Post
2/19/2009 3:24 AM
 

Salama wrote

Jumping into the future and assuming our worst DNN fear gets real where the pro version gets updated and supported while the community one rusts. What if some volunteers decide to fork the community version and decide to update it on their own, is this "legal" and permitted? Assuming they use a different name.

You haven't read this thread have you ? :).



Alex Shirley


 
New Post
2/19/2009 9:44 AM
 

You know, watching this thread I can't help thinking that I didn't see any paranoia like this when Sun bought MySQL.  Maybe it's just different in the Microsoft/Windows world or maybe this really is an isolated issue.

Jeff

 
New Post
2/19/2009 11:47 AM
 

Tried to stay out of this thread, but did not see this piece mentioned exactly, so...

My only 'fear', and that's not really the correct word more like concern, is that there is a conspicuous absence of Core Team and Project Lead support over the last year or so.  A lot of issues are being handled by folks that always contribute meaningful response.  Of course, that's always been the case, but it does seem that CT members in particular being so focused on bringing out the new model do not have the time to offer their valuable time in support of the community with regards to answering the issues presented.  Lot's of reasons for that to be the case, and I fully understand it, having been on the CT for a brief period.

Whatever the case may be, the value of these community forums for me was being able to tap the knowledgebase of the 'creators' of the codebase, to get a bit closer to understanding it, so I could help myself, and in turn pay it back to the community.  What concerns me is that more and more due to the need to provide a sound financial base for operations, folks including DNN Corp., are going to provide less free support and rely more on the community to 'test','report', and offer 'fixes' to the codebase.  It's rather difficult to provide 'fixes' for issues in other than the existing published source.   The community as a whole does not have access to the 'real' agenda or roadmap despite having some limited knowledge of where DNN 'thinks' it's heading.  So, any fix or new approach really is blowing in the wind, and subject to having to be redone over, and over.  I guess, it's a reality of the software cycle, but that's what is complicated by the 'big brother' knows better attitude that is being projected more often than not. 

I applaud the sucess of DNN and offer what assistance I can freely to the community, but if DNN Corp, and the CT in general are not represented well in support of the community version of DNN, then more folks are going to join that legion of DNN community members who only offer subscription based help.  I do understand the business side that requires having to be accountable for the effort to provide services.

So my 'fear' is that support of the community version is dropping in place of paid help service providers.  The success of DNN was not only the codebase, but the 'free' exchange of support, ideas, and solutions from folks, which included CT members that were close to the bleeding edge of developing the DNN codebase. Though the forums are the only way to exchange knowledge, it is clearly not the best way to offer knowledge.  The simple evidence of that fact is the number of question that repeated about the same topic.  Search mechanisms are insufficient, but more to the point the forums really are not a good vehicle for providing a true knowledgebase.  So, in the end all have a part to play for DNN to be successful.  Here's hoping that support moves forward as well as the codebase.

 
New Post
2/19/2009 1:09 PM
 

Phil,

I did not reduce my contributions to these forums nor do I plan to do son in the future - though there are days or weeks, when I am less responsive due to other business. Same for most of the other CT members, as far as I can observe. Besides the Corp employees, the CT members have not been involved with DNN PE in the past or present AFAIK. Of course, there are a number of CT members, offering DNN services to their customers and some have to answer questions about DNN PE as well, but I don't expect the community support being reduced significantly - in contrary, with additional resources in the corp and new CT members, our effectiveness shall grow for the benefit of community and commercial users.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/19/2009 1:55 PM
 

Sebastian,

I appreciate all of your efforts, and did not mean to suggest that CT members would not contribute, it's just that there seems to be less CT responses than in the past.  What has always been the case is that there are CT members more actively engaged in the forums than others, which is a very small percentage of the overall group.  Even the blogs reflect this lack of participation by many who supposedly have blogs from the CT.  I remember that many times only a handfull of folks participated in the Core group discussions/chats.  Many more choose to quietly contribute to the core codebase, or projects without interacting in the forums, and that's a choice folks make for various reasons.  I dropped out of the CT due to the level of workload I was doing in my 'day job', and because the 'fun' or enjoyment I was getting from working on DNN was being overshadowed by my inablility to focus on it.  For me, if I could not provide time and effort to answer to the community, I just didn't think I was worthy to be a CT member.  Of course, many probably thought - what the heck is he doing on the CT anyway.  In any event, I met and still cherish the links I made with the folks during that time. 

I don't mean that folks are not doing work, it's just that a lot of folks would really like to hear updates from CT and Project leads more often than is represented.  If it wasn't for the participation of folks with your knowledge and experience the Forums would fall in relevancy.  Bottom line is I have that is my chief concern, but not to the point of losing interest or desire to help.  The addition of a Profession Edition does not bother me, any more than using the freebie tools from Microsoft rather than pay for their professional editions.  I just want to be assured that the support of the community version continues to be a focus and provides help for those unable to bear the cost of support.  

 Personally, I'd give you the DNN Support Award for all of your efforts, and meaningful contributions, and would like to see more folks follow your example.  So, thanks, and keep it up, I appreciate it.  

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The Day of DreadThe Day of Dread


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