Coordinating work on package system improvements

[alex.mclin]

Hi Racketeers,

I'm interested in contributing to improvements for Racket's current package system. Wish lists of improvement are documented in various places, Slack, Github, and users mailing list. I will be going through those sources to attempt to consolidate them and post a reasonably complete list (and growing) either on here or probably more appropriately on an issue page in a github repository.

I see there are active issues and work in various package related repositories hosted under tonyg.

I'm posting here to announce my intentions and to reach out to others working on the package system in order to coordinate with them and prevent duplicate work. If you would be kind and let me know if you are actively working in the same area.

Cordially,

A.B. McLin

[Jack Firth]

Thanks a lot for doing this Alex!

As far as I know, the main repositories of interest are:

- tonyg/racket-pkg-website - the fronted server that renders the HTML / JS / CSS / Atom feeds displayed at pkgs.racket-lang.org
- racket/pkg-index - the backend server that provides an HTTP API for the package catalog users database and packages database
- racket/pkg-build - the build server that builds and tests every package in the catalog nightly

- tonyg/racket-pkg-server - an overview of the other repositories, as well as deployment and ops scripts
- racket/racket - contains the implementation of all the `raco pkg` commands

Discussion and issues typically end up at either racket/racket or tonyg/racket-pkg-website, depending on whether or not it's more

related to the server or the `raco pkg` commands.