[Fiware-technical-committee] Google Analytics on readthedocs and fiware wiki / specs

Davide Dalle Carbonare davide.dallecarbonare at eng.it
Fri Jul 15 15:26:06 CEST 2016


Dear all, Jose,
  I definitely support the usage of Google Analytics for all the public
services we have ...
We're using them for the Catalogue and Academy since a lot of time and
right now I was about to create some export for Manuel (Escriche).
I think they can be of interest to many of you so I attach them also to
this email (page views between 1/5/2016 and 14/7/2016).

Take into account that in Analytics is possible to open the access to a
google account for analytical purposes only (not for administrating the
tracking process).

Kind Regards,
Davide


2016-07-15 14:57 GMT+02:00 Alex Glikson <GLIKSON at il.ibm.com>:

> What if we could use a single FIWARE-wide Google Analytics account?
> Furthermore, what if all (or most of) the RTD materials resided under the
> "fiware" namespace, so that all the changes could be applied uniformly and
> in an automated/scripted manner?
>
> As a general comment - I think we MUST start thinking more in terms of
> single dev community - not just in terms of catalogue, portal, lab and
> workflow, but also in terms of GE developer experience and convenience.
> Luckily, we have github and docker hub available for all - but that is not
> enough. We need to start building dev infra, to enforce FIWARE best
> practices, and make the life of FIWARE GE developer easier.
>
> Regards,
> Alex
>
>
>
>
> From:        Pablo Fernández Moniz <pablofernandezmoniz at gmail.com>
> To:        JOSE MANUEL CANTERA FONSECA <
> josemanuel.canterafonseca at telefonica.com>
> Cc:        Alex Glikson/Haifa/IBM at IBMIL, "
> fiware-technical-committee at lists.fiware.org" <
> fiware-technical-committee at lists.fiware.org>
> Date:        15/07/2016 03:27 PM
> Subject:        Re: [Fiware-technical-committee] Google Analytics on
> readthedocs and fiware wiki / specs
> ------------------------------
>
>
>
> Hello,
>
>  Right Jose Manuel, currently we only contemplate the way to do it
> manually.
>
>  If you have any doubt to do it, please, do not hesitate to contact us.
>
> Kind Regards,
>
>
> 2016-07-15 13:17 GMT+01:00 JOSE MANUEL CANTERA FONSECA <
> *josemanuel.canterafonseca at telefonica.com*
> <josemanuel.canterafonseca at telefonica.com>>:
> I’m afraid each RTD site has to be configured individually, but, Pablo,
> correct me if I’m wrong.
>
> *De: *Alex Glikson <*GLIKSON at il.ibm.com* <GLIKSON at il.ibm.com>>
> *Fecha: *viernes, 15 de julio de 2016, 14:11
> *Para: *Jose Manuel Cantera Fonseca <
> *josemanuel.canterafonseca at telefonica.com*
> <josemanuel.canterafonseca at telefonica.com>>
> *CC: *"*fiware-technical-committee at lists.fiware.org*
> <fiware-technical-committee at lists.fiware.org>" <
> *fiware-technical-committee at lists.fiware.org*
> <fiware-technical-committee at lists.fiware.org>>, Pablo Fernández Moniz <
> *pablofernandezmoniz at gmail.com* <pablofernandezmoniz at gmail.com>>
> *Asunto: *Re: [Fiware-technical-committee] Google Analytics on
> readthedocs and fiware wiki / specs
>
> Good idea, but can we somehow make it once/automated, and not separately &
> manually by each GE owner? The latter is not scalable, and will surely be
> error-prone and will cause trouble.
>
> Regards,
> Alex
>
>
>
>
> From:        JOSE MANUEL CANTERA FONSECA <
> *josemanuel.canterafonseca at telefonica.com*
> <josemanuel.canterafonseca at telefonica.com>>
> To:        "*fiware-technical-committee at lists.fiware.org*
> <fiware-technical-committee at lists.fiware.org>" <
> *fiware-technical-committee at lists.fiware.org*
> <fiware-technical-committee at lists.fiware.org>>
> Cc:        Pablo Fernández Moniz <*pablofernandezmoniz at gmail.com*
> <pablofernandezmoniz at gmail.com>>
> Date:        15/07/2016 03:04 PM
> Subject:        [Fiware-technical-committee] Google Analytics on
> readthedocs and        fiware wiki / specs
> Sent by:        *fiware-technical-committee-bounces at lists.fiware.org*
> <fiware-technical-committee-bounces at lists.fiware.org>
> ------------------------------
>
>
>
> Dear friends,
>
> In order to improve our data on the popularity of FIWARE and its GEs, I’m
> proposing to use Google Analytics over the readthedocs documentation portal
> of each GEri. Our colleagues of ULPGC have prepared this guide (draft) on
> how to do so.
>
> It documents the procedures to be followed , thanks to ULPGC for preparing
> this!
>
>
> <https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Configure_Google_Analytics_for_RTD>
>
> *https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Configure_Google_Analytics_for_RTD*
> <https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Configure_Google_Analytics_for_RTD>
>
> It would be great to* have the ok from the TSC on making this mandatory *for
> each of the FIWARE projects. An agenda item for next sessions would be
> great.
>
> In addition my recommendation is*to use Google Analytics on the Wiki and
> on the published open specs and APIs. *
>
> Thanks for your consideration
>
> All the best
>
> PS: I will be on vacation until August 10th
>
>
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
> _______________________________________________
> Fiware-technical-committee mailing list
> *Fiware-technical-committee at lists.fiware.org*
> <Fiware-technical-committee at lists.fiware.org>
> *https://lists.fiware.org/listinfo/fiware-technical-committee*
> <https://lists.fiware.org/listinfo/fiware-technical-committee>
>
>
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
>
>
> --
>
> Pablo Fernández Moniz
> GIT Analyst
>
> *Web* <http://www.pablofm.com/>    *Linkedin*
> <http://www.linkedin.com/in/pablofernandezmoniz/>   *Twitter*
> <http://www.twitter.com/monizpablo>
>
>
>
> _______________________________________________
> Fiware-technical-committee mailing list
> Fiware-technical-committee at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-technical-committee
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160715/e708a4c8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FIWARE Academy Analytics All Web Site Data Pages 20160501-20160714.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 9627 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160715/e708a4c8/attachment.xlsx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FIWARE Catalogue Analytics All Web Site Data Pages 20160501-20160714.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 31650 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160715/e708a4c8/attachment-0001.xlsx>


More information about the Fiware-technical-committee mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy