A `raco` tag for all packages that add raco commands is a great idea. I don't think we should build some sort of system tag that's automatically added though; I'd much rather have some way of granting "tagging rights" to a set of catalog users and let them figure out what tags are appropriate for the variety of packages we have today. Not all sensible tags will have automatic means of detection. Here's a sample list of tags I'd like to have used consistently across the catalog:
- raco: provides a raco command - testing: provides something useful for testing code - data: provides a data structure of some sort - graphics: provides something related to drawing, images, or GUIs - lang: provides a #lang language - reader: provides something that modifies the racket reader, such as adding reader syntax for shorter anonymous functions - sugar: provides a simple shortcut that's generally useful and not specific to a particular library - documenting: provides something useful for documenting code - syntax: provides something useful for macros and other syntax object manipulations - concurrency: provides something useful for concurrent programming - network: provides something useful for making network calls and implementing various protocols - storage: provides something useful for persistent storage of values, such as database clients Dear package catalog maintainers: I volunteer to scour the catalog and tag everything under the sun. -- 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.
