[sane-devel] SANE2 commitment

Gerard Klaver gerard at gkall.hobby.nl
Sun Dec 17 20:41:49 CET 2006


On Sun, 2006-12-17 at 19:37 +0100, Frank Zago wrote:
> Alessandro Zummo wrote:
> > On Sun, 17 Dec 2006 15:02:19 +0100
> > Jochen Eisinger <jochen at penguin-breeder.org> wrote:
> >
> >   
> >> Hi,
> >>
> >> Alessandro Zummo wrote:
> >>     
> >>>  I'd appreciate if everyone who is interested can reply
> >>>  with their own commitments for the 2007.. ehm.. sane2 :)
> >>>       
> >> I'm quite surprised to hear there is a sane2 standard - at least one
> >> that we can easily start to implement.
> >>
> >> I don't think it's a good idea to start hacking something before it's
> >> clear we have a standard that will support us for the next few years.
> >>     
> >
> >  you're right. my idea is to rally up some developers
> >  and then define the standard. only then we should start
> >  hacking.
> >
> >  however, defining the standard without the developers
> >  will not lead us to anything useful.
> >
> >  some people has committed the time necessary to
> >  port to sane2 the first bunch of drivers.
> >
> >  we are currently missing coders for
> >  - all of sanei/* (i'll take sanei_tcp)
> >  - the build system (configure, makefile et al) 
> >  - X11 frontends
> >
> >   
> 
> I believe the right approach is to fork the existing tree and start
> fixing and adding functionalities to it. That way you'll keep something
> that works all the time, saving many headaches.
> As or for the sane2 standard, it's only just a piece of paper right now.
> Coding should determine what will stay and what will go away, not the
> opposite (cathedral vs bazaar).
> 
> Frank.
> 
> 

One other step is to check which bugreports can be solved before such a
fork.

-- 
--------
m.vr.gr.
Gerard Klaver





More information about the sane-devel mailing list