30 Jul
2013
30 Jul
'13
4:29 p.m.
On Jul 30, 2013, at 4:15 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
On 07/30/2013 08:28 AM, Vincent Massol wrote:
I'm not sure this is needed. XWiki is all about the notion of wiki… even in its name.
The generic name "wiki" seems a much better name to me than anything else:
* it's a set of pages that can be edited/modified by users with links between pages,
using some syntax, etc.
I don't think we need to change that. Any other name would be awkward IMO.
Definitely +1 for B. I really think we need to
drop the concept of workspaces and come back to the concept of wiki/subwiki. It's much
simpler for the user. What we call "workspace" can be seen as a configuration
for a wiki, i.e. the usage of global users only.
I disagree. For us XWiki veterans it's obvious that an XWiki wiki is an
all-powerful collection of applications and pages that can do anything
we want it to. But for users, a wiki is Wikipedia, where you can find
documentation written by amateurs that's hasn't been proof-read by a
real professional. It takes months or years of using a wiki to shift
from the external viewer bad opinion to the internal collaborator good
opinion of the term "wiki".
So "wiki" is a bad name for users. I think "workspace" is a much
better
name than "wiki", although it's far from perfect. First of all because
it creates confusion between a "space" and a "workspace (wiki)".
So, what better word describes a "collaboration space" than
"workspace"?
Some random ideas, most of them bad:
- node
- workgroup
- community
- rename space to directory and we can use space or workspace for the
current "wiki"
- virtual server
- environment
- sandbox
- appspace
- office
- location
- rack
- stack
- instance
- room
- workroom
- desk Let's not forget that some of the instances are
customized so much that
users don't even know they're using a wiki, so just seeing the word
"wiki" might cause confusion: "Wiki? What wiki? I'm using our
company's
internal Foobars application!". So it would be a good idea to make this
term configurable.
If the instance is customized so much that it doesn't look like a wiki, then whoever
did this customization can easily also customize the translation resources to pick
whatever suit their needs! ;)
For example, if the wiki is used as a projects wiki and they want to have one project =
one wiki, they could rename "Wiki" to "Projects".
We'll never be able to use a specialized name by default so we might as well stick
with "wiki" which is the best name for what it is… a wiki ;-)
Thanks
-Vincent