Nepomuk

[Tony Sivori]

Lindsay Mathieson wrote:

> 
> A few months back I saw a post on a nepomuk  developers blog re the fact
> that:
> 
> - external interfaces were poorly or not documented and frequently
> changed
> 
> - return codes/exceptions were undocumented and frequently changed
> 
> - errors went largely unlogged and were ignored
> 
> - logging in general was almost non-existent
> 
> 
> I commented that this was a recipe for disaster - in the large corporate
> projects I worked on it was essential for core services to be well
> documented and *essential* for them to log every error, especially
> unexpected ones. It paid off in spades when you were trying to debug
> weird shit happening on the various remote and obscure setups we had to
> work with.
> 
> Sure you have to keep service specifications flexible, especially in
> development as new requirements/problem emerge, but you also have to be
> able to say  enough is enough and tie it down. And always always
> document and make it transparent.
> 
> My comment was deleted.

You might want to check out this Bug Tracker link "Annoyed by 'Nepomuk
Indexing Disabled' - Akonadi Agent message".

While it contains little useful info, it does well illustrate the
poor attitude of a hopefully tiny minority of Nepomuk / Akonadi hackers.

https://bugs.kde.org/show_bug.cgi?id=258171

-- 
Tony Sivori
Due to spam, I'm filtering all Google Groups posters.