[sane-devel] [RFC] how to enable 1.1 features
Alessandro Zummo
azummo-lists at towertech.it
Thu Feb 28 23:54:57 UTC 2008
On Thu, 28 Feb 2008 18:40:03 -0500
"m. allan noah" <kitno455 at gmail.com> wrote:
> my original idea was to have the end user protect the frontend by not
> choosing settings it could not support. that would enable us to make
> no changes to frontends, no changes to old backends and get sane a
> much needed feature in a hurry. some folks thought that was playing
> fast and loose with the standard.
this is because we are speaking about sane 1.0 standard. you can't
have a standard that covers from 1.x to x.x :) we need an 1.1
standard.
> calling it sane 1.1, but leaving the soversion at 1 was a compromise
> to hopefully clue front-end authors in to the existence of these
> changes, while keeping the advantages of the small, fast solution.
> That was still not enough for some folks, as this is still an API
> change.
> With your repeated requests to make other API changes, and your
> willingness to write code, how about we bite this bullet and re-open
> the discussion about building a new, simpler sane2?
because I don't want to discuss, I want to write code. I very
much like the linux development model. discussion is based on code,
not the other way around. Write a little, discuss a little, repeat.
But they have Linus as the ultimate deus-ex-machina :)
But while in linux there's willing to evolve and change, here this
willingness is restricted to a few individuals.
An interesting read about that can be found in
http://kerneltrap.org/Linux/Kernel_Evolution
28 people contributed to the last two changelogs, but
only a few here are saying what they would like to do.
Even if their desire is to keep the thing as is, it is
very much important to say it.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
More information about the sane-devel
mailing list