Hi everybody,
> I also think we should setup a more or less small
> group of developers who are willing to help Oliver
> to finish the sane2 standard. We might should setup
> a list of stuff that should also go into this new
> standard - this list should be more or less a whishlist,
> which means that some points may find their way into
> the standard, some not.
> Let's keep this list open for lets say 4 weeks.
> During this time the team around Oliver should
> be found and they could start with their work.
reading this sane2 thread and seeing that some people have some quite
different views of how to proceed regarding openness of the discussion,
i wanted to suggest to use a WIKI page for holding some kind of wishlist as
Gerhard suggested, and another page for editing the document defining the
standard. This last one could be read only for everybody except for a
few 'editors'.
In this way even if the 'core' of the technical discussion and commits goes
among just a few people, everybody can 'monitor' the results and speak out
if they come with a brilliant or revolutionary idea ;-)
It is not necessary to have a finished ('written on stone') standard to
start coding, but it is also not wise to start coding (call it fork sane-1
or start from scratch, doesn't matter) without having a general idea of
how the API should look like...
My 2 cents...
Best wishes, Ariel
