Improved API for 2.x Release

http://stackoverflow.com/questions/15146523/how-to-design-an-easily-extensible-api-with-the-simplicity-of-enums/15147504

Have been curious the best way to extend the API for many months to make it usable AND extensible. Some excellent replies on that thread which would allow the continued use of the Enums (very user friendly) but allow extensibility through simple interfaces (great for devs).

[jtrunick]

I really need this. I'd like to be able to process some Video information (encoding/mime type, audio information).

Is anyone working on this? If I commit code will it get picked up?

@jtrunick I think to unblock you the most effective thing would be to fork the repo and do whatever work you needed to happen - I will review and pull incremental requests, but if your desire is to significantly change the structure of the project and submit it back -- I would recommend just keeping that as a fork so you don't need to worry about merging any 1.x with 2.x concerns.

I am not actively maintaining this (as much as I might want) right now to the level you would need me to -- or at least the level with which I am extracting from the urgency of your comment.