You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pirk.apache.org by ea...@apache.org on 2016/07/20 23:38:27 UTC

incubator-pirk git commit: configuring google analytics

Repository: incubator-pirk
Updated Branches:
  refs/heads/gh-pages 22fa4e21f -> 838e508df


configuring google analytics


Project: http://git-wip-us.apache.org/repos/asf/incubator-pirk/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-pirk/commit/838e508d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-pirk/tree/838e508d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-pirk/diff/838e508d

Branch: refs/heads/gh-pages
Commit: 838e508df1dd1eb5ee251ffa7a927d5dfcc54342
Parents: 22fa4e2
Author: eawilliams <ea...@apache.org>
Authored: Wed Jul 20 19:37:58 2016 -0400
Committer: eawilliams <ea...@apache.org>
Committed: Wed Jul 20 19:37:58 2016 -0400

----------------------------------------------------------------------
 _layouts/skeleton.html | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-pirk/blob/838e508d/_layouts/skeleton.html
----------------------------------------------------------------------
diff --git a/_layouts/skeleton.html b/_layouts/skeleton.html
index 125d247..8ffc483 100755
--- a/_layouts/skeleton.html
+++ b/_layouts/skeleton.html
@@ -65,12 +65,11 @@
   (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
   (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
   m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
-  })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
 
-  if (ga.hasOwnProperty('loaded') && ga.loaded === true) {
-    ga('create', 'UA-50934829-1', 'apache.org');
-    ga('send', 'pageview');
-  }
+  ga('create', 'UA-81114308-1', 'auto');
+  ga('send', 'pageview');
+  
 </script>
 </head>
 <body style="padding-top: 100px">


Re: incubator-pirk git commit: configuring google analytics

Posted by Ellison Anne Williams <ea...@gmail.com>.
I agree. Thus far, I have set up the ApachePirk Twitter and
ApachePirkWebsite Google Analytics accounts. I am happy to make those
community creds for the PMC members.



On Thu, Jul 21, 2016 at 6:46 AM, Tim Ellison <t....@gmail.com> wrote:

> On 21/07/16 00:38, eawilliams@apache.org wrote:
> > Repository: incubator-pirk
> > Updated Branches:
> >   refs/heads/gh-pages 22fa4e21f -> 838e508df
> >
> >
> > configuring google analytics
> >
>
> This raises the question about who should have access to the accounts
> held outside the ASF that are associated with Apache Pirk; for example,
> this Google analytics account, and the Pirk Twitter account.
>
> Ideally, it won't just be one person with sole access; although it may
> end up being just one volunteer who posts tweets, etc.
>
> I suggest that admin access be given to anyone on the (P)PMC who
> requests it, since it is the entire PMC that effectively manages the
> project on behalf of the foundation.
>
> Some projects choose to regularly post analytics reports to the dev
> list, others will just do it upon request; but in either case the data
> that is gathered from the analytics would generally be publicly
> available to anyone who asks.
>
> Thoughts?
> Tim
>

Re: incubator-pirk git commit: configuring google analytics

Posted by Tim Ellison <t....@gmail.com>.
On 21/07/16 00:38, eawilliams@apache.org wrote:
> Repository: incubator-pirk
> Updated Branches:
>   refs/heads/gh-pages 22fa4e21f -> 838e508df
> 
> 
> configuring google analytics
> 

This raises the question about who should have access to the accounts
held outside the ASF that are associated with Apache Pirk; for example,
this Google analytics account, and the Pirk Twitter account.

Ideally, it won't just be one person with sole access; although it may
end up being just one volunteer who posts tweets, etc.

I suggest that admin access be given to anyone on the (P)PMC who
requests it, since it is the entire PMC that effectively manages the
project on behalf of the foundation.

Some projects choose to regularly post analytics reports to the dev
list, others will just do it upon request; but in either case the data
that is gathered from the analytics would generally be publicly
available to anyone who asks.

Thoughts?
Tim