Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add metric to help assess awareness of package ecosystem #90
Description of the Change
We consider Atom's extensibility (or "hackability!"
Equipped with this information, we'll be able to assess the effectiveness of our efforts to increase the awareness and approachability of the package ecosystem. For example, does a particular tweak to the welcome guide increase or decrease the percentage of users that have installed a package? Similarly, if we were to add an "Install" button on each package page on https://atom.io, does that result in an increase in the percentage of users that have installed a package?
Implementation-wise, this pull request sends an event that reports the quantity of optional (i.e., non-bundled) packages that get activated at Atom startup.
Instead of sending the count of optional packages that are activated, it would provide richer information if we sent the names of the optional packages that are activated. However, I don't think it will be practical to take that approach:
I updated the pull request body to describe the verification process, and the screenshot below shows the metrics resulting from my testing.
You can view metrics by various dimensions, and this particular view shows the average number of optional packages activated by Atom version. In a VM running an Atom 1.29 dev build, you can see that I have no optional packages installed. And on my main dev machine running an Atom 1.30 dev build, you can see that I have 38 optional packages installed.