Matomo Issue #12420 - Finish renaming Piwik to Matomo everywhere

@mattab opened this Issue on January 10th 2018 Member

As part of the renaming efforts we're updating all our websites, tools, core app, plugins, ie. everything!

Renaming checklist left to do:

[ ] make the build files matomo.zip and matomo.tar.gz, as well as the directory inside the builds should be called matomo
[x] plugin CustomPiwikJs to be renamed eg. CustomJsTracker --> see #13604
[ ] plugin AnonymousPiwikUsageMeasurement to be renamed
[ ] HTTP Tracking API endpoints: piwik.js and piwik.php
[ ] JavaScript tracking sdk with objects like Piwik and window.Piwik and methods like getPiwikUrl
[ ] Plugin developers, core platform uses namespace Piwik + some objects called "Piwik", an event Piwik.getJavascriptCode
[ ] cookie names eg piwik_auth
[ ] URL parameter like piwik_campaign to also support matomo_campaign
[x] HTTP API methods eg. ExampleAPI.getPiwikVersion -> 3.3.0
[x] DB prefix like piwik_ -> 3.3.0
[x] Remove --piwik-domain console parameter (see #13192) - Will be done with #15503
[x] After a successful auto-update, the screen shows Piwik is now Matomo and a big image. Be good to remove both. --> Will be done with #15504
[ ] Marketplace URL parameters like "piwik_version"
[ ] plugin.json parameters like require "piwik"
[ ] CSS classes etc
[ ] angular directives like piwik-foobar
[x] Remove Piwik font (already "renamed" to Matomo in #12489)
[ ] Tracker proxy: Add matomo.php with keeping BC + Update [faq])https://matomo.org/faq/how-to/faq_132/) https://github.com/matomo-org/tracker-proxy/issues/55
[ ] ... and more

In the case of Matomo core platform we want to keep things backward compatible for users including HTTP APIs users or users of the JavaScript SDKs.

Assigning to Matomo 4.0.0 but hopefully we can tackle a few of the list, and make progress on the others, during Matomo 3.x :rocket:

Finish renaming Piwik to Matomo everywhere #12420