[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Writing down design documents
From: |
Bas Wijnen |
Subject: |
Re: Writing down design documents |
Date: |
Fri, 14 Apr 2006 10:35:00 +0200 |
User-agent: |
Mutt/1.5.11+cvs20060126 |
On Fri, Apr 14, 2006 at 04:51:59AM +0200, Pierre THIERRY wrote:
> So why not write down some documentation about what we are discussing
> here, to make it easier for newcomers to grab the situation when they
> want? (and for the others to refresh their memory when they need)
Sounds good.
> Here are the main documents I'd like to see to find information quicker:
> - Design principles
What a design principle is, or what design principles we (plan to) use?
Probably both, right? :-)
> - Concepts (things like POSIX, capabilities, etc.)
> - Subsystems
What kind of subsystems do you mean? Can you give examples? Somehting like
device drivers, or the graphics system? Or?
> Could the main contributors of the discussions state if they agree or
> not on this idea?
Yes, I agree that it would be a good idea, and would like to help write these
things.
> so I'm willing to try to write at least stub pages and begin to fill them
> with what has been said on the list,
Sounds good. Where do you plan to put them? A wiki seems suitable for this.
Thanks,
Bas
--
I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see http://129.125.47.90/e-mail.html
signature.asc
Description: Digital signature