Matthias Felleisen
unread,Apr 5, 2017, 11:20:09 AM4/5/17Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Racket Developers
Every few months, the principals of the Racket world meet for a day to
discuss the state and near (and, occasionally, distant) future of the
Racket world. We met on April 1 (not a joke) and discussed the following
topics, revisiting some that had been on the agenda before:
-- software freedom conservancy
We are still corresponding with the SFC to set up a separate funding
channel for Racket. While we have made some progress, the correspondence
moves at a snail's pace mostly due to delays on SFC's side.
-- license
Most contributors have responded to our request for changes to the
license. See last announcement for details. We will email the remaining
individuals directly to seek their permission for a switch.
-- beta releases
Northwestern is keeping additional releases, including some that survive
for the entire release cycle, but discoverability is unfortunately
subpar. We will improve it.
-- infrastructure
Ryan Culpepper joined us for a short time to present his plans for
re-organizing some of the major background infrastructure at
Northeastern.
We thank Ryan for many years of volunteering to take care of the
Northeastern computers.
-- security
In anticipation of security problems, we have decided to set up a web page
and to link to it from our front page at a prominent position. The web
page will allow users to report security problems and will list all
confirmed and patched problems. In addition, we will create a mailing list
for people interested in security vulnerabilities.
-- packages
We will change the site so that it also signals a problem if a package
comes without documentation and/or the documentation does not build.
Furthermore, we will shortly switch the server's front-page to improve its
usability.