In an attempt to try to increase the usage of metriks and make it easier to integrate, @josephruscio has suggested that the reporters be split into separate gems (or maybe their own gems).

This would mean the core metriks gem would just contain:

• the metric building blocks (Timer, Meter, etc)
• the registry
• a reporter base class? (if we ever have such a thing)

Reporters

We would need to decide if it made sense to have a single metriks-reporter gem that contains all of the reporters, or if it would make sense to have separate gems for each reporter. The benefit of separate gems is the reduction in dependencies that would be required, which seems like a nice gain.

Naming and upgrading

My first thought is to call the core gem metriks and have the reporters in their own gems. The downside of this is that anyone who is upgrading metriks will have their code break, as it will no longer contain any of the reporters. I'm not sure what the best way to solve this is a smooth upgrade path, so I'm open to suggestions here.

CC: @lmarburger, @josephruscio, @nextmat