Add post on libical 0.1.0

1 files changed, 49 insertions, 0 deletions

diff --git a/content/blog/2019-12-13-libical-0-1-0.md b/content/blog/2019-12-13-libical-0-1-0.md
new file mode 100644
index 0000000..7c6657a
--- /dev/null
+++ b/content/blog/2019-12-13-libical-0-1-0.md
@@ -0,0 +1,49 @@
+---
+title: "libical v0.1.0"
+date: "2019-12-13T21:12:40"
+tags: [ "linux", "open source", "programming", "rust", "software", "tools", "ical", "vobject"]
+---
+
+I'm happy to announce the availability of "libical" version 0.1.0.
+
+[libical](https://github.com/libical/libical) is a library for parsing and
+generating icalendar data objects (.ical files). It is used by the GNOME and the
+KDE communities in their codebases, for example in the codebase of the GNOME
+calendar implementation, the akonadi framework and other known software.
+
+With the availability of the libical crate, which relies on the code from the
+[libical-sys](https://crates.io/crates/libical-sys) crate, the rust ecosystem
+now has a high-level binding library for the icalendar data format.
+
+
+The library was extracted from the
+[khaleesi](https://github.com/Valodim/khaleesi) project, a commandline calendar
+implementation that is inspired by the famous
+[khal](https://github.com/pimutils/khal) project.
+
+
+# Current status and way forward
+
+This release marks the first stepping-stone. The code was extracted, but not
+refactored or cleaned up. The tests run, but the code has not been run in a
+real-world application (by me, fwiw).
+
+You are all welcome to contribute on this codebase to refactor it, clean it up
+and help me making this the go-to crate for handing icalendar data in Rust.
+
+* imag-pim.org repo: https://git.imag-pim.org/libical/
+* Github: https://github.com/matthiasbeyer/libical/
+* codeberg: https://codeberg.org/matthiasbeyer/libical
+
+
+# Credit
+
+All credit goes to the original authors of the code, [Vincent
+Breitmoser](https://github.com/Valodim) and
+[puzzlewolf](https://github.com/sonea-pm8)
+(not sure whether they want to be introduced by their real name).
+
+I just extracted the code from the original codebase, cleaned up the repository
+a bit and set up the travis jobs, but I am planning to refactor this code to get
+the best usability out of it.
+