Geyser Core
This specification is with regards to the planning and implementation of the Geyser project as a whole. It is intended as an introduction and will be split into seperate sections at a later stage.
Though there are many other notification frameworks out there, Geyser claims to be different, why wouldn't it. The Geyser project works around the idea of plugins; input, output and filters. You may like to think of this as a stream of data eminating from it's source, the input plugin, passing through filters, and ending up at the output plugin. It is using this system of configurations of plugins that Geyser should be an ultra generic platform for notification generation.
Blueprint information
- Status:
- Not started
- Approver:
- Geyser Devel
- Priority:
- Undefined
- Drafter:
- Geyser Devel
- Direction:
- Needs approval
- Assignee:
- Geyser Devel
- Definition:
- New
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Features to be included/
* Auto updating of plugins
* Multiple inputs mapping to multiple outputs
* Filters for data passing through Geyser, ie, notification contains X
* Full logging of all notification data
* Support for native and non-python plugins over dbus
* Support for TCP/IP connection inputs through dbus daemons
* Highly abstracted API for creating plugins to remove as much of the complex stuff from the user as possible
* Support for integration into standard desktop apps through core plugins, as well as integration with other notification frameworks
