This page lists Racket projects which are feasible for people who don't have a lot of experience with the Racket code base. They're mostly small, self contained, and would be extremely useful. Some involve writing a new library that would be useful to lots of other people, and some help fix or clean up some aspect of the existing Racket code base.
The best place to ask for help with any of these is on the users mailing list.
These are intended to be a collection of fun topics to explore, intended as exercises or mini-projects, but also interesting in their own right. If you implement one, then leave a link: different solutions can lead to comparisons of style and constructive suggestions. Finally, add more ideas ...
These are self-contained projects. Just create a new github repository, and start hacking. When you have something that works, release it on the package catalog. To get started with packages, take a look at its documentation.
demo.racket-lang.orgthat show cases programs and snippets written in Racket. There's a start of explanations of the home page snippets here: https://github.com/samth/racket-examples
These are improvements to the Racket source. Fork the GitHub repository and then submit a pull request.
class100to the current class system
assqand friends to find
memberand friends to find
srfi/1, replace them with
define-loggerform to change them to use their own logger. That way, users can filter the log messages. Examples might include "optimizer" and "file dependency" categories of messages.
Similar to code improvements (docs are code).
These are improvements to other systems to better support Racket.
For the more ambitious Racketeer ...
#lang scsh-- or better: write just a library for similar bindings (macros & functions), and make it into a language that has shell-like syntax