3 Sep
2013
3 Sep
'13
1:06 p.m.
On Aug 27, 2013, at 11:49 AM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
I've started a design page for this at
http://dev.xwiki.org/xwiki/bin/view/Design/ActiveInstalls
(and created the jira issue at http://jira.xwiki.org/browse/XWIKI-9401)
Compared to the original proposal and after talking to Thomas we agreed that this should
be done independently of the EM module.
WDYT of the architecture?
I've now implemented the first version of it and I'm ready to commit it in
platform.
If nobody objects, I'll add this for 5.2M2 in the coming days before the 9th (going to
do some cleanup before committing).
Thanks
-Vincent
Thanks
-Vincent
On Oct 28, 2011, at 4:38 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
I think it would be great to have some indication of how many active instances of XWiki
are out there in the wild. The idea is not so much to know the figure but to see how this
figures evolves and thus to see if we're doing things right. It will also give us
information about how quickly or slowly our user base upgrades from version to version.
Here's my proposal:
* When installing XWiki on a clean DB (ie first time install) generate a unique id and
store it in the DB (similar to the version we're storing in the DB but using some
UUID). Thus when an install is upgraded the same id is preserved.
* When the Extension Manager is used and thus connects to extensions.xwiki.org (default
extension repository), this unique ID is sent too.
* In addition the version of XE is sent too
* On extensions.xwiki.org side, we only log the unique ID/XE version **without** logging
the IP or any other information thus ensuring that the ID remains completely anonymous
* We display a counter on xwiki.org about the # of active instances of XE with a graph
about XE versions used
WDYT?
Thanks
-Vincent