Greetings developers, This email documents a hallway conversation I had with a Geode committer today, and I would like to get a consensus on a policy about website analytical data.
A website update the middle of last December clobbered a Google Analytics tag that the Pivotal Community Marketing team had been using to measure Apache Geode website activity in terms of hits, unique visitors, etc. This was discovered today as we were doing our monthly survey of community statistics. Our public Bitergia dashboard is a great way to monitor community engagement: http://projects.bitergia.com/apache-geode/browser/ Website analytics aren't so easily made public. In fixing the clobbered tag, the committer rightfully asked what should be appropriate to maintain transparency for the Apache Geode community. I offer the following policy, and if there's a lazy consensus, will follow this going forward. Access to the Google Analytics account and tag monitoring geode.incubator.apache.org website will be made available to the same members of the PPMC of Apache Geode who expressed an interest on being able to use the social media handle @apachegeode. Access to said account will be made available to any member of the PPMC that expresses an interest. Going forward a report of prior months web statistics will be posted to [email protected] at the beginning of each month by one of the PPMC members with access to the analytics account. Are we generally ok with this approach? A more public option would be if there's statistics collected on Github about website activity, but I don't see a way to collect this data on the Apache mirror. -- Greg Chase Global Head, Big Data Communities http://www.pivotal.io/big-data Pivotal Software http://www.pivotal.io/ 650-215-0477 @GregChase Blog: http://geekmarketing.biz/
