| Summary: | sysadmin documentation for nepomuk | ||
|---|---|---|---|
| Product: | [Websites] docs.kde.org | Reporter: | Michal Svoboda <kde> |
| Component: | general | Assignee: | Documentation Editorial Team <kde-doc-english> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | annma, luigi.toscano |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Michal Svoboda
2009-09-13 19:06:02 UTC
Where do you want that doc please? (In reply to comment #1) > Where do you want that doc please? I'd prefer a googlable location, plus a link at http://nepomuk.kde.org/node/2 (ie. nepomuk->documentation) Are we moving somewhere with this report? C'mon. You introduce a new load of functionality, with tons of propaganda, but not a word of documentation? Bump. Kick. Please be patient and considerate of the lack of documentation writer and developer time. There is some documentation at http://nepomuk.kde.org/discover/developer which does not fully address your specific questions, but provides pointers that will help you infer the answers, or where you would need to look to find the answers. Also, you might be able to infer the answers to your questions given the files stored by nepomuk-kde are in .kde/share/apps/nepomuk/repository [This isn't to suggest that more documentation wouldn't be useful, but instead to help you in the interim. Perhaps you could even write the documentation?] (In reply to comment #5) > Please be patient and considerate of the lack of documentation writer and > developer time. Time we have all equally - 24 hours per day, it's up to us what we do. The point being, you can devote time to writing the doc instead of whatever else you guys are doing on the project. Needless to say that writing a documentation usually has a purifying effect on the other parts (development, testing). > There is some documentation at http://nepomuk.kde.org/discover/developer which > does not fully address your specific questions, but provides pointers that will > help you infer the answers, or where you would need to look to find the > answers. I read that page even before posting this ticket, obviously I was unable to make sense of it. > Also, you might be able to infer the answers to your questions given the files > stored by nepomuk-kde are in .kde/share/apps/nepomuk/repository OK, at least something, that answers some of my questions, but I'm afraid in not a very useful way, $ less triples-cspo.dat "triples-cspo.dat" may be a binary file. See it anyway? ^@^@^@^A^@^@^H^@^@^@^@^Q^@^@^X^D^@^@^@^@^@^@^@^@^@... It means that the answers could be about the following, 1) all the meta data (incl. tags, stars...) are in the .kde dir, which is usually the first one to go ("problems? delete .kde") 2) seems they live together 3) probably not - backend dependent 4) only God knows - is the database open at all times? supports online backup? recovery? 5) probably none 6) probably not 7) oh please :) 8) no Correct? > [This isn't to suggest that more documentation wouldn't be useful, but instead > to help you in the interim. Perhaps you could even write the documentation?] I have no incentive to do so. I hoped to wet my taste by reading the doc. But right now for me Nepomuk & co is totally alien, messy and possibly broken technology, probably not the outcome you'd want to hear. Unfortunately (and sorry for the lack of answers) time passed, and Nepomuk was replaced. |