Input status: June 19th, 2015

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

What is it?

The purpose of Input is to collect actionable feedback from our user base across each channel of our software development process. The application collects feedback and offers a set of analysis methods for looking at the resulting data.

Project site.

This is a status post about Input.

Development

High-level summary:

  • lots of library updates and changes to make way for Django 1.8

  • switch from nose to pytest

  • new suggests and redirector frameworks

  • upgraded from Elasticsearch 0.90.10 to 1.2.4

  • added editorconfig and pre-commit for easier development

That doesn't sound like a lot, but it was.

I'll write a more comprehensive blog post about the new suggests and redirector frameworks soon.

Thank you to contributors!:

  • L Guruprasad: 6

  • Michael Kelly: 1

  • Ricky Rosario: 17

Skipping the long list of commits and bugs. If you're interested, you can check the commit logs.

Current head: ac406e4

Rough schedule going forward

  1. Finish up upgrade to Django 1.8.

  2. Implement trigger-keyword provider.

  3. Redo the Elasticsearch infrastructure in Fjord.

That's it for this update!

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.