Hi Gus, Everyone is invited of course, but really after those willing to spend some time on it to make it happen, and just want it clear to leave company biases and agendas at the door. I'd like to make everything public but not sure it would be a good idea to force any derivative work to be public. For instance a company that spends a lot of time generating code/hardware to control motors may not wish to share with the general public the details for commercial reasons, (though it would be nice). But if we can offer them and everyone else a standard and reasons, for using this interface, that would be at least a move in the right direction. Designs done by the working group members on this would be public, though not posted till something reasonable is formed to avoid people going off in different directions. And would like to keep original conversations private so people are free to suggest anything and not have to worry about repercussions to start with and things can move faster.. As soon as their's a straw-man it would be published so the rough edges could be knocked off by everyone.
Cheers, Dave David Lissiuk Sr. Computer Scientist Springbok DIgitronics ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
