Future improvements

[javierhonduco]

Some ideas that @mvaello, @rmed, and I have been having:

• [x] Improve seed data. Add comments, speakers, and so on. And add quite a lot of them.
• [x] Update to Rails 5.1.X
• [ ] Update all gems. We have locked 3 gems or so which introduce breaking changes.
• [ ] Try to reduce our dependencies.
• [ ] Deploy as soon as possible
• [ ] Improve the test suite right now we are doing really basic testing of the controllers.)
• [ ] Start using a style guide.
• [ ] Get rid of the several n+1s that we have around.
• [ ] Clean up the models a bit.
• [ ] Improve README and basic documentation.
• [ ] Think whether to move off haml.
• [ ] Add visual diff-ing so we know if we have some important regression.
• [ ] Review the other opened issues
  • [ ] #23
  • [ ] #35
  • [ ] #36
• [ ] I think some of the emails are being sent synchronously. Could this be a problem in our case?
• [ ] Deploy to production and improve the deployment workflow.
• [ ] Improve observability in production with error and performance monitoring
• [ ] Compare to a brand shiny new Rails 5 app and see if we still have old stuff lying around

[rmed]

Seed updated in #63

[yagop]

Maybe its easier to use Milestones and spread the tasks by Issues

See https://guides.github.com/features/issues/

Kudos for the devs