Hello devs,
as suggested before, I would like to make the main page of the wiki a
full dashboard, namely to relocate the welcome message in a gadget so
that the type of page of the main page is more clear. See this two
screenshots about how it could look (one is with default style, other is
with panels style).
http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/WikiDashbo…http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/WikiDashbo…
(also
http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/MainDashbo… ) if you want to import it in your own wiki and play with it.
I want to discuss the following points now:
1/ is the title "Wiki Dashboard" ok for the main page of the wiki?
2/ Is the welcome message visible enough, is it accessible to users and
explanatory about what the page is about and what they could do next?
3/ what would be the relation now with the old Main.Dashboard page,
which, as you can see in the quick links panel, is a "Wiki Dashboard"
itself? Should it be the same page? if so, is it ok that the welcome
message appears on the wiki dashboard? if they're not the same page then
it's a bit strange that they're called the same but 2 different pages...
Should we rename one?
Technically the welcome message is written in a new page, Main.Welcome,
and then included in a gadget in the dashboard. This page can be
translated for getting the message in different languages.
WDYT?
Thanks,
Anca
Hi,
In order to get more community help and to open up our xwiki.org infrastructure to the community we could introduce an infra(a)xwiki.org mailing list which would be the place to:
- talk about infrastructure. By infra I mean machines and their configuration + xwiki.org + myxwiki.org
- receive emails from xwiki.org and myxwiki.org when XE/XEM restarts (there's a script to restart them automatically when an instance doesn't respond within 30 seconds for ex). These emails contains thread dump + other information useful to debug and understand why the instance wasn't responding.
WDYT?
Thanks
-Vincent
Hi devs,
We need to name stable branches in git repositories and we can't use
the same name as in svn (xwiki-enterprise-3.0) since it will conflict
with tags names.
So here are some proposals with xwiki-enterprise repository as example:
1. xwiki-enterprise-3.0-SNAPSHOT
2. stable-3.0
3. 3.0-SNAPSHOT
4. xwiki-3.0 (the current one)
WDYT ?
+1 for 2, that's what it is: stable branch 3.0 plus it's short and
easy to remember
-1 for 4, it does not make any sense to me
1 is probably what makes the most sense but it's a pain to write and
would be nice to have the same thing in all repositories
+0 for 3.0-SNAPSHOT, make sense but it's not very nice
--
Thomas Mortagne
Hi Devs,
I'd like to introduce a new configuration property that would define
at which level users should be handled in a farm.
See the proposition about the new entry in xwiki.properties, it should
be self-explanatory:
--------------------------------8<--------------------------------
#-# [Since 2.5M1]
#-# Define at which level users and groups should be handled in the
farm. Available modes:
#-#
#-# mixed (default):
#-# - user registration available in the main wiki and local wikis
#-# - users from the current wiki and the main wiki will be displayed
in the rights interface and user suggests
#-# - user administration is present in all the wikis
#-#
#-# local:
#-# - user registration available in the main wiki and local wikis
#-# - only users from the current wiki will be displayed in the rights
interface and user suggests
#-# - user administration is present in all the wikis
#-#
#-# global:
#-# - user registration available in the main wiki only, the register
link in local wikis will point to the main wiki
#-# - only users from the main wiki will be displayed in the rights
interface and user suggests
#-# - user administration is present in the main wiki only
core.virtual.users=mixed
-------------------------------->8--------------------------------
More details are available here:
http://dev.xwiki.org/xwiki/bin/view/Design/UsersModule
WDYT ?
Thanks,
JV.
Hi,
After having a bit of thought about the XE/XEM Home Page investigations,
I don't think the "home page" investigation is relevant.
I'd like to propose to split this investigation into 2 investigations:
1/ "XWiki in the first 5 minutes" investigation
How to improve XWiki's User Experience in the first 5 minutes with
simple or more complex changes in the home page but for all initial
actions that are made by a user/administrator when he starts with XWiki.
The objective of this investigation would be to list small changes that
could be implemented in the coming releases and list larger work that
would need their own investigation.
2/ XEM/Workspaces investigation
This investigation is about the next generation Multi-Wiki management
including creation of Workspaces with the management of application. New
features would be part of that as well as a redesign of the Wiki
creation and management UI.
On this matter there is already work in the Wiki 3.0 project with a
prototype delivered of this work, which is a great basis for discussion,
in which we need to bring some guidelines about the objective of these
features as well as User Experience proposals by Cati.
WDYT ?
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
We've decided with the new reorg following the move to github that xwiki-platform was a collection of libraries/resources that work together (and released together) that can be used by top level projects (XE for example) to build a running application.
We've also implicitly decided that we didn't have a notion of "core" and that all libs/resources were at the same level (all in xwiki-platform-core/).
As a consequence it doesn't really make sense for xwiki-platform to release a WAR since we wouldn't know what to put in it (since there's no notion of core). Right now it's a bit a mess with no logic (for example the watchlist is not in it but other modules are).
I'm thus proposing to transform xwiki-platform-web in 1 or 2 modules instead (resources and templates) that generate a zip/jar that only contains resources, and that it's up to the top level projects (like XE) to build their own distribution by pulling in whatever libs/resources they want from xwiki-platform.
Note that this solves an issue we currently have with Maven. If a top level project depends on the platform web but also on other modules that transitively depend on artifacts bundled in the platform war then we can get duplicate jars in the resulting war since maven sees the war artifact as a blob and doesn't know about the dependencies that were included in it.
Here's my +1
Thanks
-Vincent
Hi devs,
This is a thread to discuss what kind of title behavior we want in the future. I've listed some topics I consider open below. Could you give me your opinion about them?
1) Should we force titles to be mandatory by default
2) Should we merge page names and titles in the UI (ie only expose titles and compute page names based on it)
3) Do we want titles to be generated from content if the title is empty or not. If 1) is agreed then there'll always be a title set so this is probably not needed
4) Should we allow wiki syntax in the title field and make that field a textarea rather than a single line string (to allow scripts to generate titles, this is useful for applications for example). Note that currently the title field can only contain velocity and no wiki syntax AFAIK.
Any other topic to discuss related to titles?
Thanks
-Vincent
Hi,
First of all I would like to thank XWiki for selecting me to the
Google Android Client for XWiki project through the GSOC. As a
beginning I'm currently studying on building XWiki public repositories
like xwiki-enterprise, xwiki-manager, xwiki-platform etc. so that I
can get the domain knowledge. I hope to fix some jira issues in these
repositories. Can anybody tell me some other way to get proper
understanding in XWiki appropriate to this Android project?
Thank you,
Chamika Weerasinghe