> On Oct 20, 2017, at 8:06 AM, Vincent St-Amour > <stamo...@eecs.northwestern.edu> wrote: > > That page is pretty out of date. > > This list is more focused on contributing to Racket itself, but is more > up to date. It was compiled for the "office hours" portion of the last > RacketCon, ~2 weeks ago. > > https://github.com/racket/racket/wiki/Racketeer-Office-Hours-2017-Task-Ideas
There’s something that I now want, and I’m not sure which list to add it to. Following a discussion with William Hatch about shell usage in Racket, what I think I really want is auto-completion of filenames in DrRacket, probably using a pop-up. That is: I type a string containing a path fragment, and then I hit, say, C-c C-r or some other unused combination (ha!), and I get a dialog that will allow me with a small number of keystrokes to auto-complete to the filename that I’m looking for. Should be not-too-impossible. If I get a spare ten hours, I’d love to do it myself… Which list should I add this to? John cc: william hatch except I’m too busy to > > Vincent > > > On Fri, 20 Oct 2017 05:14:28 -0500, > Stephen De Gabrielle wrote: >> >> There is also a suggested projects page on the wiki >> >> https://github.com/racket/racket/wiki/Intro-Projects >> >> I don’t know if it is still accurate. >> >> Kind regards, >> >> Stephen >> >> On Fri, 20 Oct 2017 at 06:45, Jack Firth <jackhfi...@gmail.com> wrote: >> >> Welcome, we're very glad to have you! >> >> Open source Racket projects are scattered all over the place, but here are >> some good ways to find actively maintained and hopefully accessible projects >> that might interest you: >> >> - Watch some talks from recent RacketCons, especially the most recent one >> (which, conveniently, was barely a week and a half ago). A lot of talks are >> on interesting and wildly unusual open source projects, and as a bonus most >> presenters >> give out their contact information so people can reach out if they have >> questions or might be interested in contributing. You can find information >> on the most recent RacketCon at con.racket-lang.org including video and >> livestream recordings, >> talk descriptions, and slides for each talk. Info for previous RacketCons >> are available at con.racket-lang.org/2016/, con.racket-lang.org/2015/, etc. >> Alas we don't yet have individual prettily-edited videos for each talk at >> RacketCon 2017; they're >> only viewable via the saved livestream on youtube. >> - Search the official package catalog at pkgs.racket-lang.org for packages >> whose descriptions sound interesting and which are hosted on GitHub / GitLab >> / some other platform that makes it easy to contribute. Every package >> includes links to its >> docs and repostiory, as well as a contact email address for whoever >> maintains it. If you're not looking for a package in a particular problem >> domain your best bet is probably to restrict your search to only packages >> that build, have passing tests, >> and have docs. Decent issue / todo lists in the project repo are a nice >> bonus. >> - Browse around the front page of the online Racket documentation at >> docs.racket-lang.org. The online docs includes all docs from all >> successfully built user packages at pkgs.racket-lang.org, grouped into top >> level categories. Once you find >> some docs for a project that's interesting, it's (hopefully!) not difficult >> to find the package containing those docs by searching pkgs.racket-lang.org. >> - Hop in the Racket IRC (#racket on freenode) or the Racket Slack channel >> (signup at racket-slack.herokuapp.com) and ask around about what people are >> working on. I'm sure many folks will be delighted to talk about their >> projects. And this >> mailing list isn't a bad place to ask either. >> - If you want to try something more ambitious, you can take a peek at the >> Github repos in the "racket" organization (https://github.com/racket). These >> are all (or mostly? not sure) packages in the "main distribution", meaning >> they ship directly with >> Racket and don't have to be installed by users. Contributing to these >> packages can be a little trickier because sometimes they depend on the >> latest version of Racket's core, meaning you'll have to compile Racket's >> core from source. >> >> Also, all throughout this month Github and DigitalOcean are hosting an >> online event called Hacktoberfest. By signing up at >> https://hacktoberfest.digitalocean.com/ you'll get a free tshirt mailed to >> you if you submit four or more pull requests to any >> public repositories on Github before October ends. It doesn't matter how >> large each pull request is and a pull request to your own repo counts. And >> speaking from experience, they're very comfortable shirts. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> Kind regards, >> Stephen >> -- >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.