13 May
2009
13 May
'09
noon
Hi Sergiu
Hi Vencent
Thank you for your answer and sorry it took me so long to respond.
Vincent Massol wrote:
That's great. I think you should make it available
on code.xwiki.org
(plugin section for the plugin) with a download - you can also put the
sources there for now.
This weekend I should have time to look into it and upload the code.
Then the next step would be to contribute the source
in our SVN. For
this I can see 2 paths:
1) You want to maintain your code (best) along with others. We could
do something we've talked about for a long time and create a
contributor repository (under the xlet standalone project name for
ex).
2) You don't want to maintain your code (less good, depends on quality
of existing code). In this case we would need to see if one or several
existing committers would be interested in taking over the maintenance
of it and if so we should start a vote to decide if this is something
we want to maintain in the main SVN repo and thus in the XWiki
project's platform. For this we need to see the code first and the
best way is to create a jira issue with the code attached.
I would be ready to maintain the code. I will leave the decision on
the how and where to place the code to you. Feel free to chose the
option you like best.
Sergiu Dumitriu wrote:
We welcome feedback about your usage of XWiki, what
you like and what
you dislike, so that we can improve it to meet the users'
expectations.
Since you're using it for quite a long time, I suppose you have enough
to talk about.
We are using xwiki mainly as base for our content management /
information management system. The focus is on easy accessible in
place editing. To be a little more specific a few examples:
- Editing page content, banners, ... in place and not having to search
for it in a backend.
- Adding, renaming, moving pages (in the menu) directly on the page
using a right click context menu.
- different plugins as e.g. Photo albums, Blog (own / extended version
of xwiki Blog), Shop
So we use overall the API and the scripting possibilities of xwiki and
not the front end since we use our own skins. For most actions we have
written our own versions (view, edit, import, ...).
What I like XWiki is its flexibility. Its easy to add plugins and
include the code on a page. I also like the multilingual capabilities
(different language content as a users, dictionary as a developer) and
the versioning with the possibility to trace changes. Another great
tool is the classes / objects model, especially with the possibility
to use custom mappings for "heavy used" classes.
Thanks
Edo