# What's coming up in imag (24)

This is the 24th iteration on what happened in the last four weeks in the imag project, the text based personal information management suite for the commandline.

imag is a personal information management suite for the commandline. Its target audience are commandline- and power-users. It does not reimplement personal information management (PIM) aspects, but re-uses existing tools and standards to be an addition to an existing workflow, so one does not have to learn a new tool before beeing productive again. Some simple PIM aspects are implemented as imag modules, though. It gives the user the power to connect data from different existing tools and add meta-information to these connections, so one can do data-mining on PIM data.

# What happened?

In the last four weeks, not that much happened. Mainly, because I was on vacation. Semester ended on Feb 21st, so from there on I did exactly one thing: Enjoy my free time.

Nevertheless, we got some things done in the imag codebase:

• #801 merged the initial support for annotations.
• #897 merged a new feature which gives us the possibility to build imag with the early-panic flag, which causes the store to panic on a failure rather than to throw errors. This is mainly for debugging, not for production use.
• #900 merged improvements for the libimagstore documentation.
• #901 merged some notes on long-term todos which would perish in the github issue tracker.
• #902 merged some improvements on the Ruby API.
• #903 improved the libimagrt documentation.
• #907 updated clap.

Four PRs are not in this list because they are too trivial.

What about Ruby? Well, because of the little progress, nothing happened in regards of the Ruby bindings. But we get there, I promise.

# What’s coming?

I don’t know yet. My 2nd semester for the masters course just began and I really don’t know what the workload will be. So… this is all in all a rather sad update, I guess. Progress slowed down a lot, I don’t know what will be there in the next four weeks…

We’ll see…