the community is in need of a comprehensive archive/collection of Rascal libraries. Think grammars and front-end for specific programming languages, visualization libraries, etc.
the goal is to make Rascal libraries "discoverable" and "usable", so as to enable more Rascal users to reach their own goals
we need to think about this carefully, learn from others. For example for R there is CRAN.
the functionality of entries into the library depends on Rascal's run-time system, i.e. how Rascal libraries are dynamically linked. With the compiler under-way, and this archive not being created over-night, let's consider this from a "compiled Rascal" viewpoint?
example entries: rascal-csharp, rascal-dotnet, shapes, drambiguity, rascal-ecore
see also the RAP 1 on rascal deployment, where we speak of a "rascal package server" named r2d2.usethesource.io
note that this community feature is independent of the adoption of such libraries on usethesource.io. The distinction:
a library/project on usethesource.io is developed and maintained by members of the usethesource organization; their development is closely evolved with Rascal. These libraries would certainly also end up on the comprehensive rascal archive
other libraries could also end-up in the comprehensive rascal archive, which are not on usethesource.io
this does not imply that usethesource is a closed organization (people will be added to it if they want to and can contribute to one of the usethesource projects)
r2d2.usethesource.io