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...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?
Previous
 
Next
New Post
3/26/2010 2:42 PM
 
Greg, I happen to agree with your suggested solution. A few people asked me on twitter to share more details on how I viewed recent events. I'm also prepared to offer some suggestions that I'm going to share very shortly.

Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
3/26/2010 3:28 PM
 
Chris Hammond wrote:
Lars Tungen wrote:
 
There is no wiki. Important information is scattered around on various external sites that appears and disappears as time goes by. Even critical information like safe upgrade instructions and upgrade paths is located on external unofficial sites. 
 

It's coming, that's the best I can offer right now, but a public Wiki for all things DotNetNuke is in the works

 

Lars Tungen wrote:

Dead or slow moving teams. Many core modules have very few releases each year (if any). Not because they are perfect, but because their teams are not functioning. And it's very difficult to find information about how to join a team and submit patches. May be they don't want any help.

 

That too is something that Scott Willhite is focusing on, trying to revive those slow moving teams, overhauling the release process for modules, and speeding up things to make teams more proactive and faster to develop and release.

 

Lars Tungen wrote:

No decent repository for user contributed extensions. "The forge" is a joke and an insult. Nough said. 

 

I'm sorry, but that isn't "nough said". Feel free to step up and provide some suggested enhancements to the Forge. Just saying "it sucks" doesn't do anyone any good except to bitch and moan.

 

I know the wiki is in the works. In fact, Shaun Walker was getting serious about the wiki 3 years ago. It's good to know that you are still working on it. I thought you had stopped :-)

Jokes aside, it's clear for me that the core teams are not getting anything done because they don't have the time or interest to get anything done. But, I am surprised that there is absolutely no effort being done to get people to contribute. In fact, this project looks pretty closed from the outside.

The forge is useless. I am surprised you can't see it. Instead of telling you what it needs, I am going to tell you what it has:

  • You can filter by 4 categories: Most downloaded, Most popular, Most recent and core modules.
  • Each project has a title and a short description
  • When you click on something you are redirected to codeplex
  • You can search it.
     

It sucks. Period. 

 
New Post
3/26/2010 4:13 PM
 
Lars Tungen wrote:

The forge is useless. I am surprised you can't see it. Instead of telling you what it needs, I am going to tell you what it has:

  • You can filter by 4 categories: Most downloaded, Most popular, Most recent and core modules.
  • Each project has a title and a short description
  • When you click on something you are redirected to codeplex
  • You can search it.
     

It sucks. Period. 

 

I actually don't disagree with you on your comments about the Forge. I was simply hoping you could provide some features you would like to see added so that it can be improved. I'm more than willing to try to help get those features and others to improve the Forge to the proper people so that enhancements can be made.

Right now there are some very cool things coming with other aspects of the community functionality here on DotNetNuke.com, mainly features within the User Group functionality. I don't see why features can be added to the Forge as well now that resources are getting up to speed and people are able to dedicate more time to these type of things.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/26/2010 5:02 PM
 

 Chris --

Would you mind putting our 'vocal minority' minds to rest and advise those of us who use the Community edition if we should continue to work with the OpenDNN module, since it seems it is still available temporarily on Snow; or should we prepare ourselves for the future by investing our experience using other document management systems since it *seems* it won't be available as per the announcement.

Could you help us out with that?

We know you guys have to do what you have to do, but can you help us out by giving us a clear, definite signal on exactly what you plan to do? We may not be shareholders in your venture, but you can't disagree we are stakeholders. Just looking for a little consistency in DNN Corp's message.

Thanks

 
New Post
3/26/2010 5:38 PM
 

 I understand the difficulty you've put yourself in with respect to answering the above question.

If you answer "DNN will be bundling the OpenDNN product in the Community version" then you've effectively put Document Exchange out of business and maybe others who don't want to suffer the same fate.

If you answer "DNN will be selling the OpenDNN product on Snow (but everyone knows will be tightly integrated into the framework since it is a standard component of the PE edition) " that still effectively (imho) puts the screws to Document Exchange and discourages others as well.

If you answer "DNN will take the product off the market and it will not be available in anything but PE" (which you've done via bulletin) then the whole of the Community will feel screwed (which we do).

As an earlier poster has rightly pointed out, you have a bad PR problem. My reading of Geoffrey Moore on this is that you would rather take the Community into the Tornado with you, so that you can be more assured of making it. It's too early to jettison us.

You must have calculated in your make or buy decision that someone would have to get cut off at the knees.

Who is it going to be?

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?


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