Thanks, it still sounds a bit confusing, but is clearer than the previous warning.
Perhaps that section should be retitled to something like "Preventing the Akonadi subsystem from autostarting." What do you think?
I wanted to include it because I came across a lot of people who didn't want it even autostarting on their systems. They didn't use any of the akonadi-based applications and felt that it was using up resources for no reason. Ideally, I'd want such users to find the answer on userbase (either directly or through google searches).
Hmm - the problem is that it only prevents it from autostarting at login. The next problem is that there is no clear indication, as far as I can tell, which widgets will call it. Not being able to use the clock widget will actually turn out to be really important for many people. While I like to be able to help people get what they want, I'm also aware that there may be unforeseen problems. Do you use IRC? It might help to get talking to someone on the #plasma channel to see if there is any way of knowing which widgets might be a problem. There will always be a need to end with "and maybe others..." but if we could give some indication I would feel happier. The last thing we want is to throw people out of the frying pan into the fire.
Perhaps it is a bit confusing to have two boxes saying basically the same thing? Would it be better to remove the first box, promote the second box to a Remember box (with the red border for emphasis), and perhaps replace the its first sentence with the stronger worded first sectence of the first box? It would look line this:
This way, we would first have the recipe for disabling Akonadi, then the warning that running any Akonadi-enabled app will start Akonadi.
My original intention was to have a complete list of all applications and widgets that depend on akonadi. As you might have noticed, the application list is somewhat oddly formatted (I copied the markup straight from one of the application lists here) and incomplete (I can think of knode — which I don't use — and other applications that might be using akonadi already). I planned on expanding it and the translate tags got to it before me (story for another day) and now, the markup's pretty much unreadable and I decided to come back to it later.
With a complete list of applications and official widgets that use akonadi on this page, we could then leave the warning in its current state...
I am on irc (same name) on my desktop and usually have konversation running in my systray. I can be found on #kde when I'm online. It might be a better thing to discuss over a mailing list. What's the proper mailing list for discussing userbase-related issues? Would it be kde-www or kde-doc-english or some other?
Just looked again at the page layout, and actually I quite like it. I think it clearly shows the application name together with how it uses Akonadi, which makes it very clear, in my opinion. I don't know how to get a full list of apps using Akonadi, and even more important, I don't know how to maintain it - is there some resource where we can find this info?
Don't worry about the markup issue - we can help with that if needed. I see that it is using the recently added template to get the clickable links and I think the result is good.
You will usually find me, Claus_chr and neverendingo on #kde-www - and pipesmoker, though not around quite as much, also is able to help. That's probably better than using the mailing list, although the list kde-www would also find us,