Hi everyone,
XWiki is a platform for building wikis. Our default Wiki is a demo
wiki showing what can be done with XWiki. We need to improve it so
that it can stand the competition with the nicest wikis available out
there (and beat them! :)).
I've started a page to gather feedback from users and developers on
what should be improved to make our default wiki better.
It would be nice if you could all help by providing your own feedback
and experience of using XWiki. Feel free to edit and comment on the
following page:
http://www.xwiki.org/xwiki/bin/view/Idea/DefaultWikiImprovements
You can also answer and discuss on this thread if you want but
eventually we'll need to have everything on that page so that all
ideas are gathered together.
Then once we get all this feedback we could start prioritarizing the
different improvements that you suggest.
Thanks everyone for your help
-The XWiki Dev team
Hi,
I'd like to propose the following general principles for the V2
Architecture (http://www.xwiki.org/xwiki/bin/view/Idea/ArchitectureV2):
* XWiki Core API is made only of interfaces. These are all the
interfaces that are implemented by components
* XWiki Components are simple java classes (POJO) implementing the
XWiki interfaces.
* XWiki Core Distributions consist in XWiki Core + some chosen
components. Our current XWiki will be a Core Distribution.
* XWiki Containers are special modules that integrate XWiki in a
given container. For example: integration in Servlet Containers (this
means a web.xml file, servlet context listeners, packaging in a WAR,
etc), in Portlet Container, in J2ME environments, etc. XWiki
Containers depend on XWiki Core Distributions.
Are we ok with this?
If so, I'll move that to http://www.xwiki.org/xwiki/bin/view/Idea/
ArchitectureV2
Thanks
-Vincent
PS: I'll keep sending some Architecture ideas so that we start
shaping up our Architecture document and so that everyone has a clear
idea of what's happening and can participate.
How can I turn off the "shortcut" URLs where /bin/Space/Page is
interpreted as /bin/view/Space/Page?
(Specifically, I'm using mod_redirect to clean up the URL
architecture and need to assume that anything prefixed /bin that
isn't /bin/view needs to be passed through as an action.)
- - -
Hans Gerwitz
http://phobia.com/
Hi All,
I have had a search through the archives and couldn't find much on this
topic, though if there is a thread I have missed please point me in the
right direction and accept my apologies.
My primary question is has the project considered supporting the Apache
2.0 license (or similar)? We generally find this makes integration with
other OSS projects a lot easier as its much less restrictive then
GPL/LGPL which in turn attracts more folks, especially from corporate land.
I understand that LGPL may have been chosen to ensure that the community
is forced to release modifications back to the project, however we have
personally found that this works equally as well with the Apache 2.0
license and removes the extra confusion (we are programmers after all
not lawyers :) ).
A change to Apache 2.0 or a dual license if it was felt needed would
certainly get a big vote from myself.
regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
http://intient.com
Intient - "Open Source, Open Standards"
Hello,
I was wondering if there is a way to tag the whole blog entry and be able to display it later under the Tags page?
Thank you for your time and help in advance.
Regarding http://jira.xwiki.org/jira/browse/XWIKI-929
XWikiRightsServiceImpl list several categories of access rights: view, edit,
comment, delete, register, admin, programming. Each action is mapped to one
of these categories. For example, /viewrev/ is a 'view' action, /propupdate/
is an 'edit' action.
Currently, the most permissive right is "view", but some actions need an
even more permissive right. For example, if the wiki requires authentication
for viewing, then the skin will not be displayed.
We should add a new access right class, "unrestricted", which cannot be used
in the Access Rights Editor, but is used internally to allow some actions to
always be executed, regardless of the access rights of the user.
This raises some security issues, like what if the skin really shouldn't be
accessible? What if a plugin registers an unrestricted action, but nothing
should be unrestricted? For this, we can do the following:
- add an option in xwiki.cfg, 'security.allow_unrestricted', which can
disable unrestricted access; in this case 'unrestricted' behaves as 'view'.
- add an option in XWikiPreferences, which actions are allowed to behave as
unrestricted. Although some plugins by default register an action as
'unres', we can force this action to require 'view' rights.
We need to add this, a lot of users are complaining that the skin isn't
displayed, we just have to decide how do we secure this right.
Sergiu
--
http://purl.org/net/sergiu
Hi-
There exists:
http://jxdbcon.sourceforge.net/
Which apparently supports the setCatalog method that the native driver
lacks... Has anyone tried this, to allow virtual wikis?
-Tom
--
May 4, 1970: Alison Krause, Jeffrey Miller, Sandra Scheuer, William Schroeder.
Hi,
I'd like us to change the skin names for 1.0 B6. We need to do this
before the 1.0 release and now is a good time (actually already a bit
late but that's ok).
Here's the proposal:
1) Rename xwiki10b1/ into albatros/
Question: Should we name it with 2 's'. I've done a google fight and
"albatros" won. Is that correct?
http://www.googlefight.com/index.php?
lang=en_GB&word1=Albatros&word2=Albatross
2) Rename default/ into dodo/
3) Remove new/ altogether
4) Rename xwiki10/ into finch/
5) set xwiki.defaultskin= albatros and xwiki.defaultbaseskin=albatros
WDYT?
Thanks
-Vincent
Hi everyone,
I've just started a page where users can learn how to configure XWiki:
http://www.xwiki.org/xwiki/bin/view/AdminGuide/Configuration
Feel free to add configuration topics in there. XWiki is
configuration rich and for the moment there are only a few
information on there. We need more!
Thanks
-Vincent
I've been using xwiki for a week or so, and now I want to change the
functionality a bit. After importing the recommended xar file, I see
the spaces navigation on the right under the search field. Right now it
shows all spaces (even those the user doesn't have permission to see)
and all pages within that space. I'd like to change the navigation so
that only viewable spaces and top level pages (those without a parent)
are shown. However, I can't figure out what file or files I need to
modify. I'm assuming that it's something in the /skins/xwiki10b1
folder.
Anyone have any suggestions for me?
Thanks,
Eric