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...Is DNN really open source, or should it be called controlled source?Is DNN really open source, or should it be called controlled source?
Previous
 
Next
New Post
4/22/2007 12:14 PM
 

 

I'd like to make a proposal. 

When the source for this open source project is finally released, wouldn't it be nice if the community had access to all the latest source? 
It's bad enough that we have to wait on official releases to even see the latest source. So when we get the latest release and it has bugs, how can we fix them if all we have is binaries for referenced projects?

The WebControls project for the last two releases has not been updated, but the core project references newer builds on each one (good job getting a release build in the last release).

The FCK Editor provider has had several changes, but the latest project source is dated 11/27/2006.

My proposal is this:

Please make the build process include the building of all referenced source in the project that has been changed.  
Include all of the latest source in the source package of the core release.

If that is too hard to manage then please provide read access to all of the source at any time like most other open source projects.

Then again, maybe I am missing the boat.  Have all the developers that actually compile the source from this project gone away?


DotNetNuke Modules from Snapsis.com
 
New Post
4/22/2007 3:04 PM
 

We'll look into where the source code is for these projects.  The source code should have been released when DNN was released, since those projects are defacto "approved" for release once they are bundled with the core.  Although I don't understand why this has to be made into a major issue as indicated by the subject line.  If there is a problem, then you certainly know who to discuss it with to get it resolved without resorting to inflamatory postings.


Joe Brinkman
DNN Corp.
 
New Post
4/22/2007 3:43 PM
 

Thanks for looking into it Joe.

As for the subject line.  I have a question and I thought that subject line may get the attention of the people who might also have an opinion on the subject so we could chat about it.

I am really interested in knowing how many developers actually compile the source and work with it as compared to the number of people that just use DotNetNuke by installing it (or letting their host install it) and waiting for the next release.

If you find it inflammatory, then I apologize.


DotNetNuke Modules from Snapsis.com
 
New Post
4/22/2007 4:33 PM
 

John Mitchell wrote

I am really interested in knowing how many developers actually compile the source and work with it as compared to the number of people that just use DotNetNuke by installing it (or letting their host install it) and waiting for the next release.

It's probably a large number of people but an increasingly smaller percentage. You know I'm constantly recommending that people stay away from the source because you don't need it for module development.

I also think we have a growing number of people who do not have a copy of Visual Studio and are only using Visual Web Developer Express which as you of course know can't be used to compile the source.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
4/22/2007 5:07 PM
 

John,

  I have raised the issue internally and we will push to get it fixed.  One thing to keep in mind is that we do try to allow projects to be somewhat autonomous, even if it may not always seem that way, so I can't really demand Jon or Mauricio post the latest versions but I am sure that this is just an oversight and will be quickly remedied.


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Is DNN really open source, or should it be called controlled source?Is DNN really open source, or should it be called controlled source?


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