Stats Collection issueshttps://lab.civicrm.org/infra/stats-collection/-/issues2023-04-03T15:51:03Zhttps://lab.civicrm.org/infra/stats-collection/-/issues/15Cleanup old data2023-04-03T15:51:03ZbgmCleanup old dataThe tables have become rather huge and not all of it is relevant.
```
--- /var/lib/mysql/stats
8.9 GiB [##########] extensions.MYD
6.5 GiB [####### ] entities.MYD
3.5 GiB [### ] entities.MYI
2.6 GiB [## ...The tables have become rather huge and not all of it is relevant.
```
--- /var/lib/mysql/stats
8.9 GiB [##########] extensions.MYD
6.5 GiB [####### ] entities.MYD
3.5 GiB [### ] entities.MYI
2.6 GiB [## ] extensions.MYI
1.8 GiB [## ] stats.MYD
```bgmbgmhttps://lab.civicrm.org/infra/stats-collection/-/issues/8Get stats on PRs2019-03-26T13:52:34ZcivideskGet stats on PRsMight also be nice to track PRes: how many submitted, open, closed, merged. Stats by month so we can see how CiviCRM dev is slowing/accelerating, stats by people to see top PR authors/reviewers/commenters, stats by status, by CiviCRM ver...Might also be nice to track PRes: how many submitted, open, closed, merged. Stats by month so we can see how CiviCRM dev is slowing/accelerating, stats by people to see top PR authors/reviewers/commenters, stats by status, by CiviCRM version/branch, resolution for closed PRs (merged/rejected/closed), needs to be rebased?https://lab.civicrm.org/infra/stats-collection/-/issues/7Generate Gitlab issue statistics2019-03-25T22:28:02ZJoeMurrayGenerate Gitlab issue statisticsWe don't use JIRA anymore, and we do use lab.c.o. Update the tracking to use our current system.We don't use JIRA anymore, and we do use lab.c.o. Update the tracking to use our current system.https://lab.civicrm.org/infra/stats-collection/-/issues/6Collect payment processor usage stats2019-03-28T06:46:10Zmattwiremjw@mjwconsult.co.ukCollect payment processor usage statsWe can get some idea for all the payment processor extensions but for the core processors there is no info as to their usage. And with extensions you may still have multiple different processors (eg. omnipay is actually a set of quite a ...We can get some idea for all the payment processor extensions but for the core processors there is no info as to their usage. And with extensions you may still have multiple different processors (eg. omnipay is actually a set of quite a few different ones).https://lab.civicrm.org/infra/stats-collection/-/issues/3Define key trends to identify within stats2019-10-19T00:48:27Zjoshjosh@civicrm.orgDefine key trends to identify within statsThanks to @cividesk we are taking snapshots of our stats such that they could be displayed over time, i.e. showing trends within the data. This task is intended for those in the marketing group that are interested to flesh out key trends...Thanks to @cividesk we are taking snapshots of our stats such that they could be displayed over time, i.e. showing trends within the data. This task is intended for those in the marketing group that are interested to flesh out key trends to identify. Nicolas has offered to put a few of these together.https://lab.civicrm.org/infra/stats-collection/-/issues/2Collect contact info in-app2020-03-27T15:14:37ZJonGoldCollect contact info in-appOn install, let's add a couple of questions to the process, with sensible defaults.
A select box that asks who the installer is.
* I am installing this for use by my organization.
* I am a member of the CiviCRM Providers' Association
* O...On install, let's add a couple of questions to the process, with sensible defaults.
A select box that asks who the installer is.
* I am installing this for use by my organization.
* I am a member of the CiviCRM Providers' Association
* Other (e.g. I am a website builder hired by this org, just curious, etc.)
Checkboxes that submit additional data during pingbacks to:
* auto-subscribe user 1 to the CiviCRM newsletter;
* Ask if the installer is interested in being contacted by a CiviCRM community ambassador for help getting started/finding community resources.
Make it clear that these can be changed at any time.
The first question will give us partner/non-partner stats, and allow us to target messaging more effectively. The second question will identify folks interested in becoming attached to the community.
In addition to approving this concept generally, we need to float this past various parties to satisfy these concerns:
* Is this GDPR compliant? Does it raise any privacy issues generally?
* Does it violate the WordPress directory plugin policy, necessitating we exclude it from the WP "lite" version?
* Do partners have an issue with their clients being known to core team? Does answering that it's a partner install mean the other questions should change?https://lab.civicrm.org/infra/stats-collection/-/issues/1Collect data on the download screen2018-10-15T20:28:55ZJonGoldCollect data on the download screenWhen users go to download, we previously asked for money - which presumably was targeted at upgraders. However, the much larger group was evaluators, who won't respond well to a request for money. However, it's a great time to get thei...When users go to download, we previously asked for money - which presumably was targeted at upgraders. However, the much larger group was evaluators, who won't respond well to a request for money. However, it's a great time to get their contact info.
I propose the download screen optionally collects data, which a "No thanks, just start my download" option. See https://dev.mysql.com/downloads/file/?id=479839 for an example (though I am NOT proposing we create a login).
For usability purposes/maximizing conversions I think we minimize data collected. I propose:
* Name
* Organization
* Email
* Would you like to be contacted by a community ambassador to help you get started?