Hi all, hi Greg, 2010/12/20 Gregory GUENEAU <ggueneau(a)me.com> +1 Can you create a page somewhere to gather the informations? I will try to find time after the holidays to add a few solutions.

Hi! Vincent Massol wrote: May I add to "others": Joomla (http://www.joomla.org/) Moodle (http://moodle.org/) OpenCMS (http://www.opencms.org) BlackBoard (http://www.blackboard.com/) Thanks! -- Ricardo Rodríguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems

Hello Team. I have 2 proposals to make : 1. Rationale: "XWiki competitors" is a little bit too aggressive. We should not use so harsh words like competitor, rivals, etc. So I am proposing to replace "XWiki competitors" with: 1.1. "Other alternatives to XWiki" 1.2. "Alternatives to XWiki" 1.3. "Similar products to XWiki" 1.4. "Similar solutions to XWiki" 2. If a user is not happy with XWiki and wants to switch to another alternative from the page, we should allow that user to "manifest" it's unhappiness via some sort of form. Maybe we can link the XWiki.org Survey to this page, so at least we hopefully get some feedback from the leaving user. WDYT ? Regards, Sorin B. -- View this message in context: http://xwiki.475771.n2.nabble.com/request-Comparing-XWiki-to-other-solution… Sent from the XWiki- Users mailing list archive at Nabble.com.

Hello, 2011/1/4 Vincent Massol <vincent(a)massol.net>et>: Why not a features matrice like we can found at 7zip, WinRAR, WinZip websites For example: xwiki sharepoint Access from Office application V V Google Calandar integration V X Infopath integration X V Arnaud.

On this note, it would be right to put a link to Wikimatrix http://www.wikimatrix.org/ It is partly because of there that I chose Xwiki for our Office. If you add Drupal, what other CMS systems get a nod as well, perhaps they could be a separate grouping. Where does a product like Liferay fit in? Sort of a near too but not quite a wiki group, if you were not aware Liferay has a wiki built in. I would add to the page but I dont have a log in for Xwiki.org Cheers Peter On 04/01/2011, at 9:47 PM, Vincent Massol wrote:

Liferay has only the rendering component of jspwiki integrated. The resulting wiki is very basic. I have just moved the office from liferay to xwiki because of the flexibility of the latter. Rgds, Tim Sent from my iPhone On 5 Jan 2011, at 00:01, Peter McLarty <peter.mclarty(a)pacificdbms.com.au> wrote:

Hi I should explain what i have in mind regarding competition evaluation by the community. I talk about competition, because even in the OpenSource world, we can talk about competition, because after all, XWiki intends to be the best wiki, no ? This project should be organized as following : Step 1 : identify - identify the real competition (what are the real choices users have when they want to build an intranet, a community, or so on, and these choices are not only in the OpenSource world !) - identify the real user need when they balance XWiki against a competitor Step 2 : evaluate - evaluate the strength and weaknesses of XWiki vs the competition, at the solution level and the feature level (a qualitative evaluation, not quantitative, there is already lots of quantitative studies such as wikimatrix, we need more smart evaluation) - evaluate the objective and subjective differences of XWiki, with user feedbacks, try to do the same with biggest competitors - list the competitive advantages of XWiki and each competitor (quite same question, as previous, but with another angle) Step 3 : analyse - for each feature, provide a comparison study (probably the biggest and most difficult work here) - identify critical things missing in XWiki - analyze the tendencies of the market (grab infos about others roadmaps, announcements, etc.) - balance the result vs. user real needs Step 4 : publish - at the end, publish in the community a white paper (precise content to be defined, but with the material defined here), the idea is to have a synthetic document to help users evaluate xwiki against others, and to see if XWiki fits their needs (it is better to prevent any unsatisfaction) - and of course feed XWiki community with this info in the roadmap process (easier to set up priorities, and input information for feature design) This is quite a medium term work (should take a couple of month), but it will -i think- really benefit the dev community, and also the attractiveness of xwiki.org website. Anything here will be done in the open. If some community member provides sensible info, we will of course care about confidentiality. Best Gregory Le 4 janv. 2011 à 23:11, Sergiu Dumitriu a écrit :