I would like to see deep integration of FlexWiki and DotNetNuke?

It would bring the free workflow of a Wiki, the time-based Blog, the templates of Bliki into the best .NET portal system on the web today.

The ideal FlexWiki integration would mean that the DNN pages would be created by WikiWords, editing could be done in FreeTextBox or another WYSIWIG editor, with FlexWiki(Bliki) buttons, and also use something like XML Forms, a la XMod. It would of course have the Blog Feature. The WikiPedia wiki system has many of these features.

In my view this would follow the progress of such Bliki's as http://www.xwiki.com , as they integrate with Java portal servers.

Would this be called a DNNFlexBlikiModule ?

NicholasRoberts

How much work is there in upgrading the old version vs how much would there be in modding flexwiki?
I'm keen to get a FlexWiki DNN project up, because I think there's a real advantage in harnessing the current maturity of FW.
Is this here project committed to upgrading the old DNN wiki, or is it up for debate?
Is it worth having both projects?
Am I asking too many questions?

It is more than just deciding to use one set of code or another as a base.  For every DotNetNuke sub-project the IP holder had to agree to a joint copyright so that the sub-project could be distributed under DNNs BSD license.  So there is more involved in using FlexWiki than just a simple yes/no decision by the dev team.  In the case of the existing DNN Wiki module, we already have that agreement from the original author Jonathan H. (name abreviated to save me the embarassment of badly mangling the spelling ).

One thing that we need to be extremely careful of on any DotNetNuke code is that we don't inadvertently use someone else's IP without express written permission.  We don't want to become the next SCO/LINUX legal battle.

---

Joe Brinkman
DNN Corp.