Projects/Nepomuk: Difference between revisions
(Created page with '{{Template:I18n/Language Navigation Bar|Projects/Nepomuk}} Image:Nepomuk_logo.png == About Nepomuk == This page is dedicated to Nepomuk development ideas, progress, experi...') |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Image:Nepomuk_logo_big.png|center|300px]] | |||
[[Image: | |||
== About Nepomuk == | == About Nepomuk == | ||
| Line 39: | Line 37: | ||
It still misses an implementation of the transaction support in Soprano backends (Sesame2 and Virtuoso) and in the client/server architecture. | It still misses an implementation of the transaction support in Soprano backends (Sesame2 and Virtuoso) and in the client/server architecture. | ||
== Ideas == | |||
There are many ideas on how to improve the Nepomuk system or on how to use it. This is the place to list them all. | |||
Feel free to add your own ideas. Please leave your name in case someone wants to contact you for details or a discussion of the idea. | |||
=== FIXME: add ideas === | |||
Revision as of 16:13, 18 May 2009
About Nepomuk
This page is dedicated to Nepomuk development ideas, progress, experiments, and is a general starting point for new developers.
For general information about the Nepomuk project see the dedicated Nepomuk homepage.
Developer Coordination
The Nepomuk project is maintained by Sebastian Trueg of Mandriva.
Documentation
The following links provide good reads for getting used to the Nepomuk system and its APIs.
ToDo
Nepomuk is a rather young project with a notorious shortage in developers. There are many tasks and subprojects to get ones hands dirty on. Unlike other projects like Plasma, however, developing for Nepomuk is not easy. One has to read up on a lot of things and fight some day-to-day annoyances. But: helping with the development will improve the situation in any case.
If you are interested in working on a task in this list, please contact Sebastian Trueg.
Low level Nepomuk Development Tasks
The low-level development tasks are those that are not directly reflected in the GUI or even in the API used by most developers. However, they are important in terms of performance, scalability, and compatibility.
Soprano Transaction Support
Soprano is the RDF database framework used in Nepomuk. Currently Soprano does not support transactions, i.e. sets of commands that can be rolled back. An experimental development branch exists which already contains new API for transaction support (while keeping BC).
It still misses an implementation of the transaction support in Soprano backends (Sesame2 and Virtuoso) and in the client/server architecture.
Ideas
There are many ideas on how to improve the Nepomuk system or on how to use it. This is the place to list them all.
Feel free to add your own ideas. Please leave your name in case someone wants to contact you for details or a discussion of the idea.