Re: Writing down design documents

[Gustav van der Merwe]

On Fri, 2006-04-14 at 10:35 +0200, Bas Wijnen wrote:
> 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
> 
> _______________________________________________
> L4-hurd mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/l4-hurd

Another me too message, I agree that this is an excellent idea. People
should have a place they can read about past discussion and resolutions
as the other documentation is not always up to date.
My only quibble is, who is going to take it upon themselves to maintain
this? This leads to thinking, well why not everyone?
So a Wiki I think it should be.

-- 
Gustav van der Merwe <address@hidden>

signature.asc
Description: This is a digitally signed message part