Article: VaultWiki 2.0.4

[pegasus]

You can view the page at http://www.vaultwiki.org/content.php?r=6-VaultWiki-204

[Kaelon]

Thanks for releasing this update (and especially the demo). I have a few pre-sales questions that I am hoping you can answer:

1. Are NameSpaces mandatory? I like using NuWiki's separate forums for my "namespace needs", but being able to link various articles among my different Wiki Forums using just the article name. If I want a NameSpace sort of place, I'll use a Wiki Island.

2. What sort of import functionality do you have for NuWiki? How long will it take on a forum with 1.3 million posts (around 1,000 of those being Wiki posts)?

3. Can you offer a direct, head-to-head comparison of NuWiki and VaultWiki?

4. What sort of copyright and intellectual property implications does VaultWiki have, with regardst o NuWiki (which is copyrighted code belonging to NuHit LLC)? Is VaultWiki original code, or did it borrow/use code from NuWiki? If the latter, does it have written permission from the author to develop this Wiki? My concerns are largely proprietary -- if I were to deploy VaultWiki on a large commercial website, I'd want assurances that we would not face legal challenges from NuWiki as the valid copyright holder of NuWiki related softwrae that might be used improperly.

Thank you!

[pegasus]

1: Namespaces are mandatory. In terms of infrastructure, this allows for a number of things that were not possible in NuWiki. I won't get into this here. If you don't create too many namespaces, it should be easy to tell where articles are, and it's never really necessary to include anything but the article title when using the appropriate link BB-Code.

2: For importing NuWiki, we have an Import script via the AdminCP. This has not been used extensively, so it would be hard to say how it would react to your database. When in doubt, create a backup. The Importer currently requires MySQL 5. If you cannot meet this requirement, then we would happily rewrite it sooner rather than later.

3: There is a comparison of NuWiki and VaultWiki on VaultWiki's product page, here: VaultWiki.

4: VaultWiki is entirely original code. Aside from code, having anything to do with NuWiki, the only things are the importer, forum headers, and books. But again all of these use original code.

As an aside, if legal action from NuWiki were to happen to any of their prior customers (who may or may not be customers of mine) for whatever reason, I would say that a counter-suit (which could be class-action, I suppose) with respect to their violation of the terms of the contract (i.e. the support), would force them to drop any charges.

[Kaelon]

Thanks, pegasus. Re:

1: Namespaces are mandatory. In terms of infrastructure, this allows for a number of things that were not possible in NuWiki. I won't get into this here. If you don't create too many namespaces, it should be easy to tell where articles are, and it's never really necessary to include anything but the article title when using the appropriate link BB-Code.

Can you tell me more about why Namespaces are necessary/needed? Most of my users would find them confusing.

[pegasus]

Namespaces separate different kinds of articles that serve specific functional purposes. If having multiple namespaces would be confusing for your users, I would suggest only creating 1 for content. There are a total of 4 (soon to be 5) that must be created for (generally) system use only.

The system spaces serve things like Books, Forum Headers, Templates, Special Pages, and docs that would not function properly otherwise.

Aside from that, you really only need to create 1 namespace for most content purposes.