Re: [Spca50x-devs] TODO list

[Miah G. <ma...@da...>]

On Thu, 18 Apr 2002, Leonardo Milano wrote:

> > Should we drop functionality from the driver in order to ensure
> > stability, or leave it as is? Any 'dropped' functionality can be
> > included in the development branch, so it's not lost.

> Absolutely, I think we should limit the functionality in the stable
> branch to a minimum set of essential features that we know the user
> can use without crashing the machine and with no problems.

That makes perfect sense. Better that a user comes to us asking whether
something is supported, rather than coming to us to report a bug.

> Just as an example, I often crash my box when testing xawtv
> That's something we cannot afford. 

Fair enough.

> As for the structure of the driver, I think the way to go is to mimic
> what drivers in the stable branch do. We don't want to rediscover the
> wheel, and we won't get Alan Cox to sit down a whole afternoon to
> check it out and fix it. Let's just be consistent with what people are
> doing currently.

Do you know how closely the driver currently mimics some of the stable
drivers? A brief rundown would be useful, if you have the time.

> > An overall description of the driver, and its structure would go a long
> > way to attracting new developers. It would also help iron out any possible
> > bottlenecks in the code.

> Absolutely, but I doubt someone will do it. But a well commented, well
> designed driver would help. Dimitri took a good step on that direction
> separating Headers for each cam, that kind of thing will definitely
> help.

I may have a go at code documentation, if I get a chance.

> Let's try to keep this thread as ON TOPIC as possible so that we
> can extract a TODO file easily afterwords ...

Apologies if I'm not on topic, I did try to be?

-- 
Miah Gregory