Re: [Sbcl-devel] Summer Of Code 2013 - Vectorisation

[Paul K. <pv...@pv...>]

Tucker DiNapoli wrote:
> Thanks for the answers, I think than working on the sequence
> operations would be interesting and of a reasonable challenge. I think
> what would be most helpful in writing a proposal would be getting a
> better idea of the sbcl code base and the development process. I think
> the best way of doing this is probably to work on some small bit of
> code or write some documentation for sbcl. What would be a good place
> to get started with this, I've looked at some bugs on launchpad and
> some of them seem doable by me (writing documentation if nothing else)
> but I'm not sure how to go about proposing a fix to something or
> submitting documentation for review. How exactly would I go about
> getting involved, or is there some documentation out there on how to
> get started with sbcl development that I could look into.

SBCL has been using git for quite a while now. If you're not familiar 
with it, I believe there's now a plethora of tutorials. Someone else may 
be able to suggest a good one.

The official SBCL repository is somewhere on sourceforge; it's probably 
easiest to fork https://github.com/sbcl/sbcl on github. Not only will 
you avoid the boatload of imminent migration issues, but you'll also be 
able to easily publish a complete tree, which I find easier than sending 
a long sequence of patches.

You'll find a file named HACKING in the root of the source tree. It's 
pretty complete regarding how to submit patches. As for the 
preliminaries, I think the best approach is to get yourself an account 
on launchpad, and comment on tickets for which you'd like more 
information. Once you've started working on a fix, you can assign the 
bug to yourself, and then send patches via launchpad (or to the mailing 
list).

Paul Khuong