Good question. For now, we have a basic process for submitting icons, which requires adding details about the project repo, information on the icon, and Copyright attribution for whoever created / owns the brand.
We recently incorporated a JS library that allows us to generate the font from the SVG files themselves, which also builds the preview pages that can be viewed at icons.wedistribute.org. With a bit of extra automation on Codeberg, we could basically update the preview page and generated set every time a new icon gets merged in to the main
branch.
Our goal is to get to a point where new releases automatically get created, and an archive of the assets gets attached as well. That way, once a milestone gets completed, a new release will get put out with minimal amounts of work.
Yeah, I'm aware. I think the Nostr space in particular is doing a really great job, and has some good ideas on how to make it work. Why this development is significant, though, is that it's happening in ActivityPub space. It's not as robust, and doesn't have all the answers. But, the existence of such a project means that people within the space are already thinking about how to make this concept viable for the Fediverse.