+* sysfs set api in libudev is not const
+
+* Find a solution for SMACK capabilities stuff:
+ http://lists.freedesktop.org/archives/systemd-devel/2014-December/026188.html
+
+* port libmount hookup to use API's own inotify interface, as soon as that is table in libmount
+
+* bash completion for busctl, to make it truly useful
+
+* journald: broken file systems are real (btrfs), we need to handle
+ SIGBUS in some way if we cannot write or read from the disk.
+ https://bugzilla.redhat.com/show_bug.cgi?id=1151848
+
+* "systemctl preset-all" should probably order the unit files it
+ operates on lexicographically before starting to work, in order to
+ ensure deterministic behaviour if two unit files conflict (like DMs
+ do, for example)
+
+* resolved should optionally register additional per-interface LLMNR
+ names, so that for the container case we can establish the same name
+ (maybe "host") for referencing the server, everywhere.
+
+* systemd-journal-upload (or a new, related tool): allow pushing out
+ journal messages onto the network in BSD syslog protocol,
+ continously. Default to some link-local IP mcast group, to make this
+ useful as a one-stop debugging tool.
+
+* synchronize console access with BSD locks:
+ http://lists.freedesktop.org/archives/systemd-devel/2014-October/024582.html
+
+* as soon as we have kdbus, and sender timestamps, revisit coalescing multiple parallel daemon reloads:
+ http://lists.freedesktop.org/archives/systemd-devel/2014-December/025862.html
+
+* set $REMOTE_IP (or $REMOTE_ADDR/$REMOTE_PORT) environment variable when doing per-connection socket activation. use format introduced by xinetd or CGI for this
+
+* the install state probably shouldn't get confused by generated units, think dbus1/kdbus compat!