You might end up using several hours on a review, but the end result
could be a superb library that will save you weeks of work.
Notes for reviewers
When writing your review, you may wish to consider the following
* What is your evaluation of the design?
* What is your evaluation of the implementation?
* What is your evaluation of the documentation?
* What is your evaluation of the potential usefulness
of the library?
* Did you try to use the library? With what compiler?
Did you have any problems?
* How much effort did you put into your evaluation?
A glance? A quick reading? In-depth study?
* Are you knowledgeable about the problem domain?
And finally, every review should answer this question:
* Do you think the library should be accepted as a Boost library?
Be sure to say this explicitly so that your other comments
don't obscure your overall opinion.
In particular, consider if you can answer the following questions:
- was the library suitable for your daily xml-tasks? If not, what was
- was the library's performance good enough? If not, can you suggest
- was the library's design flexible enough? If not, how would you
suggest it should be redesigned to broaden its scope of use?