Thanks! Yep, you're right about format changes -- that's why I'm thinking hard how to make it as generic as possible and make error handling defensive enough, so it doesn't fail at the slightest opportunity.
Not really planning for emacs package:
- I don't feel very efficient coding in Elisp
- lots of infrastructure required (e.g. scripts for fetching data) is not worth rewriting in Elisp. Actually most of it is quite Emacs-agnosic and it would be a trivial task for Orger to output Markdown/HTML instead of Org-mode if one wants.
- it's a bit more accessible for other people when it's written in Python. I probably wouldn't be wrong if I say that people who are comfortable messing with Emacs are a strict subset of people that can run few Python scripts in cron :)
That said, if you think there are some benefits in having it tighter integrated with Emacs, I'd be really interested to hear!