Hi list, Current status of project can be called frustrating. We have a serious lack of documentation and strange goals. To be honest there are no fully determined goals, current subjectives too abstract.
I'm offer the following way that will help to continue development: - I'm determine a goals, strong small cases for releases (it's a not general purpose system with GUI and other sugar :) - You all ask me everything that you didn't know about Jari OS architecture (I will reply with argumentation) ;) - I'm starting to write docs/one_big_book/blabla to fixate this all stuff. - new method of development (see below ...) Well, new method of development will able formalize tasks, and it looks better ;) When somebody (from the team (or some group)) has a new technical idea, some new method for i/o in system or for something other - this man write a whitepaper draft. This whitepaper *should* contain benefits, goals and concept architecture design. After implementing there are should be proof that this solution is better than existing. Programming tasks should be also exist for implementation - it will decide the "I don't know what to do" problem. Also, I want team to have a discussion (no, not "how to build" trees), but it might be possible if the architecture and system basics will be documented (I'm not sure, is it ?). Currently, I start works on book (it will be available soon in jari_os.git repository). I will describe all layers, concept, problems, and so on ... Anyway, I'm waiting for questions now - it will help I think. -- Alfeiks Kaänoken, Team Lead of the Jari OS R&D Team. http://jarios.org Free open-source microkernel-based multiservice RTOS _______________________________________________ Jarios-dev mailing list [email protected] http://lists.jarios.org/cgi-bin/mailman/listinfo/jarios-dev
