On Tue, 8 Dec 2009 23:21:35 +0200 Bernt Kamark <[email protected]> wrote:
> hi hi! > > 2009/12/8 Alf Kaanoken <[email protected]> > > > 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. > > > what the hell are you mean ? :) ihave never seen any desc. of goals. sorry, I'm wrong - all the goals in my head and on the main page partially ("Target: Industrial control units, Network routers, OS for research and develop different concepts in OS design, Terminals, ...") > > > > > 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 :) > > > is it more detailed roadmap ? Tihs is a roadmap and some features > > > - You all ask me everything that you didn't know about Jari OS > > architecture (I will reply with argumentation) ;) > > > ? If you have a question about service A and thus - why A connects to B throught C - I will answer. > > > - 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. > > > this description is contrary to your above description "I'm determine a > goals, strong small cases for releases ..." > if ' assume that you describe everything, then add something new is not > necessary. You don't understand me right, I will describe basics (and this can be updated by team), but here I mean the following situation: you has an idea to implement and want to include it to the base system (or exchange the existing implementation) - for this you should describe concept, for other - not. It will helps with documentation - I'm not sure that it's a good idea to write architecture design paper after implementation/debugging/... > describe it above > > > 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 > > ?). > > > u're rght. it's very difficult to discuss the furniture for the "dark room" > i spent >10 hours to understand this "room" i'm not sure people are willing > to spend a log of time too. Use lighter to explore dark room (as you made) ! ;) Well, what kind of documentation can help to make a sense with system? > > > > > 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 ... > > > good agr. > > > > > Anyway, I'm waiting for questions now - it will help I think. > > > ... u don't know about transistor anything what are u will ask? > u will ask: what is it for? how it works? etc > but u shall not ask about selected metal for semiconductor or about housing > material features. It's not correct comparison. > the same here > people know a class of system dealing with, but they have no idea how it > works I think that developer can ask about concrete subsystem while working on it, is it ? > > > > > -- > > 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 > > > -- 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
