Re: [linuxdc-dev] Updates to UDCTM and the TODO list

[M. R. B. <ma...@uw...>]

On Sun, 18 Feb 2001, Karl Trygve Kalleberg wrote:

[...]
> 
> It doesn't look sexy. Sorry about that.
> 
> Its purpose is to be able to point to it and say 'Foo is responsible for that part, go talk to him about
> that'. The basis for the list is what you guys have told me before. Both Rene and Marcus Brown seem to be
> a bit busy as of late, so they might be willing to let other people take over their claimed areas.
> 

Heh, not busy any longer, promise :).

> I hereby proclaim myself the CVS and TODO-list guy until anybody fiercely objects. That means that you if
> you want to do anything not mentioned on the TODO-list and you're uncertain anybody else is working on it,
> talk to me. 
> 

I had a "roadmap" going, but like mostly everything else so far, time has
stolen that one :).  I have some ideas as well as areas that need to be
worked on, some things include building tools, and creating RAMDISK
images, etc.

> Also, send any and patches and requests for syncing the CVS with whatever to me. It seems that every developer
> for some reason maintains his own tree completely separately from our own CVS. 
>

Yeah, we need guidelines on submission, this is a great start.  I'm
working on a script to merge the current kernel (reflected in LinuxSH's
tree) with ours, hopefully to be setup on a daily basis.  The thing with
that is to make sure we don't step on LinuxSH's code (mostly everything in
the arch/sh tree, with a few misc. drivers).

Anyone who is on this list is welcome to submit any ideas, code, rants, to
the list as we try to get the ball rolling.  In particular any thoughts on
how to implement specifc subsystem drivers, e.g. GD-ROM, FB, AICA audio,
input, ethernet - whatever, please post for further discussion.  Hopefully
everyone didn't die off in the two months we (part. I) was in a coma :P.

M. R.