Hi Guillaume,
I understand your disappointment but:
* By default stats are off because they're not good enough and are
too-performance intensive
* Most users don't use them
* The UI for the stats app is suboptimal ATM
* We're removing more and more apps from the default XE since we now have
the EM and I don't think the stats app is a must have for all wikis.
* Using google analytics or some other web server stats tools usually
provide better information than we do
The stats app will stil be supported by the xwiki dev team and we'll still
work on improving it. I'm not suggesting to retire it.
We can bring it back in some flavors in the future. We can also VOTE to
move it back by default when we fix the performance + UI issue (it's a one
line to change to have it in by default or not).
Thanks
-Vincent
On Wed, Nov 20, 2013 at 10:52 AM, Guillaume Lerouge <guillaume(a)xwiki.com>wrote;wrote:
Hi,
I'm a bit disappointed about this discussion. To me, statistics are one of
the key features of XWiki. On many projects I see, XWiki statistics data is
used to provide insights and information about how the wiki is used and
what content is found valuable by users. Putting them away (even just
through the EM) sounds like something suboptimal. It's exactly as if we
said "search is not working well enough, it's not a key wiki competency (as
opposed to editing pages) so we should push it away".
I'd much prefer seeing proposals on how to improve this module instead of
pushing it away. I am intent on advocating on behalf of this feature during
the next roadmap cycle, so I'd be really sad to see it pushed away just
before then.
Guillaume
On Mon, Nov 18, 2013 at 6:28 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
On 11/18/2013 10:56 AM, Sorin Burjan wrote:
> Hello,
> Is it ok to split the two entities ?
> If we remove only the front-end (Stats Application) and still bundle
with
> the back-end, what will be the use of the
back-end ?
> IMO we are splitting a possible functionality of XWiki in 2, leaving
one
module in
one side (bundled) and the other not bundled.
It looks messy from my POV.
Even though it is bundled, the plugin is not really active. It's just
code that's sitting there, taking up permgen space. And there are many
other parts of the old core that aren't used, but removing things from
oldcore is a time costly process.
--
Sergiu Dumitriu
http://purl.org/net/sergiu
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs