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

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...DNN 5 Localization capabilities improved?DNN 5 Localization capabilities improved?
Previous
 
Next
New Post
8/11/2009 9:09 PM
 

cathal connolly wrote
 

when drawing up roadmap items we elicit feedback from many sources including gemini enhancements, community rquests and subject matter experts. For this item we reached out to experts such as Sebastian and Peter Donker who kindly provided lists of what they'd like to see (these lists themselves also contain aggregated information from other sources such as Erik).

Due to the fact, that my name has been mentioned, I have to defend myself:
I simply provided DotNetNuke Corp. some time ago with this document: http://dnn-europe.net/Portals/0/activeforums_Attach/DotNetNuke_Content_Localization4.doc, which has been created by myself only and is an update of a summary, I did in 2006.

I did not get any response and am not involved with subsequent activities in this area.

Thank you.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/11/2009 9:54 PM
 

 Cathal,

I think that the confusion is present and REAL because it is not always clear under which edition a new/updated functioality falls under. It is the lack of this transparency that leads to most often times wrong conclusions. In fact it is indeed possible and plausible where the DotNetNuke Corporation, after spending considerable time, resources and effort building a specific feature decides to make that feature a commercial one, where it was originally slated as part of the Open Source PE edition (as Jan pointed out, Shaun allegedly had announced it prior to the commercialization of DNN).

As a business person, I understand, and, of course, accept the reasoning behind the change of heart; I think the issue is one of open-ness and communication, and as mentioned above, transparency.

That being said, the process of fuguring it all out is a balancing act... I certainly do not wish to be in your shoes... keeping the Open Source community "pleased" at all times, while trying to make a living out of it all is certainly not an easy thing to figure out.

I presume that the sooner the folks in the community accept the fact that there is "board" that DotNetNuke Corporation answers too, the sooner they will understand the pressures, and reasoning behind such decisions. (Not saying this was already decided, because I simply do not know that, but this could apply to other similar instances).

Jan, Sebastian:

I am not defending or attacking anyone here, I am simply sharing my views, and they are what they are, MY OWN views.

Regards,

 


Maxiom TechnologyAntonio Chagoury | Microsoft MVP
Maxiom Technology
Professional .net & DotNetNuke Solutions
web: www.maxiomtech.com
blog: www.cto20.com
twitter: @antoniochagoury & @maxiomtech

 
New Post
8/12/2009 3:42 AM
 

Sebastian Leupold wrote
 

 cathal connolly wrote
 

 

when drawing up roadmap items we elicit feedback from many sources including gemini enhancements, community rquests and subject matter experts. For this item we reached out to experts such as Sebastian and Peter Donker who kindly provided lists of what they'd like to see (these lists themselves also contain aggregated information from other sources such as Erik).

 

Due to the fact, that my name has been mentioned, I have to defend myself:
I simply provided DotNetNuke Corp. some time ago with this document: http://dnn-europe.net/Portals/0/activeforums_Attach/DotNetNuke_Content_Localization4.doc, which has been created by myself only and is an update of a summary, I did in 2006.

I did not get any response and am not involved with subsequent activities in this area.

Thank you.

All,

I've chatted to Sebastian to see what offended him and he's stated that he thought my post was too ambiguous and suggested he was part of the team developing the localisation solution. I thought that my post made it clear that it was simply an information gathering exercise, and not that Sebastian was working on this area, but just in case anyone else thought this, I can confirm that he is not involved in designing or developing the localisation enhancements.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/12/2009 3:46 AM
 

Antonio Chagoury wrote
 

 Cathal,

I think that the confusion is present and REAL because it is not always clear under which edition a new/updated functioality falls under. It is the lack of this transparency that leads to most often times wrong conclusions. In fact it is indeed possible and plausible where the DotNetNuke Corporation, after spending considerable time, resources and effort building a specific feature decides to make that feature a commercial one, where it was originally slated as part of the Open Source PE edition (as Jan pointed out, Shaun allegedly had announced it prior to the commercialization of DNN).

Antonio,

I think what you're saying here is that you want a clear roadmap that states what features are being built for what version of DotNetNuke, and if any of them are PE specific, to remove any ambiguity. In this I completely agree with you and hope that the Corp post such a roadmap as soon as possible.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/12/2009 4:41 AM
 

One of the reasons it takes such a long time to implement  "content localizatition" is that everone that has ever had anything to say about it has a different idea on how it should be implemented. In the past the DNN localization team (especially in the persons of Vicenç and Sebastian) has done great work in identifying the areas that need to be looked at and in offering suggestions on how to support content localization in the core.

When members of DNN-Europe met in Switzerland last february, we had great discussions on how content localization should be implemented in the core. Mind you that in my view this was the first ever real and concrete discussion between community members that are already involved in ML DNN implementations everyday. Of course my memory does not go back as far as that of Jan Olsmar, so it could be that such discussions happened in the past as well.

Anyhow, as a result of the discussions we had in Switzerland, we were able to go to DNN Corp and offer them the views and insights that came from those discussions. This resulted in subsequent discussions with DNN Corp, and ultimately in a Corp decision to put content localization on the 5.2 roadmap. AFAIK the decision on the 5.2 roadmap was made after DNN 5.1.1. was released (as you all can remember there were some issues surrounding the release of dnn 5.1.0 ;) ).

Mind you: one of the sessions that Shaun will do at OpenForce Europe will be about content localization....

So.. where are we at now:

  • content localization is on the roadmap for dnn 5.2
  • Cathal has been assigned to work on this new feature

For the record: i agree with Antonio that there could be more clarity as to the roadmap of both CE and PE...

DISCLAIMER: all of the above are my own views!


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...DNN 5 Localization capabilities improved?DNN 5 Localization capabilities improved?


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