Paid support
ABCL is being developed as open source. Each of the contributers chooses his or her own priorities based on criteria like complexity and time available. Many changes implemented over the past years were implemented in evening hours, limiting the size and type of issue that can be addressed.
Your priorities, dear User, may not necessarily coincide with the priorities of the developers. To make sure your needs will be addressed too, there is the option of paid support, usually in the form of a consulting contract. You may want to use this option for example in case the 'regular' route (submission of a bug report or enhancement request) isn't being addressed as quickly as you like.
If you decide you want to use this option, or have other needs related to ABCL, please contact one of the following individuals:
- ehuelsmann 'at' common-lisp 'dot' net
- evenson.not.org 'at' gmail 'dot' com
- ale2014.zamora 'at' gmail 'dot' com
Potential projects / tasks that might be possible with paid support:
- Finalizing Gray stream support. Recent work has improved things considerably.
- Faster startup/load times via use of memory mapped fasls
- Compiler improvement to target more efficient bytecode version, for new class verifier and/or for dynamic method site utilization for CLOS.
- Implementation of stepper for compiled code; improvements for interpreted version.
Interested developers are welcome to have their names added to this list, but at this point in time no other developers are known to want to provide this type of support.