Is Jari OS progress stalled?

Generally not. But I didn't made the planned things yet.
Well, I will try to explain why.
First reason - I spent about one year with development/research/testing and investigation about IDL design that might be used system-wide. It was a wrong way, however Jari OS has IDL now.
Second reason - Developers lost an interest, I've tried to find new mad ones, but success was not follow me.
Third reason - I spent a lot of time with other activity, such as non-IT hobbies, contract-job in Nokia and other things.
However, it was a break in Jari OS development, I was need to take a big vacation with my position in Jari OS.
Now it's time to have a hard work on project, for the past two years a lot of good ideas accumulated and it's time to implement many of them.
Also, there are few applications found which can be powered by the project.
Well, see you later.

Decomposing big project, separating is better

You can find more information on the link in the post title.
Overally, following to the general idea - "separate all works and job to smaller ones" I decide to run microkernel separatly - like independed project.
This intended to be more effective, for example - currently I have EZA layer working for 60% (not so stable) and this was made after reorganization of the microkernel structure - and this just for less then 10 hours of normal works on the problem.
MString (MuiString) - is a name for Jari microkernel - and it's a new tag on this blog ;)
Now I'm thinking on diferent than C/Cext language for server space - it's a big flame, but I'm thinking that fully functional languages or partly functional is better than typical imperativies ones. Anyway, microkernel must be implemented on plain C - it's more comfortable language.