Digging through some of the older Issues in https://github.com/racket/racket/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc there appear to be many stale issues that may no longer be applicable or have been silently resolved in commits that were not cross-linked. I've started to respond to some such issues, though due to the low barrier of entry for finding tickets it seems that there would be value in having some sort of formal announcement asking for users to help identify and draw attention such issues. Once idea might be the inclusion of a section in "Racket News" that would list some arbitrary issues to highlight, categorized or simply listed. Another might be a (virtual) meetup akin to Google Summer of Code where individuals or small groups can pair up with a mentor to resolve non-trivial issues, reminiscent of the "Inside Racket" seminars.
As Racket moves from BC to CS, depending on what level of support can be expected for BC in the relatively near future (ie pre-v8.0) it may be worthwhile to entice users and contributors to donate their time toward doing some belated "spring cleaning". Consider this my (uninformed) 2 cents as a Racket-curious user and hopeful contributor looking to donate some of my own time. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/0b36280f-7995-4974-83a3-bf4d87fd0e9fn%40googlegroups.com.
