Sahil (Nov 15 2024 at 14:48): Sahil (Nov 15 2024 at 14:48):I'm proposing an idea where we can create a new repo under roc-lang organization. This repo will be used to create a github page that will keep track of all the roc packages. This is how it'll work: Whenever someone creates a pakage for roc lang, they can submit a PR to this repo with their package link. Then as soon as the PR merges, it'll update the list of packages.
This will help users like me to discover packages easily.
I have discussed this in one of the threads and @Anton suggested me to create a thread about this.
Please let me know your thoughts, if this sounds good, then I would love to implement this
Anton (Nov 15 2024 at 14:52):Currently there is the mostly automated https://hasnep.github.io/roc-packages/ , if @Hannes approves we could move it under roc-lang for increased discoverability.
Hannes (Nov 15 2024 at 14:54):Haha, you could move it under the roc-lang org, but it's a pretty bodged Python script to dump data and then a Roc script to convert that to an almost unstyled HTML page. If there's interest in making it more official then I'd like to at least rewrite it in Roc :sweat_smile:
Sahil (Nov 15 2024 at 15:08):sure as long as the process to find packages easily can be achieved, looking forward to see the improvement
Richard Feldman (Nov 15 2024 at 16:04):I don't think we should move it haha
Richard Feldman (Nov 15 2024 at 16:05):eventually we'll make something fancier that can live under the roc-lang org
Anton (Nov 15 2024 at 16:24):Can you elaborate? This looks a bit like letting perfect be the enemy of good.
Richard Feldman (Nov 15 2024 at 16:37):I don't think people are looking for a package listing by browsing the roc-lang org's list of repositories, so I don't think it would make a significant difference in discoverability
Richard Feldman (Nov 15 2024 at 16:39):but I do think it would create a perception of like "this is the official way to do it and we plan to incrementally improve this so let's coordinate about that on Zulip like usual" as opposed to "this is a community member who made a helpful thing in their free time, so let's be appreciative but not create pressure to polish it etc"
Last updated: Jun 16 2026 at 16:19 UTC