# What should we do for the summer event this year? **URL:** \ **Category:** General\ **Tags:** standard-fish\ **Created:** [June 25, 2023, 12:19pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039 "2023-06-25T12:19:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [June 25, 2023, 12:19pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/1 "2023-06-25T12:19:00Z")
What should we do for the summer event this year? In past years we have done - Pictures - Quickscripts - Macros - Languages I'm quite aware Racket the Platform are different things for different people. I'd like the event to be inclusive to bring new Racketeers in - but I also feel it needs some challenge to both showcase what is special about Racket, and make the event interesting. There is a strategy for coming up with ideas where you try to turn the filters off so you don't exclude ideas too soon. I think this is the 'no bad ideas' phase. I'll go first but if you have an idea you think is too crazy just DM me if you are shy. My idea: Little languages for pictures. so you are not making pictures you are making a little language to make a class of pictures s. ---
**Author:** ![sorawee](https://avatars.discourse-cdn.com/v4/letter/s/ea5d25/32.png) [@sorawee](https://racket.discourse.group/u/sorawee)\ **Post date:** [June 25, 2023, 3:08pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/2 "2023-06-25T15:08:30Z")
Documentation / examples 🙂 ---
**Author:** ![maueroats](https://avatars.discourse-cdn.com/v4/letter/m/c0e974/32.png) [@maueroats](https://racket.discourse.group/u/maueroats)\ **Post date:** [June 25, 2023, 9:47pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/3 "2023-06-25T21:47:23Z")
(I just made this up; I am not qualified to do the work so the description could be very flawed.) From a recent discord note: continuations: a quick intro (aka control flow fun) Show off cool, concise examples of uses of continuations. The target audience for reading the work is somebody who just heard of them once or twice but did not read any academic treatment of them (or did not understand it). Accessibility: an example illustrating the basics could probably produced after an hour of reading and thinking, so call it 2-3 hours of investment in learning and writing by someone who knows nothing. Why are you making this suggestion? So the next person with a big "why I'm quitting Racket" post is not able to cite "I did not understand the documentation on continuations" as one of the reasons. Coolness factor: low, afaik. Utility factor: low-medium unless either you include some specific examples of interesting constructs in the suggestions (amb?) or better-informed people have cooler uses. Include: - tutorials - small examples - delimited continuations ### Additional resources 1. [Lessons in Using Continuations](https://gist.github.com/jackfirth/027411d567385dadb3202bee75a847b4) - Jack Firth. (edit: added resources) ---
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [June 26, 2023, 3:18pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/4 "2023-06-26T15:18:45Z")
Thank you @maueroats & @sorawee These are excellent ideas! In addition to continuations, are there any other **areas** that need more examples? - [engines](https://docs.racket-lang.org/reference/engine.html) (came up for me recently and I still have not made an example I'm happy with) - syntax-parse-examples are always welcome 😅 - ??? For the mechanics of an event this seems pretty easy? - An entry consists of a PR against a racket repo - How to enter is effectively [Tutorial: Contributing to Racket](https://blog.racket-lang.org/2017/09/tutorial-contributing-to-racket.html) What constitutes an entry? - an example added to Racket docs - a [vignette](https://r-pkgs.org/vignettes.html) for a package e.g. [Pivoting](https://cran.r-project.org/web/packages/tidyr/vignettes/pivot.html) - a tutorial ( 👍 @maueroats fantastic idea) - an entry in a [Racket Cookbook](https://github.com/Racket-Cookbooks) - a working example in [pasterack](http://pasterack.org). e.g. [Paste # 7658: typed/racket](http://pasterack.org/pastes/7658) - a working example on the discord racket trick bot `!rkt` e.g. `!rkt show rackedle` best regards, Stephen PS any other event ideas? ---
**Author:** ![soegaard](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/soegaard/32/19_2.png) [@soegaard](https://racket.discourse.group/u/soegaard)\ **Post date:** [June 26, 2023, 5:08pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/5 "2023-06-26T17:08:55Z")
I enjoy reading about new topics, so how about: > ``` > 1) Implement you favorite algorithm in Racket and > write about it in a blog post. > or > 2) Experiment with a new Racket feature and > write about it in a blog post. > > ``` > > If you have the time, write a tutorial instead of a blog post (not an requirement). > If you do not have a blog, the entry can be posted on [blog.racket-lang.org](http://blog.racket-lang.org) . ---
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [July 11, 2023, 6:14pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/6 "2023-07-11T18:14:17Z")
---
**Author:** ![benknoble](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/benknoble/32/16_2.png) [@benknoble](https://racket.discourse.group/u/benknoble)\ **Post date:** [July 24, 2023, 1:38pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/7 "2023-07-24T13:38:59Z")
An area that could use some examples: `augment` and `inner` methods. The Class guide gives a few examples using `override`able methods (with `super` IIRC), but neither guide nor reference seems to contain an `inner` example. (I'd happily be proven wrong.) ---
**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\ **Post date:** [July 24, 2023, 5:45pm UTC](https://racket.discourse.group/t/what-should-we-do-for-the-summer-event-this-year/2039/8 "2023-07-24T17:45:49Z")
Hi, If there are no objections to the following I’ll post the announcement (with any corrections) on 1 Aug 2023 on Racket Discourse Best regards Stephen :standard_fish: :beetle: * * * # The 2023 Racket Summer Event This years theme is ‘racket examples’ The task is create an example - code and description - of a feature or algorithm. ## Entry Categories There will be two categories: ### Small to medium examples for inclusion in [https://docs.racket-lang.org/](https://docs.racket-lang.org/) (Or perhaps the [Racket-Cookbooks · GitHub](https://github.com/Racket-Cookbooks) ) ### larger examples As a [vignette](https://r-pkgs.org/vignettes.html) or blog post. Also for [https://docs.racket-lang.org/](https://docs.racket-lang.org/) but these may be considered for possible publication (or republication) on the official Racket Blog) ## How to submit? Two phase 1. Publish your submission this can be - a pull request to the relevant repository - a blog post - a post (‘topic’) on the Racket Discourse (category: [Show & Tell](https://racket.discourse.group/t/about-the-show-tell-category/121) with the tag ‘example’ 1. Notify the organisers: this will be a web form and will also include consent to use the entries and contact information for prizes. Personal information (name and address) will be kept private and only be use for the purpose of arranging postage of prizes. Personal information will not be retained after the event. Is concluded. ## Rules - Entries open 1 Aug 2023 - Entries close 20 October 2023 (in your timezone) - Winners will be announced at RacketCon 2023 and on RacketDiscourse. - entries must be _racket related_: any language on the racket platform including languages not part of the standard distribution; it can be racket/base, typed racket, Qi, RacketScript, Zuo, Urlang, Rhombus, Nora(LLVM Racket compiler), Shplait, or something else entirely. - All entries must include :standard_fish: ## Prizes! - the admiration of your peers - stickers! - tbc ## Sponsor this event ! Racketeer are the most capable developers I have met - do yourself a favour and get in touch.