@mattab opened this issue on October 28th 2014

The goal of this issue is to create a new automated test that runs in each Plugin's CI build, that will help a plugin developer implement best practises in his plugin.

Ideas of best practises to check for: - The repository should have some tests, - The README should have the section Description, Changelog, Support, - The plugin should have a screenshot (so it looks good on marketplace), - The plugin.json license, authors, should be consistent for Piwik and Piwik PRO plugins, - Notifications to Slack should be enabled, - Other ideas?

Reference: distribute your plugin on the Marketplace.

@mnapoli commented on October 28th 2014

Notifications to Slack should be enabled

Notifications about builds? I'm not sure this is a good idea, even with piwik and ui-tests the amount of notifications makes it near useless.

@mattab commented on October 28th 2014

Notifications about builds?

I meant git push notifications as it's quite nice to see all commits in the channel. You're right that travis build notifications is too noisy in slack.

@mnapoli commented on October 28th 2014

Oh ok even more noisy, I'll be out of this channel ;)

@mattab commented on January 2nd 2017

Not needed anymore

This issue was closed on January 2nd 2017
Powered by GitHub Issue Mirror