Archive:Hermes

Jump to: navigation, search
Icon-trash.png This article is being considered for deletion!
Reason:

openSUSE is not using Hermes anymore, development has stopped in 2013..

Please do not blank, merge, or move this article, or remove this notice. Refer to this article's discussion page and our deletion policy for more information.

Hermes User Notifications

Hermes is a free notification distribution system. You control it with powerful filters.
Hermes is the central notification hub of the openSUSE Project. It gives users control over the kind of notifications they wants to receive, in which way and when.

Even though Hermes has its roots in the openSUSE project, it is not bound to it and can be integrated in other environments seamlessly.

What is Hermes?

People using professional IT systems such as the openSUSE Buildservice often want to receive notifications about events that happen within the system while they are off line. Usually this is done by having the system to send email. This however has great drawbacks. First and foremost it takes the control, which messages are sent out, to the system. That is near to SPAM and shouldn't be.

Hermes is a solution for that with great advantages for users:

  • Users can pick themselves which notification they want to have.
  • Users can pick in which way they want to be notified, ie. E-Mail, Jabber or Twitter.
  • Messages can be digested. Instead of hundrets of similar message per day, that makes one message with all content collected.

Everything can be controlled through Hermes user- and admin web portals.

Hermes also comes with lots of advantages for developers and administrators as it brings simplicity to the overall system.

Dive into the details below.

Variety of delivering systems

Todays users expect information to come up in different ways like being presented on a web page, coming through news systems or as jabber messages or as XML based RSS feeds.

Aggregation

Moreover users would probably love if messages of the same type get aggregated to a digest message that is posted daily instead of one by one. For example, for failed package builds it would be sufficient to get one message per day that contains a list of all failed packages of the day (possibly without duplicates) instead of tons of messages with similar content.

Choice

User should have the choice how, which and in which form messages get delivered. There should be a interface where one can maintain the settings which kinds of messages get delivered how.

For example one might prefer to get PDB- and package build fail messages as nightly digest mail, but wants to receive buildservice messages directly via jabber to the mobile phone.


Start Hacking

Hermes is an open source project! It is not bound to openSUSE. If you are interested about Hermes' functionality on your site, let me know.

If you want to contribute, you're more than welcome. Please read the hacking information page as a starting point.

More Information