- He has fixed many bugs in SBCL. There's no single summary theme, but
- he's fixed about a dozen different bugs in LOOP alone, and it appears
- that a lot of his fixes there and elsewhere reflect systematic
- public-spiritedness, fixing bugs as they show up in sbcl-devel or as
- archived in the BUGS file.
+ He has fixed many, many bugs. There's no single summary theme, but
+ he's fixed about a dozen different bugs in LOOP alone, and more
+ in the compiler itself. It appears that a lot of his fixes there
+ and elsewhere reflect systematic public-spiritedness, fixing bugs
+ as they show up in sbcl-devel or as archived in the BUGS file.
+
+Paul Dietz
+ He is in the process of writing a comprehensive test suite for the
+ requirements of the ANSI Common Lisp standard. Already, at the
+ halfway stage, it has caught many tens of bugs in SBCL, and provided
+ simple test cases for them.
+
+Miles Egan
+ He creates binary packages of SBCL releases for Red Hat and other
+ (which?) platforms
+
+Nathan Froyd:
+ He has fixed various bugs, and also done a lot of internal
+ cleanup, not visible at the user level but important for
+ maintenance. (E.g. converting the PCL code to use LOOP instead
+ of the old weird pre-ANSI ITERATE macro so that the code can be
+ read without being an expert in ancient languages and so that we
+ can delete a thousand lines of implement-ITERATE macrology from
+ the codebase.)
+
+Matthias Hoelzl:
+ He reported and fixed COMPILE's misbehavior on macros.
+
+Espen S Johnsen:
+ He provided an ANSI-compliant version of CHANGE-CLASS for PCL.
+
+Frederik Kuivinen:
+ He showed how to implement the DEBUG-RETURN functionality.
+
+Arthur Lemmens:
+ He found and fixed a number of SBCL bugs while partially porting
+ SBCL to bootstrap under Lispworks for Windows