I guess the best thing to do is to actually maintain QvLib outside of SGI.
It would be gesat if we could have a consorted effort as you mention.
I propose for that matter the following method:
A company/ person that has found bugs in QvLib posts these bugs to the VRML
mailing list for a week, together with failing cases that show the bug and
proposed bug fixes.
During that week, people who are interested in that topic could make sure
that the bugs are definitely there. In case there is any misunderstanding
about some bug, that person/company who has doubts about the bug, clears it
with the bug reporter. At the end of the week, the company/person that
reported the bugs and the fixes, updates QvLib and publishes it. The VAG
could update the link to the newest code for QvLib.
Older QvLib's would be kept and accessible for security purposes
The important thing about the "period of grace" that QvLib gets is to make
sure that the changes would be platform-independent or would work for all
platforms tmat QvLib supports.
Do people feel at ease with that solution?
Omar has volunteered a couple of hours a week for QvLib work. Would people
feel ok if he becomes the QvLib "moderator"? -and again, Omar, would that
interest you? Any thoughts by VAG members?
Sincerely
-- Richard Rabbat, Computer and Communications Engineer Center for Educational Computing Initiatives Massachusetts Institute of TechnologyEmail:
[email protected], [email protected] mail : 1 Amherst Street E40-370, Cambridge, MA 02139 url :http://abelard.mit.edu/staff/Ricky.html phone: 1-617-252-1838 fax : 1-617-253-8632