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 :
On 01/04/2011 10:28 PM, Arnaud bourree wrote:
Hello,
2011/1/4 Vincent Massol<vincent(a)massol.net>et>:
>
> On Jan 4, 2011, at 6:59 PM, sorinello wrote:
>
>>
>> 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"
This is not about a feature comparison where we select key features to
prove that XWiki is the best compared to others. So I agree that
"competitors" might not be the best word here.
This is more like a list of other products that users take into
consideration "instead of" or "along with" XWiki, so other products
that
overlap some of the usage scenarios of XWiki.
The end result (as far as I understand from Gregory's initial message)
is not to be able to compare XWiki with "the competition", but to
extract a list of features that the community values in other products,
and which they would like to see in XWiki.
For example, just today I've seen mentioned that "Wordpress has many
more skins available". Thus, the product in this case is WP, and the
desired feature is a broad collection of skins/themes that the users can
choose for their wiki.
> I'm ok with any (even Competitor is ok
with me).
>
> On a side note, it's always difficult to compare 2 products since there are
multiple angles and it's hard to have people from both products agree on the
comparison. I'm not sure where this will lead...
We don't want a feature matrix, we want a "Feature F present in Product
P that's missing in XWiki" list. And to get there, we're currently
gathering the list of products to look at.
>> 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.
No, we don't want that now.
Yes but
this shouldn't be linked to this page. We should have such a form accessible probably
from the download page. The feedback result should probably be sent to the list (devs
list?).
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
That would be nice, but it's not the subject of this thread.
>
> This is becoming a bit off topic for this thread.
>
> Thanks
> -Vincent
>
>>
>> WDYT ?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users