tattletale

tattletale copied to clipboard

The ability to group things together for dashboard rollups would make consuming the metadata around check-in time easier.

mckern

This will make it possible to have an unauthenticated rollup endpoint for public jobs.

mckern

These things are like [tribbles](http://en.wikipedia.org/wiki/The_Trouble_With_Tribbles), and if left unchecked they will chew up your database like it was grain stores. - Maybe [acts_as_trashable](https://github.com/bdurand/acts_as_trashable)? - Or maybe use [Sidekiq](http://mperham.github.io/sidekiq/) to clean...

mckern

Look at integrating [Omniauth](https://github.com/intridea/omniauth) for pluggable authentication instead of the unrealistically simple "authentication" in use right now. That'd make it easier to plug multiple authentication backends into place.

mckern

Here's some ideas for the sort of things that should be output: - Check-in history for jobs - Maybe some sort of param for specifying how far back to go?...

mckern

You don't have any. How is that even _possible_?

mckern

What you've got now will never cut it. Try these on for size: - Setup & installation - Dependencies - Better usage examples

mckern