It seems we need to:

   - refer the privacy policy (either by the ASF or - if not sufficient -
   our own)
   - have a option to opt out on our website (regarding cookie policies).

I don't feel that a suggestion to add '"Google Analytics opt-out browser
add-on' (as suggested in the JIRA issue) will be in the best interest of
our project.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Apr 17, 2017 at 9:57 AM, Jacques Le Roux <
[email protected]> wrote:

> So it's OK,
>
> Do we all agree with the request at INFRA-13701? Is it the best way?
>
> Thanks
>
> Jacques
>
>
>
> Le 16/04/2017 à 23:00, Jacques Le Roux a écrit :
>
>> Thanks James,
>>
>> I posted your comment at https://issues.apache.org/jira
>> /browse/INFRA-13701?focusedCommentId=15970517&page=com.
>> atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel#comment-15970517
>>
>> Jacques
>>
>>
>> Le 18/03/2017 à 12:28, james yong a écrit :
>>
>>> Hi,
>>>
>>> According to "7. Privacy" section under Google Analytics Terms of
>>> Service at
>>> https://www.google.com/analytics/terms/us.html, we need to post a
>>> Privacy
>>> Policy on the use of Google Analytics which uses cookies to collect
>>> anonymous data.
>>>
>>> We can ask the users to install "Google Analytics opt-out browser
>>> add-on" at
>>> https://tools.google.com/dlpage/gaoptout if they do not wish to
>>> participate
>>> or be tracked.
>>>
>>> Regards,
>>> James Yong
>>>
>>>
>>> taher wrote
>>>
>>>> Reading the specifications in [1] implies tracking of user information
>>>> like
>>>> ip address and location. So the first question to ask is .. do we need
>>>> any
>>>> legal disclaimer? I don't speak legaleze so maybe we need input from
>>>> specialists in that area?
>>>>
>>>> The next question to ask is what do we need to track? What is our
>>>> objective
>>>> or the information we want to capture? Is it simply a hit count per
>>>> page?
>>>> Time spent? Others? And how should we share this information? Do we
>>>> create
>>>> a frequency report?
>>>>
>>>> I guess we lack an overall plan on this task. What do we want to do and
>>>> how
>>>> will we do it are important questions to answer before going to the
>>>> trouble
>>>> of implementing this feature.
>>>>
>>>> [1]
>>>> https://developers.google.com/analytics/devguides/collection
>>>> /analyticsjs/
>>>>
>>>> On Mar 18, 2017 1:13 PM, "Jacques Le Roux" &lt;
>>>> jacques.le.roux@
>>>> &gt;
>>>> wrote:
>>>>
>>>> I created https://issues.apache.org/jira/browse/INFRA-13701 <
>>>>> https://issues.apache.org/jira/browse/INFRA-13701> for the analytics
>>>>> script addition, but as Michael rightly said on Hipchat we need to
>>>>> discuss
>>>>> this here before
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>> Le 17/03/2017 à 18:41, Jacques Le Roux a écrit :
>>>>>
>>>>> Hi James,
>>>>>>
>>>>>> Maybe one thing we can do is attach the js script to the "no spam"
>>>>>> header. It's showing on the top of every OFBiz wiki pages and only
>>>>>> there.
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>> Le 17/03/2017 à 14:10, james yong a écrit :
>>>>>>
>>>>>> Hi,
>>>>>>>
>>>>>>> I am not sure if this is possible. Would like to suggest the use of
>>>>>>> Google
>>>>>>> Analytics in Confluence. This will allow the team/committee to gather
>>>>>>> info
>>>>>>> on the users' demographic, know the frequently accessed wiki pages
>>>>>>> and
>>>>>>> give
>>>>>>> insights on how to optimize user experiences with limited manpower.
>>>>>>>
>>>>>>> Regards,
>>>>>>> James Yong
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context: http://ofbiz.135035.n4.nabble.
>>>>>>> com/Using-Google-Analytics-in-Confluence-tp4703557.html
>>>>>>> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://ofbiz.135035.n4.nabble.
>>> com/Using-Google-Analytics-in-Confluence-tp4703557p4703616.html
>>> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>

Reply via email to