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...SiteMap.aspx errant link to dotnetnuke.comSiteMap.aspx errant link to dotnetnuke.com
Previous
 
Next
New Post
6/8/2007 2:33 PM
 

John Mitchell wrote

I have noticed that there seems to be more and more places in the code where we are linking back to dotnetnuke.com assets and/or places where we might be violating policies.

For example:
      1.)   In SiteMap.ascx.vb there was code added to make the DotNetNuke.com website show in the list of links.
      2.)   The new search features for searching the web includes an embedded Google AdSense ID that belongs to DotNetNuke Corporation.
      3.)   The new DotNetNuke Powered! program is being promoted as a way to build reciprocal recognition, but it is designed in a way that does not reciprocate fairly.

Is there any official policy on how DotNetNuke approaches advertising, so as not to make the application into an AdWare vehicle?

Would any core team member like to talk a little bit about why this was done and what direction you see going forward?

 

This should probably be a seperate thread for wider discussion but .....

My thoughts:

1)

In my own mind, had it not caused a google validation error, it would be fine as this is controlled by the user.  It's just part of the Show Copyright setting.  It's nothing sneaky and I can understand the promotion aspect for a project like this.  How many sites of any commericial value have the DNN copyright notice on anyway.  Lets be realistic.  If you are going to link to DotNetNuke on every page anyway, why do you care about one link in your sitemap.

2)

I haven't studied this fully yet, but I understand and can agree with your concern.  If there was an interface to enter your own AdSense ID in say the the Search Admin screen but it defaulted to the DotNetNuke one if it was blank then I would be OK with that assuming this does not violate any Google terms of service as someone tried to allude to.

3)

Could you elaborate more on what you would like the Powered! program to do to better reciprocate?  I just would like to understand your position.  I think I understand the Team's position.


Jeremy White
DNN Core Team Alumni
 
New Post
6/8/2007 2:38 PM
 

Mitchel,

These issues are beyond "submitting a ticket".  It is a fundamental difference in the policy we use when making changes of this nature.

The issue about the Powered! program is supposed to be addressed, but I have received word that Shaun actually told the project leads that it was developed that way "by design". 

I do appreciate your enthusiasm though.  The project is lucky to continue to attract people like you.

Thanks for your input.


DotNetNuke Modules from Snapsis.com
 
New Post
6/8/2007 2:43 PM
 

John Mitchell wrote

My original post in this thread was just an off-hand comment due to my frustration in not getting any constructive dialog with the people making these decisions.

Constructive dialog requires actual "dialog".  My only reason for posting a response of any kind here is that this directly maligns my personal character as an individual (apart from DotNetNuke).

Recently I made an attempt to simply greet you in person... to respectfully shake your hand and say hello in the presence of shared friends.  Your response was "I don't think so" and an admonition that it would be wise for me to leave.  This has been lied about publicly and I have said nothing, done nothing, worked very hard to respond civilly despite continued character assaults on personal blogs and even on this site.  So much for dialog.  So much for truth.  So much for constructive intent.

I understand that you are personally upset and frustrated.  But these very actions provide the explanation as to why you were retired from the team.  Working with you on any basis other than your own personal terms was entirely life-draining.  Interestingly, the productivity and output of the team has gone up dramatically since your departure.  This says nothing about you personally, it never has... you are a very smart, very helpful and very talented person.  But you are not easy to work with (in a team environment) and not very gracious about it.  That shows in the teams output.

Continue to hate and despise Scott Willhite (and others) if you must.  We can live with that.  But please don't cloak that anger & frustration in some high ideal.  The entire team and the community suffers for it.

We have and will always continue to embrace the abundance mentality.... which says there is ample opportunity for everyone to be successful... and that we build each others success when we contribute.  As I have stated publicly on many occasions, and even privately in communication which you have posted publicly, I wish you great success.  I just wish you could believe that it does not have to come at the expense of others.

Despite what I believe you may think.  I (indeed we all) wish you well.

Kind Regards,
Scott Willhite


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
6/8/2007 2:50 PM
 

Jeremy,

My concerns with the Powered! program were outlined in this thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/threadid/119363/scope/posts/Default.aspx

Here they are:

There are a couple small problems with it doing what is promised though. 

The links to the pages are postback's so a search engine is not going to spider them.
Please make the paging control use a simple GET anchor, otherwise only the 15 sites on the first page will recieve any benefit, yet DNN will still recieve the benefit from all sites submitted.

Also, In order to make it a proper link exchange so all can benefit, the link back should go to the Powered! Page on DotNetNuke.
Otherwise DotNetNuke recieves much more boost from the back link than any of the other sites do.  
There is currently no Google PR on the Powered! page to even pass on to the sites in the program.


DotNetNuke Modules from Snapsis.com
 
New Post
6/8/2007 2:58 PM
 

Scott,

You make some assumptions that are not true, but I thought we were past making this dicussion about me.  I could say a lot on the accusations you make, but I don't think this is the time or the place.  Then again, maybe I should just address one thing to keep the dialogue going.  If you take a look back at that publicly posted communication that you are referring to, you will see that it has the name of the person that sent it removed.  I did that out of respect to the fact that the person sending it was acting on behalf of the company they worked for.  I do not wish to attack your personal character and I am sorry if you feel that way.  I think you are a good a decent person.

 


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...SiteMap.aspx errant link to dotnetnuke.comSiteMap.aspx errant link to dotnetnuke.com


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